I'm pleased to announce the availability of the new OpenGuides development site, http://dev.openguides.org/. This site integrates several resources we've been using before and should improve the workflow of the project.

Dev wiki: Trac includes a wiki which we'll use as a replacement for http://openguides.org/dev/ (which has broken). I've integrated most of the content of the old wiki, though I've dropped a few nodes that were no longer relevant. http://dev.openguides.org/ is the front page of the wiki.

Bugs: Instead of rt.cpan.org (which has proved rather cumbersome in the past) we'll use trac's ticketing functionality: I've integrated all the open RT tickets (and closed them with a reference to their trac URL) and you can see a report of all active tickets at http://dev.openguides.org/report/1. You can report new bugs at http://dev.openguides.org/newticket.

SVN browser: We didn't have any nice web view of the source before; now we have http://dev.openguides.org/browser which is a good way of viewing changesets and file histories, and so on.

The SVN repository itself remains at https://urchin.earth.li/svn/openguides/

Timeline: http://dev.openguides.org/timeline, and its associated RSS feed, provides a good overview of OpenGuides development activity. If you use RSS I recommend you subscribe to the feed.

Email notifications: Changes to tickets get emailed to the mailing list http://urchin.earth.li/mailman/listinfo/openguides-tickets which you may want to subscribe to (as a companion to http://urchin.earth.li/mailman/listinfo/openguides-commits.

All these things link in rather nicely, so you'll see references in changeset logs, tickets and wiki pages referring to reach other. Please take a few minutes to browse through the Trac user documentation at http://dev.openguides.org/wiki/TracGuide for how to use Trac most effectively.

Currently, all day-to-day aspects of trac can be used without logging in. However I recommend that regular users of the site register for an account by emailing me an htpasswd password hash or plain text password, and their preferred username. Then they can be referred to as a simple username rather than an email address. In time I reserve the right to restrict certain operations to registered users, if spammers get hold of the site.

Note that people with commit access to SVN should be using the same usernames but different passwords. This is due to the increased security on the SVN site compared to Trac (ie it's SSL-protected).

Please address any comments about Trac to me or to the mailing list, and enjoy! Thanks are due to Earle and Ivor for suggesting the use of this fine package, and to Edgewall Software for developing Trac.

Cheers,

Dominic.