Sirikata

Sirikata is slowly improving the infrastructure surrounding the project: we’ve had the mailing lists and a code repository since the project started, added the wiki soon after, we have an IRC channel, and most recently we added this blog.  Today, we’re making the new bug tracker public.  We’re using an instance of the excellent Trac software.  Calling it a bug tracker may be giving it too little credit: it also allows you to track milestones, versions, feature requests, commits to the source code repository, and much more.  A lot of the services we need are already provided by GitHub, so we’ve turned many of those features off and are focusing on using Trac specifically to handle bugs and feature requests, with just a little bit of milestone tracking thrown in for good measure.

We still need a bit more documentation on how to file good bug reports.  A short list of items to keep in mind:

• The version or revision number which the bug was discovered on. Bonus points if you can track down the revision that introduced the problem.
• The platform you are working on.
• The features you have turned on and/or plugins you have loaded.
• A minimal test case if applicable, or a minimal set of steps needed to reproduce the problem.
• A backtrace if you are reporting a crash and can obtain one.

So if you’ve encountered problems compiling or running Sirikata, please take the time to file a bug report on our new system.  It does require an account to avoid spam, but anybody can register.  And if you run into any problems, email me and/or the developer list for help.