On Wed, 14 Feb 2001, Ceki [iso-8859-1] Gülcü wrote:
>
> Hi Jason,
>
> I admit that the current situation where some contributions end up in a black hole
>needs to be corrected.
>
> One approach is to add a link to the external contrib on a widely visited page on
>the log4j site (e.g. download.html). This is the easiest solution to manage/maintain
>except that not all contributions have a web-site.
>
> We could also add a contribs/ directory under jakarta-log4j/ on our CVS repository.
>The question is then how to manage these contributions. Do we just dump them in a
>directory? Clearly, this problem is not unique to log4j.
>
> Comments? Ceki
>
> ps: How do the Turbine developers deal with this?
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
