I'm all for having a resource that has example configurations, etc. That's a pretty good idea, and one of the reasons I posted my own HOWTOs and started trying to host connector binaries for people to download.
I was only suggesting that it might be faster, easier, and more efficient to integrate with the existing dev and doc team(s), rather than start up yet another disconnected project. For example, the biggest issue (or one of the biggest issues) I see on the list (and I've only been a subscriber since June) is the configuration of Apache + Tomcat using a connector. That alone is three separate projects: Apache Team, Tomcat team, and connector team. Now its being suggested that a separate documentation team/project be started. I don't see how that can help much, when it would make more sense to me to continue and expand upon what is already in progress. There is also the consideration of responsibility, and yes, trust. Let's say a new doc project gets started. Who has access? Who has commit access? Who has the passwords to the site? Who owns the domain name? What happens if that person gets killed by a bus? What happens if one or two people are in charge of the site, and they start hosting banner ads and affiliate links? Who gets the money from that, since arguably the people supplying the content are at least partially responsible for generating the traffic? My point is that the Apache Foundation has a track record, they have the resources already in place, they have the momentum, they have the trust, they have the web space, they are open to suggestion and volunteer contributions, and they have the knowledge base. It makes a lot more sense to me to pitch in and help them out than it does to go off on a tangent and do something separate. John > -----Original Message----- > From: yoom nguyen [mailto:ynguyen@;e-integration.net] > Sent: Friday, October 18, 2002 1:41 PM > To: Tomcat Users List > Subject: Proposal for new Site > > > John > > Are you suggesting that we should use what is already there? > Don't you think it will be crowded for original site. If > folks start to upload and submit different type of deployment > examples > for > different flavor of OS or apps. > > We should reserve the original site for fundamental, basic and release > information and materials. The new site that I proposed would > accommodate a variety of deployment examples that offer from the Open > Source community. > > For example: I am almost certain that someone out there have deployed > what I am currently looking for, a combination of Apache2.0.43, > Tomcat4.1.2 and JK2.2.0.2 on linux platform. If the proposal > site was > up. We can suggest to our user communities that they need and should > share they deployment with other by post a complete and detail > implementation of the (example ->) > www.apache-opensource-implementation- > documentation.com after they done with their deployment. > There will be > someone folks that will not share their work, but most of them will. > > Do a search on google.com. There are dozen of great and excellent > documentation that scattering everyway. We are wasting lot > of our user > communities. They need to get it work and spread the Open Source > technology across the industry. The more users we have the more of > the market share we are going to have. > > One the site up and running, I will need help to manage it as well. > Anyone volunteer to help will have all access and permission to the > machine. > -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
