This page is out of date. See Communication Tools
Summary of instruments we use to manage the Cocoon project:
- Bug tracking
*add a new bug (direct link)
*list of all open bugs
*list of all blocker bugs these bugs definitely stop a release because of broken core functionality
*add a new patch
*list of all provided patches
*See How to Prepare a Patch and How to Contribute a Patch via Bugzilla.
- Roadmap planing
*add a new enhancement issue
*Cocoon Roadmap (the complete Cocoon2 roadmap)
*Issues for the next release
*Issues for future releases
*issues that changed in the last 2 days
*issues that changed ini the last 7 days
If you assign yourself to an issue don't forget to add firstname.lastname@example.org as CC'ed mail address (otherwise the community won't be informed about changes on the issue any more)!
We use mailing lists as our central communication tool. Also see the archives. The Cocoon mailing lists are currently also being archived into an unofficial Cocoon Forum by Nabble. You can browse and search all lists' posts there. The UI is clean and the search is good. You can also create sub forums there to expand the discussion.
Every FirstFriday in a month we meet for 'virtual hackathons'.
As you found this page you already know that we have set up a Wiki for some of the documentation. If you want to enhance or add docs to the official documentation have a look at our Documentation HowTo and How to Prepare a Patch.