For low-traffic announcements of new versions or other important news, subscribe to the Crabgrass Announcement mailing list
For a slightly higher traffic, you can join the list where development discussion happens: the Crabgrass Developer mailing list
If you are hosting crabgrass you can sign up to this low traffic list dedicated to hosting issues: the Crabgrass Hosting mailing list
IRC: We’re currently holding down an IRC channel on the `irc.indymedia.org` network. You can find us in `#crabgrass` if you prefer to communicate this way.
This channel is logged, so please be aware of that when you join. You can find past logs here of the channel.
Found a bug? Feature request?
Reporting Bugs and Requesting Features: If you have found a bug in the system, or would like a feature added, head over to our Bug Tracker and search to see if your issue has already been reported (if so, maybe you can add some more information?) and if not, sign up and submit a new issue.
You can get the core rework here. This is where development towards version 1.0 is taking place.
git clone labs.riseup.net:crabgrass-core.git
Contributing Code: Do you have some code to share, a bug to fix, or a feature to incorporate? We’d love to see it! Please first associate your change with an issue in our tracker (if there is none related to your work, please open one!). Then either attach a patch to the issue in Redmine, or indicate where your public Git repository is located with the change.
The Users Group: If you have questions and comments about crabgrass you can view and join the users group.
Crabgrass Developer Network: If you have checked out the code and become familiar with the basic concepts, you should request to join the Crabgrass Development network. This network is for people and groups actively contributing code and templates to crabgrass.
Please feel free to contact us at firstname.lastname@example.org