[Gforge-devel] Commit policy?

[Jacob Levine]

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.

I posted this to the Devel forum as well, but I was told it was being
withheld until a moderator could approve it.

Cheers,

-- 
-Jacob Levine