[Gforge-devel] Commit policy?

Roland Mas lolando at debian.org
Thu Oct 5 04:43:58 EDT 2006


Tim Perdue, 2006-10-05 03:14:50 -0500 :

> The old core team of french guys all quit working on the project a
> couple years ago,

That's not entirely true.  While we haven't worked much on the core of
Gforge itself, Christian and I keep committing stuff, both to keep an
automated installation doable and to add plugins.  Your other points
still more or less stand, though.

> and I quit posting here 6 months ago because absolutely no one was
> responding or supporting me or my team in any way. I provided all
> the support on the user forum for the last 1-2 years and can't
> remember the last time someone simply said 'thanks'.

  I don't read web forums (or post on them) as a matter of intense
dislike for their UI (not Gforge-specific), but I have provided
support to people contacting me by email, as well as on IRC.

> In order for an open source project to survive, their needs to be
> people encouraging and supporting it, not just sucking the system
> dry, which is what happened here. The project got sucked dry and
> without any feedback from the users, people stopped working on it. I
> call it the "Rip n Run" mentality of the GForge user base.

  Yeah.  That depressed me at some point too.  As a matter of policy,
I keep all my developments (including for-hire ones) on Gforge public,
but not everyone does that, unfortunately.

> I'd suggest consolidating discussions on the user forum so as not to
> divide attention between two low-volume lists.

  I'd suggest using the (more accessible) mailing-lists instead, but
consolidating them all into one would indeed be a good move.

Roland.
-- 
Roland Mas

Why did the elephant cross the road?
Because it was the chicken's day off.


More information about the Gforge-devel mailing list