On Sun, 2011-03-20 at 11:44 -1000, Warren Togami Jr. wrote:
> On 3/19/2011 1:08 PM, Karsten Bräckelmann wrote:
> > Please help keep bugzilla clean!
>
> Good point. Thank you.
Just to clarify -- sure, any directly related information, update, and
to some extent discussion, of course is appropriate as a bug's comment.
Unrelated questions and discussion, that just happen to come to mind
reading bug comments, should go to the dev@ list instead. Bugzilla is
not a means of communication (other than in very special situations),
but a tool to track an issue's state. This helps tremendously e.g. when
re-reading a bug later, as well as generally improves keeping a clear
picture and overview of the state.
> > > Is there a process to nominate new committers?
> > Anyway, this is NOT about a lack of committers. Such code changes go
> > into trunk only, which equals the current Target Milestone 3.4.
> > Committing for the current stable branch 3.3 requires votes *before* the
> > commit.
>
> I wasn't aware that it was proposed for 3.3.x. I agree 3.4 is fine. I
It was not explicitly proposed for the 3.3 branch -- though kind of
implicitly, by urging to get it committed to SVN. With a Target
Milestone of 3.4 (granted, set after the fact), there's quite some time
to get reviews, extended testing and possibly some feature refinements,
before committing the code to trunk.
There's other, more important tasks to be done for forthcoming 3.3.x
releases, which is likely to get more attention in the short-term.
> only suggest that Darxus would make a fine addition to our team as we
> appear to be short staffed and he has the skills, desire and time to
> work on our issues.
The general way for an active community member to become a committer is,
to have a proven track record in bugzilla and the lists, get promoted by
a PMC member and voted by the whole of the PMC.
Recent additions to our committers e.g. have published various plugins
during the months (or years) before, which have been actively used by
the community.
FWIW, "to work on our issues" does not necessarily require committer
status. Frankly, it generally is the other way round -- there are bugs
one can work on and attach patches to bugzilla, which after review then
can be committed to trunk (or even the current stable branch).
Just as with any Open Source project, there is no need to gain commit
privs oneself, to contribute to the project by providing fixes and
patches.
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
