[Gforge-devel] Commit policy?

[Tim Perdue]

Jacob Levine wrote:
> Hello list,
> 
> I have been wondering what sort of policy I should be following regarding
> commits to the svn repository. As far as I can tell, since opening a
> handful of bugs last month here and in the Mod Auth GForge project no else
> has made any changes to them. I have patches attached to half of my bugs--
> valid patches so far as I can understand.
> 
> That's the crux of my question-- I have only just joined this project and
> so have a very limited understanding of how GForge works. Should I just go
> ahead and commit the patches that look ok to me, expecting someone else to
> revert them if they discover a problem? Or should I continue to post
> patches to the trackers, hoping that someone will find the time to look at
> them? The Contribution Guide indicates that the latter approach should be
> taken, but in the trackers I've found some old patches that have never
> been addressed.

You should try to review and commit patches, fix bugs, etc, as long as 
you are keeping it stable.

Basically, the core team of GForge needs to be rebuilt. The old core 
team of french guys all quit working on the project a couple years ago, 
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'.

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.

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

Tim