Bjorn,
I am not sure why you are creating a higher
standard for Nathan. When Mike nominated Donald to be a committer you did
not have these concerns?
Regarding your suggestions to move
forward, why is it not good enough to have the discussion on a public mailing list?
A lot of the work done on the web site is content related and we
have not been entering bugzilla requests for these types of things. Starting
to enter bugzilla requesst just to have Nathan voted as a committer seems
artificial and bureaucratic.
Regardless, here is what I believe Nathan
has done and I believe it is available for all to review.
1. Matt has already voted a +1 and
referred to a bug # that Nathan has done.
2. Denis is out of the office but he did
check-in the code for the updates Nathan did to these pages: http://www.eclipse.org/community/rcp.php,
http://www.eclipse.org/community/rcpos.php,
http://www.eclipse.org/community/rcpcp.php.
I also reviewed these pages before they were checked in.
3. Nathan has been working with Susan on
the RSS feeds and a community bulletin. One example is http://www.eclipse.org/org/press-release/20060309cb_elections.php.
4. Nathan will be doing a number of pages
for the Eclipse Awards. I will review them and commit them next
week. Unfortunately they can not go public until March 21, for obvious
reasons.
Bjorn, are there specific things you would
like Nathan to work on, so you can review his work?
Ian
From: phoenix-dev-bounces@xxxxxxxxxxx
[mailto:phoenix-dev-bounces@xxxxxxxxxxx] On
Behalf Of Bjorn Freeman-Benson
Sent: March 9, 2006 4:15 PM
To: For
developers on the new Eclipse.org website project.
Subject: Re: [phoenix-dev] New
Phoenix Committer
Given that I have vetoed Nathan's immediate election
as a Phoenix
committer, I should state what I think we should do to move him towards a place
where I will remove my veto. So...
What I am looking for is public evidence of Nathan's skills - public in a way
that someone who is not working with/directing Nathan can use the same evidence
to decide that Nathan has the skills and judgement necessary to be a committer.
This can be done by having bugs in bugzilla that Nathan fixes with patches,
having a committer apply those patches, and having the committer report back in
the bug that the patch was good and close the bug. This allows others to see
and evaluate for themsevles: (1) the difficult of the problem being solved (the
bug); (2) the quality of the fix (the patch file and the number of times it had
to be re-spun); and (3) a public statement of the committer's opinion of the
work (the comment from the commiter when closing the bug).
I'd also like to see Nathan work with three different existing committers and
thus get three different reviews of his code. I understand that he has worked
with Ian and with Susan, although I'm not sure (because there is no bugzilla
traceability) whether both Ian and Susan committed his files/patches or just
Susan did? Anyway, three seperate, independent evaluations done in public
(bugzilla) and I will definitely remove my veto.
Please note that all of this had nothing to do with Nathan - it's just standard
"before electing a new committer to an Eclipse project" process.
Really.
- Bjorn