----- Original Message ----- From: "Henri Yandell" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Friday, April 08, 2005 8:58 PM
Subject: Re: New TLP draft
On Apr 8, 2005 11:19 PM, Bill Barker <[EMAIL PROTECTED]> wrote:
----- Original Message ----- From: "Costin Manolache" <[EMAIL PROTECTED]> To: <tomcat-dev@jakarta.apache.org> Sent: Friday, April 08, 2005 7:23 PM Subject: Re: New TLP draft
> Remy Maucherat wrote: >>> >>> Need to identify just how much of the jakarta-* CVS will go with >>> Tomcat. Watchdog + ServletAPI modules? >> >> >> That's undecided. Would the old projects would remain at Jakarta, or >> would they be covered by the new project ? > > > Why would they remain in jakarta ? They have the same committer list as > tomcat, and are closely related. >
Urm, no. For example I, personally, have no karma for any of
jakarta-servletapi* or jakarta-watchdog*. Also, jakarta-watchdog* are all
dead projects. It's all about who wants to watch the corpse ;-).
A better description is that their committer list is a direct subset of the Tomcat list, and they exist primarily for use by the Tomcat community.
True for servletapi.
Mark Thomas (I think, sorry if it wasn't Mark) explained Watchdog as existing for Tomcat 4 and being dead because Tomcat 5 no longer needed it (or some such). This seems like a pretty clear ownership by Tomcat.
Don't forget Tomcat 3! (except that jakarta-watchdog is hopelessly broken, with no active committers). I don't really have any objection to corpse-watching. We should probably assume jakarta-tools in this case as well (dead project used, AFAIK, only by watchdog).
The ServletAPI modules were (I assume) created for use by Tomcat. Unless we start a project at Apache for hosting JCP spec jars, it seems that a part of the Tomcat community would be the ones writing the servletapi-3.0.jar in 2 years time; so servletapi also seems like it's owned by the Tomcat community.
Other than jakarta-servletapi-3.0 would be an alias for jakarta-servletapi, I agree with moving them to the tomcat PMC oversight. However, they have a separate committer list (for good reason), and this should be preserved.
Going a bit further out; I think it would be fair to say that the Tomcat community are the inheritors of the mod_jserv stuff; but as the last published cvs location for this no longer works, there's nothing concrete to hand off. Just vague ownership of something archived somewhere.
The last version of mod_jserv is already living in jakarta-tomcat. If there is another copy not listed at http://jakarta.apache.org/site/cvsindex.html, I vote to nuke it, since it is even older and less supported than the copy in jakarta-tomcat. Personally, I don't care if the jakarta-tomcat version works or not (since I've finally moved my last webapp off of it :).
Hen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments.
In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
