# The TurboGears Community

# need help?

If you can't find the information you seek in the documentation, you can probably find the answers:

- by searching the mailing list archive
- by subscribing to the mailing list
- from people on the IRC channel

As an open source project, TurboGears thrives on the enthusiasm and participation of its users. The community supports TurboGears and drives its development.

## Getting Involved

There are plenty of interesting projects to work on (and tickets to work on in the Trac), and we're trying to make it easy to contribute to TurboGears. Even contributing ideas, observations and bug reports to the mailing list is a big help.

## Sprints

A sprint is a focused event where people get together to work on TurboGears code and work out some ideas.

TurboGears had a "mad dash" sprint on October 8th, 2005 in Ann Arbor, Michigan.

The next sprint is likely to be online. Date/time and details have not yet been arranged. To participate, sign up for the turbogears-sprint mailing list to get your preferences in.

There will likely be another Ann Arbor sprint coming up as well.

## Reporting Bugs (even with bugs on this site!)

There is a Trac instance at trac.turbogears.org. Use this to report bugs, check on what's going on with new versions, write up small bits of documentation that can eventually make it into the full site, etc.

## Adding unpolished documentation

You can also use the DocumentationPlayground on the Trac wiki to add things that you've learned that are missing from the docs. These things will be reviewed prior to releases to figure out which items will get included (and where!) in the official docs.

## Need help?

The documentation is being added at present. The best way to influence which docs get written first is to let us know on the mailing list.

If you want to chat with someone, there are often a few people hanging out in the turbogears channel on irc.freenode.net.

You can get help on TurboGears from the mailing list, by asking questions and searching the list archives. (There's also an announcements mailing list if you just want to keep up with new development.)

Most of the techniques you need to use in TurboGears come directly from the projects that are included with TurboGears. That means that you can get great support from the established mailing lists for those projects:

MochiKit mailing list for MochiKit JavaScript related questions.

Kid mailing list for Kid template related questions.

CherryPy-users mailing list for questions about how to use CherryPy. Since this is where TurboGears code is most visible, your best bet may be the TurboGears mailing list for these questions. This is still a good list to subscribe to, though, because tips that come up here are often relevant to users of TurboGears.

CherryPy-devel mailing list for talk about improving CherryPy itself.

SQLObject mailing list for questions about using SQLObject to work with your database.

## Stay Up To Date

Planet TurboGears has the latest articles from TurboGears-related blogs. This will be less traffic than the discussion list, but more frequent than the announcements list.