Hi,
That actually gave me an idea: why not put it in the NetBeans repository
where you're already setup?

In Apache, there needs to be a long-demonstrated background of
contributions before getting commit privileges.  We have different
processes in this area than NetBeans and some of the other open-source
collaborations.

Yoav Shapira http://www.yoavshapira.com


>-----Original Message-----
>From: Garrison, Meg [mailto:[EMAIL PROTECTED]
>Sent: Monday, November 01, 2004 7:03 AM
>To: Tomcat Developers List
>Subject: RE: contrib directory
>
>Hi Leslie,
>
>I'm also willing to maintain the HP OpenVMS scripts.  Rather than
create
>a whole new project (tomcat-contrib) maybe it would be possible for the
>Tomcat folks to grant us commit access to a single module/folder in
>their CVS library (a contrib folder of some sort).  Then they wouldn't
>have to worry about committing our changes, etc..  If we misbehave and
>don't follow their rules, then they have the option to "boot us out".
>That's how the NetBeans project does it.  For example, I have commit
>powers in the core module, which is where the OpenVMS launcher lives,
>but no other.  Our needs for NetBeans (as yours, I'm sure) require that
>the default Tomcat distribution contain our launcher somewhere...it
>doesn't have to be in /bin.
>
>Any other ideas?
>
>Meg
>
>-----Original Message-----
>From: Leslie Kishalmi [mailto:[EMAIL PROTECTED]
>Sent: Friday, October 29, 2004 5:29 PM
>To: Shapira, Yoav
>Cc: Tomcat Developers List; Garrison, Meg
>Subject: Re: contrib directory
>
>Dear all,
>
>  I'm willing to spend some of my limited free time to collect,
organize
>and maintain these contributed code.
>However, it is very unlikely that I would be ever a committer on this
>project with my OS/2 launchers.
>So, as Yoav said, we could find an other committer. Or we could create
>an other project something like tomcat-contrib where we maintain our
>code.
>
>Best regards,
>Leslie Kishalmi
>
>Shapira, Yoav wrote:
>
>>Hi,
>>Yeah, it's gone for now.  The reason is that the maintenance aspect is
>>too hard for the long term.  While I don't doubt the quality of you
(or
>
>>anyone else's) work, nothing is perfect.  It is inevitable that the
>>scripts will need work.  Even if you stay on top of it and keep
>>submitting patches, someone will have to keep checking for them and
>>applying them.
>>
>>I'm not interested in doing that work, and other committers apparently
>>aren't interested enough to even comment on what an appropriate place
>>in CVS might be for these contributions. So I took them out for now.
>>
>>That's not to say they're gone forever.  I can see a couple of
possible
>
>>solutions, and that's why I'm doing this thread on tomcat-dev as
>>opposed to just replying to you personally.
>>
>>One approach is what I'm doing now: contributed stuff is owned by
>>authors (like you) who post it wherever they want (hp.com, personal
web
>
>>sites, whatever), and we link to it from our FAQ and/or wiki pages.
>>This approach solves the long-term maintenance concerns.
>>
>>If this was a one-time effort, I would have done it and we'd be all
set
>
>>by now.  But it's not, and I just don't have the bandwidth to work it
>>;( Another approach is for someone else with commit privileges to say
>>they're interested and do what they think is appropriate.  That can
>>happen at any time, I wouldn't stand in their way obviously, as I'm
not
>
>>principally objecting to these contributions.  I just don't have the
>>bandwidth to deal with them at this point.
>>
>>So this issue is not dead.  It's just not going to be in 5.0.30/5.5.4.
>>We might also want to raise it on tomcat-user to see if people have
>>other creative approaches to solving this.
>>
>>
>>
>>>Are you really going to take the contrib directory out?  I was just
>>>about to make a contribution to you via PayPal as a thank you...
>>>
>>>
>>
>>Thank you ;)
>>
>>Yoav Shapira http://www.yoavshapira.com
>>
>>
>>
>>This e-mail, including any attachments, is a confidential business
>communication, and may contain information that is confidential,
>proprietary and/or privileged.  This e-mail is intended only for the
>individual(s) to whom it is addressed, and may not be saved, copied,
>printed, disclosed or used by anyone else.  If you are not the(an)
>intended recipient, please immediately delete this e-mail from your
>computer system and notify the sender.  Thank you.
>>
>>
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to