On Jul 27, 2006, at 9:53 AM, ant elder wrote:
One of the reasons I started this thread was to try to get a common
understanding about what everyone expects is required to become a
Tuscany
committer. Its hard to publicly say you think someone isn't ready
yet, even
on the private list, so a
On Jul 27, 2006, at 9:53 AM, ant elder wrote:
One of the reasons I started this thread was to try to get a common
understanding about what everyone expects is required to become a
Tuscany
committer. Its hard to publicly say you think someone isn't ready
yet, even
on the private list, so a
One of the reasons I started this thread was to try to get a common
understanding about what everyone expects is required to become a Tuscany
committer. Its hard to publicly say you think someone isn't ready yet, even
on the private list, so a common understanding would mean nominations would
On 7/27/06, ant elder [EMAIL PROTECTED] wrote:
One of the reasons I started this thread was to try to get a common
understanding about what everyone expects is required to become a Tuscany
committer. Its hard to publicly say you think someone isn't ready yet, even
on the private list, so a
A tongue in cheek reply to this I've once heard in OS in general was
when you get tired of applying the persons patches :-)
(sorry if this old or already mentioned)
robert burrell donkin wrote:
On 7/27/06, ant elder [EMAIL PROTECTED] wrote:
One of the reasons I started this thread was to try
On Jul 5, 2006, at 4:42 PM, Raymond Feng wrote:
Hi,
I guess I can understand how to get credits for the committer
status.
As a contributor, I would like to see a well-defined measurable
path which I can see how I make progresses toward the goal. It
leads two questions:
1) How many
+1 from me on taking into account diverse activities, but I must declare a
vested interest.
I'm encouraged by this discussion, since I'd like to become a committer, and
have had that niggling feeling that if it's notches on the jira bedpost that
are the primary measure, then it's going to take a
I assume that a committer, once elected, is active in the entire code base.
This bothers me a little. I currently
work entirely in the C++ implementation and do almost nothing with the Java
code. I think I could easily reach a
situation where I have done all the things required of a committer
In my opinion no, everyone has strengths and weaknesses and you don't have
to be able to do everything to become a committer. Its more about trust. If
someones speciality is doc they may never touch any code but they'd still
need commit access to update the website. This is the way the Apache WS
On 7/3/06, ant elder [EMAIL PROTECTED] wrote:
I think it should take a bit more than code to be made a committer -
participation in mailing list discussions, the weekly IRC chats, votes,
and
things like that. And its not just code, high-quality patches could
include
things for documentation or
On 7/3/06, Andrew Borley [EMAIL PROTECTED] wrote:
I'd agree with this - however, as someone working on the C++ side of things
I personally don't feel able to join in with the majority of discussion,
centred, as it is, around the Java work. The C++ side is quieter, with Pete
and Ed being the main
11 matches
Mail list logo
