A good way to coordinate open source project development

Question

What would be a good way to coordinate the development of an open source project? (This is a Python project.)

I know that the traditional way is mailing lists, but I don’t like it. I don’t want people to receive emails about the project all the time. They should be able to participate only when they so wish. In addition, mailmansucks.

I looked at Google groups, but I heard several horror stories from people who tried to coordinate their development there.

Does anyone have any other suggestion?

Answer 1

wiki. , .

Answer 2

Assembla GitHub, , .

Answer 3

. : http://www.simplemachines.org/

Answer 4

, . , , . , , , , phpBB. , google, Google.

, , ? Karl Fogel , ( Subversion).

Answer 5

(, - phpBB), , - - " ".

Answer 6

, Google Wave "" . . , .

, . , , (SVN, Mercurial ..), .

Answer 7

, ( ).

, . . " " .

As a developer, use search queries / functions to find the most important issues for the current iteration. Ideally, choose a problem that provides high value, or just what you can do. Update the status of the problem when you start working on it, when everything is ready, etc., so that others know that something is happening.