>>>> "Jan" == Jan Rychter
<jan(a)rychter.com> writes:
Jan> I did just that about a year ago -- I posted a reasonably
Jan> simple patch that adds about 4 lines of code to the XEmacs
Jan> code base. I brought the issue up again about three weeks
Jan> ago, and a couple of days ago, but it seems continuous
Jan> nagging doesn't get me anywhere.
I'm sorry about that. Your patch is not one I'm competent to review.
As far as I knew, Ben was aware of it (and in fact has since committed
it), so I left it at that.
Jan> I understand "being short-handed for developers", but this
Jan> attitude will cause even more developers to go elsewhere.
It's not an "attitude", it's a fact. If saying so would make
developers go elsewhere, I think it's only fair to say so so they can
make an informed choice: go, or ask for the authority to make it
happen themselves.
If you want to accept the responsibility (ie, to review _some_ of
other people's small patches) and get the authority (to commit them),
write to xemacs-review(a)xemacs.org and say you want to be a reviewer.
I can't say it's a done deal, but I know your posts and patches well
enough to support you; I suppose there are probably other reviewers
who would, too.
By the way, as far as I'm concerned, people who have been contributing
for a while, even just bug reports, are welcome to nominate themselves
to the review board. It does require that the current reviewers be
able to assess your ability to review, so you need a public track
record as a developer somewhere (preferably in XEmacs, of course) or a
strong sponsor already on the board.
You're welcome to ask for more information, from me, at least. If you
know other reviewers well enough, you could ask them too (there's a
list at
http://www.xemacs.org/develop/jobs.html). My guess is most
would welcome inquiries, but I'm the only one I _know_ does. :-)
--
School of Systems and Information Engineering
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.