[STUMP] commit access (was [PATCH] Add command-line options support)
Ben Spencer <dangerous.ben <at> gmail.com>
2011-03-06 14:34:32 GMT
On Sun, Mar 06, 2011 at 07:37:42AM -0600, Krzysztof Drewniak wrote:
> This list is oddly silent. YOu send in a patch, and you never find out
> if anyone has even *seen* the thing, let alone their opinions of it
> and wether it will ever be committed. I can understand that people
> have a life, and probably won't reply to anything right away. However,
> I sent a trivial bugfix a week ago, and I still don't have word on
> whether the fix will make it in, which is supprisong, given that
> someone (Shawn) evidently reads the list. Now, there might be some
> external factor that's causing this patch backlog that I don't know
> about, in whih case I take all of this back, but if there isn't, then
> maybe, just maybe, this project needs more active maintainers.
You are quite right, the project does need more active maintainers.
That said, you yourself surfaced on the mailing list just a week ago,
which is not a long time by any project's standards.
The hard part of being a maintainer is something you (or anybody else
for that matter) can already participate in - reviewing and commenting
on patches on the ML. This alone would make life easier for the
existing maintainers and make the list less silent. You could also
publish your patches in your own public git repo.
So my take on this is not to give you commit access right now, but
maybe later when you've been active for a while. Happy to hear
opinions from others of course.
I have had a look at your patches and will reply separately to those
emails because this one is already too long. If you want to talk