Jim,
The procedure for new contributions is quite simple. You just post your contribution
to the log4j-user mailing list. If it makes sense to do so, I (or any another
comitter) will add it to the contribs/ directory. I plan to be liberal about adding
contributions but would like to exert a minimum amount of selection so that the
contribs/ directory does not get out of hand.
If you would like to update an existing contribution, then you should submit a patch
to the log4j-user ML or to log4j-dev ML as you prefer.
Unless I am mistaken, the ASF rules say that an existing committer nominates a
developer, the existing committers take a vote, and if there are 3 in favor and no
objections, then the developer gets commit access. In practice, if a developer
*consistently* makes contributions, then there is a good chance that she will get
commit access.
The ASF is very open to newcomers. We just would like to see some commitment (no pun
intended) to the project first. Ceki
At 13:51 14.02.2001 -0500, you wrote:
>What's the procedure for submiting something for contrib and for
>suggesting/making changes to it? I doubt yu're going to give full, open
>access to the entire log4j project...
>
>-Jim Moore
>
>
>-----Original Message-----
>From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, February 14, 2001 12:44 PM
>To: LOG4J Users Mailing List
>Subject: Re: AW: JDBCAppender
>
>
>
>Jason,
>
>I added a contribs/ directory to the log4j CVS module. I hope that it will
>work out as well as in the Turbine project. Cheers, Ceki
>
>At 11:25 14.02.2001 -0500, you wrote:
>
>>In Velocity we have a whiteboard directory, but things that have
>>been whiteboarded have been managed by a committer. The majority
>>of the time the items being whiteboarded are done so by
>>committers. But the whiteboard directory can be kept away
>>from the compile and it's been my experience that items
>>being whiteboarded are usually either dumped or moved
>>into the project relatively quickly because the item
>>is in demand.
>>
>>I think if the JDBCAppender was thrown in a whiteboard
>>directory we could all get a look at it and comment.
>>I like this method, and I don't think the whiteboard
>>will get out of control. There is usually only a couple
>>things in the whiteboard at a time and I think something
>>like a JDBCAppender will get enough attention that it
>>can be made solid enough to put in the package in a
>>short period of time.
>>
>>jvz.
>
>
>
>
>----
>Ceki Gülcü e-mail: [EMAIL PROTECTED] (preferred)
>av. de Rumine 5 [EMAIL PROTECTED]
>CH-1005 Lausanne
>Switzerland Tel: ++41 21 351 23 15
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
----
Ceki Gülcü e-mail: [EMAIL PROTECTED] (preferred)
av. de Rumine 5 [EMAIL PROTECTED]
CH-1005 Lausanne
Switzerland Tel: ++41 21 351 23 15
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
