On bootstrapping a community-run FOSS event
Posted Apr 21, 2010 22:13 UTC (Wed) by n8willis
In reply to: On bootstrapping a community-run FOSS event
Parent article: On bootstrapping a community-run FOSS event
Again, it's not that a mailing list is hard in and of itself, it's that the closed source service offered by Google is orders of magnitude simpler. Point, click, done. When you don't know which direction a concept is going to take, the overhead of all of the other software-project-management setup processes (TOS, project approval policy, enabling features that you neither need nor want) put the code-centric services further behind the list-only offerings.
As for the forges you mention, Alioth and Savannah both have very strict pre-approval processes: http://lists.debian.org/debian-devel-announce/2003/03/msg00024.html and http://savannah.gnu.org/register/requirements.php. SourceForge doesn't use a pre-emptive block on new projects, but it still requires that you produce code: https://sourceforge.net/apps/trac/sitelegal/wiki/What%20projects%20qualify%20for%20hosting%20at%20SourceForge.net? ... and in any case, you end up with a code project built around tools you do not need. Bugzilla is not capable of tracking event-planning tasks; the only relevant fields are Modified Date and Assigned To, which is essentially just as trackable as a wiki page or plain text document.
to post comments)