Re: [DOC] Table of Contents
Punky Tse wrote: 3) How about putting all the installation and configuration of Tomcat standalone first, and then followed by some chapters (advanced topics) about Running Tomcat behind web servers? It's already organized that way. See the first paragraph of the editorial notes: I think there should be a chapter or series of chapters on installing Tomcat standalone, that covers *everything* or almost everything start-to-finish. Then we also need separate chapters for installing behind each Web server. Then come chapters on administration and advanced configuration issues. I have a feeling you may have missed the attachment. See the post I just made for the latest one (in much detail). Alex, What I mean is to swap Part II with Part III like below: I. Standalone Installation Guide II. Deploying and Configuring, or Tomcat Administrator's Guide III. Installation Behind a Web Server Guide IV. Performance Tuning Guide V. Tomcat Developer's Guide (writing code for Tomcat itself) I treat Installation Behind a Web Server Guide as advanced topics. For general tomcat users, they should be more interested in configuring Tomcat than in making it running behind web server. Punky I agree with you on the motivation (that behind is an advanced topic), but I don't think that means we should automatically put it behind :-) the admin guide. Instead, someone reading start to finish should be able to get an installation running -- perhaps skipping the Apache part if they need to -- *then* they can play around with administering what they've got. It's a judgement call, and if we make them separate docs, then reordering is trivial. -- Alex Chaffee mailto:[EMAIL PROTECTED] jGuru - Java News and FAQs http://www.jguru.com/alex/ Creator of Gamelan http://www.gamelan.com/ Founder of Purple Technology http://www.purpletech.com/ Curator of Stinky Art Collective http://www.stinky.com/
RE: [DOC] Table of Contents
I'm missing a very important one : servlet debugging. All the development environments support jps debugging, but servlet debugging is still a pain.. So that could need some explenation.. Mvgr, Martin -Original Message- From: Alex Chaffee [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 10, 2001 4:37 AM To: [EMAIL PROTECTED] Subject: [DOC] Table of Contents OK, at Craig's request, here's the current Table of Contents for Tomcat docs. (I wrote a program to convert *** to 1.2.3. format so it's easier to read.) It just occured to me that maybe the TOC will be applicable to both versions (3 vs 4), even though the content of each chapter will be completely different. I think there's actually value in synchronizing the TOCs of two different books, though maybe I'm just being weird :-) -- Alex Chaffee mailto:[EMAIL PROTECTED] jGuru - Java News and FAQs http://www.jguru.com/alex/ Creator of Gamelan http://www.gamelan.com/ Founder of Purple Technology http://www.purpletech.com/ Curator of Stinky Art Collective http://www.stinky.com/
Re: [DOC] Table of Contents
Martin van den Bemt wrote: I'm missing a very important one : servlet debugging. All the development environments support jps debugging, but servlet debugging is still a pain.. So that could need some explenation.. See http://www.jguru.com/faq/view.jsp?EID=158 I've added it to the TOC. -- Alex Chaffee mailto:[EMAIL PROTECTED] jGuru - Java News and FAQs http://www.jguru.com/alex/ Creator of Gamelan http://www.gamelan.com/ Founder of Purple Technology http://www.purpletech.com/ Curator of Stinky Art Collective http://www.stinky.com/
Re: [DOC] Table of Contents
3) How about putting all the installation and configuration of Tomcat standalone first, and then followed by some chapters (advanced topics) about Running Tomcat behind web servers? It's already organized that way. See the first paragraph of the editorial notes: I think there should be a chapter or series of chapters on installing Tomcat standalone, that covers *everything* or almost everything start-to-finish. Then we also need separate chapters for installing behind each Web server. Then come chapters on administration and advanced configuration issues. I have a feeling you may have missed the attachment. See the post I just made for the latest one (in much detail). Alex, What I mean is to swap Part II with Part III like below: I. Standalone Installation Guide II. Deploying and Configuring, or Tomcat Administrator's Guide III. Installation Behind a Web Server Guide IV. Performance Tuning Guide V. Tomcat Developer's Guide (writing code for Tomcat itself) I treat Installation Behind a Web Server Guide as advanced topics. For general tomcat users, they should be more interested in configuring Tomcat than in making it running behind web server. Punky
Re: Copyright issues (was Re: DOC: Table of Contents)
For Apache projects, documentation is licensed under the same license as the code (i.e. documentation is software). If you check it in to an Apache repository, it needs to have the Apache license (including the Apache copyright on it). Of course, that also gives you the right to use the docs under the same terms as you can use the software. Note that discussion of GPL licensing for docs isn't really relevant to Tomcat documentation. Craig On Mon, 9 Jul 2001, Alex Fernández wrote: Hi Alex! Alex Chaffee wrote: A note on copyright: I'm claiming copyright for this document, since I may use parts of it to write articles or books, and I haven't done the research on what it means to post text (as opposed to code) into an Apache project. I'd contribute it explicitly as open source if I were sure I'd keep my rights to use it too. If anyone can enlighten me on this topic, please respond with a separate subject line (like Copyrights) so we can keep discussions of copyright separate from discussions of the table of contents itself. The copyright will not prevent other Apache contributors from using or editing it or adding it to the code base -- that is, I want to preserve *my* right to use it in a non-Apache context, but also to grant Apache the right to use it too. If that's even possible. I'm confused. On www.gnu.org you can read the following: --- Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001 Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. Updated: $Date: 2001/06/29 17:42:09 $ $Author: rms $ --- For all I know, (c) in software is not essentially different from (c) issues in text. Of course, the concept has been borrowed from there, otherwise we would use patents. In fact, you can copyleft a book, or BSD-like-license an essay. But I don't know much anyway. Perhaps the following link would be useful: http://www.gnu.org/philosophy/nonsoftware-copyleft.html Un saludo, Alex.
Copyright issues (was Re: DOC: Table of Contents)
Hi Alex! Alex Chaffee wrote: A note on copyright: I'm claiming copyright for this document, since I may use parts of it to write articles or books, and I haven't done the research on what it means to post text (as opposed to code) into an Apache project. I'd contribute it explicitly as open source if I were sure I'd keep my rights to use it too. If anyone can enlighten me on this topic, please respond with a separate subject line (like Copyrights) so we can keep discussions of copyright separate from discussions of the table of contents itself. The copyright will not prevent other Apache contributors from using or editing it or adding it to the code base -- that is, I want to preserve *my* right to use it in a non-Apache context, but also to grant Apache the right to use it too. If that's even possible. I'm confused. On www.gnu.org you can read the following: --- Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001 Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. Updated: $Date: 2001/06/29 17:42:09 $ $Author: rms $ --- For all I know, (c) in software is not essentially different from (c) issues in text. Of course, the concept has been borrowed from there, otherwise we would use patents. In fact, you can copyleft a book, or BSD-like-license an essay. But I don't know much anyway. Perhaps the following link would be useful: http://www.gnu.org/philosophy/nonsoftware-copyleft.html Un saludo, Alex.
