Quoting "Noel J. Bergman" <[EMAIL PROTECTED]>: > Henri Yandell wrote: > > > If all the PMC's share the same website, who is responsible > > for the website as a global concept. For example, the need > > to do mirrors. > > > If a Jakarta-Site PMC exists, all other PMCs [jakarta sub-project based] > > are accepting the Jakarta Site PMC's oversight over their websites. > > How do you think the Jakarta site works already? The site2 module is just > the "core" Jakarta site. All of the projects already have their own sites > in their own CVS, which are then checked out under the > /www/jakarta.apache.org/$project.
And all of those $project sites are under oversight of the Jakarta PMC. There is no such thing as a "jakarta sub-project based" PMC. > Nothing would have to change, unless a > project *wanted* a new domain, from what I can see. Am I missing your > point? I'm just not seeing the problem. > Although I'm sympathetic to the idea that Jakarta sub-projects who then become TLPs might want to maintain their jakarta.apache.org/$project web site for brand identification purposes, I'm concerned about the potential for external confusion over "who's in charge here". The reality would be that the Jakarta PMC would (correctly) *not* think they had management over that subdirectory of the site, but the legal distinction would be very likely missed by anyone who is visiting. If/when Struts becomes a TLP, I'm going to recommend that we do exactly what Ant, James, and Maven (for example) did: * Maintain a link on the Jakarta home page under "Related" * Install a webserver redirect from <http://jakarta.apache.org/struts> to <http://struts.apache.org>. > --- Noel Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
