In the old setup, we had a special developer site based on Trac, with a wiki and an issue tracker, and our own version control system. Instead of setting all that up again, we're moving to hosted services. Not all content from Trac has been migrated yet, we'll work on that.

The code and documentation

The Drupal source code is now on Github. https://github.com/nabuur/nabuur-d5

This makes it lots easier for coders to participate: just fork the code, make improvements, and send us a pull request.

The documentation should slowly appear on the Github wiki, as well as in a public folder on Google Docs (via bit.ly/nabuur-docs)

Tracking and planning the work

Github has its own issue tracker that we can use for code-level bugs, feature requests, and so on. There are no tickets in there yet, but perhaps we'll use it in the future.

Our main planning tool, however, is Pivotal Tracker (we have a non-profit account from them for free). We run a couple of public projects there:

• NABUUR.com is the project for "behind the scenes" work on the website: cleaning up things, code issues, developer-oriented work. (The Github project is linked with this project.)
• NABUUR is for all community-oriented tasks and issues (not only technical). We'll add the community chats as milestones there, so we can plan the work ahead a bit in relation to community chats.

You can have a look at the progress in these projects without having to register.

Keeping up to date

• If you are on Github: Watch our repository and get updates on your dashboard.
• Follow nabuurtracker on Twitter where we aggregate updates from Pivotal Tracker and Github.
• Join the community chats and gatherings. They're announced via the blog, and in a Google calendar (soon to be visible on nabuur.com too)
• Join the IRC #nabuur chat channel on Freenode