Re: questions license for site documents
Might it be possible for us to add links to http://jakarta.apache.org/LICENSE from each generated htmls?? I think this would be enough. Use META tag. (e.g. meta name=license value=http://jakarta.apache.org/LICENSE/) Perhaps this can be easily done by editing /xdocs/stylesheets/site.vsl What would you say? -- Tetsuya. ([EMAIL PROTECTED]) On Sun, 29 Feb 2004 10:57:56 + (Subject: questions license for site documents) robert burrell donkin wrote: the generated html does not contain an explicit license just a copyright. am i right in thinking that now it would be better to publish them under the apache license 2? also, am i right in thinking that all the source documentation should have license notices added? - robert - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] http://www.terra-intl.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: news symlinks
I think the best solution would be to have one page with news N days old, and then have a completely separate news archive where news are categorized by month/year/whatever. The former could have news from both Jakarta and elsewhere on the same page, preventing people from having to check two URLs when reading news. The latter could have different categories for Jakarta news and other news. that's probably true but it would require active maintenance to keep it up to date. so, probably some sort of consensus would be needed amongst those who'll be doing this extra work before going ahead. Huh? Surely the news items are entries in a database of some sort, or are you implying that someone actually modifies html files directly?! Having two lists should only be a matter of having two different db queries, e.g. All news from year 2003: SELECT title, time, body FROM news WHERE time='2003-01-01 00:00:00' AND time'2004-01-01 00:00:00' All news from the last month: SELECT title, time, body FROM news WHERE time='NOW() - INTERVAL 1 MONTH maybe it'd be cool to have a complete latest-first index of all news stories in the news index page. that way, not only would it be a useful resource but also it'd be a fixed page for people to book mark. Yes. (Well, it would be cool in the sense that it is cool that you can edit text in a text editor.) - Marcus Sundman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-site2/xdocs/site/news elsewhere-2004-1stHalf.xml
tetsuya 2004/03/01 07:52:53 Modified:docs index.html docs/site/news elsewhere-2004-1stHalf.html xdocsindex.xml xdocs/site/news elsewhere-2004-1stHalf.xml Log: 29 February 2004 - Xalan Java 2.6.0 is available -- Oh, this year is Olympic Games year ... -- Revision ChangesPath 1.378 +1 -0 jakarta-site2/docs/index.html Index: index.html === RCS file: /home/cvs/jakarta-site2/docs/index.html,v retrieving revision 1.377 retrieving revision 1.378 diff -u -r1.377 -r1.378 --- index.html24 Feb 2004 22:58:37 - 1.377 +++ index.html1 Mar 2004 15:52:53 - 1.378 @@ -254,6 +254,7 @@ h4Other news from a href=site/news/news-2004-1stHalf.htmlJakarta/a and a href=site/news/elsewhere-2004-1stHalf.htmlElsewhere/a/h4 ul +lia href=site/news/elsewhere-2004-1stHalf.html#20040229.129 February 2004 - bXalan Java 2.6.0 is available/b/a/li lia href=site/news/news-2004-1stHalf.html#20040224.224 February 2004 - bGeir Magnusson Jr is New Jakarta Chair/b/a/li lia href=site/news/elsewhere-2004-1stHalf.html#20040223.123 February 2004 - bSubversion 1.0.0 Released/b/a/li lia href=site/news/elsewhere-2004-1stHalf.html#20040213.113 February 2004 - bApache Cocoon 2.1.4 Released/b/a/li 1.3 +59 -1 jakarta-site2/docs/site/news/elsewhere-2004-1stHalf.html Index: elsewhere-2004-1stHalf.html === RCS file: /home/cvs/jakarta-site2/docs/site/news/elsewhere-2004-1stHalf.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- elsewhere-2004-1stHalf.html 24 Feb 2004 22:27:13 - 1.2 +++ elsewhere-2004-1stHalf.html 1 Mar 2004 15:52:53 - 1.3 @@ -195,7 +195,64 @@ /td/tr trtd blockquote -a name=20040223.1 +a name=20040229.1 +h329 February 2004 - Xalan Java 2.6.0 is available/h3 +/a +p +The Xalan team is pleased to announce the availability +of Xalan Java 2.6.0. +/p +p +Xalan Java provides XSLT processors for transforming XML +documents into HTML, text, or other XML document types. +The Xalan Java Interpretive processor and the Xalan Java +Compiling processor implement XSL Transformations (XSLT) +Version 1.0, XML Path Language (XPath) Version 1.0, and +Java API for XML Programming (JAXP) Version 1.2. +/p +p +Xalan Java 2.6.0 can be downloaded from one of the Apache +mirrors at a href=http://www.apache.org/dyn/closer.cgi/xml/xalan-j;http://www.apache.org/dyn/closer.cgi/xml/xalan-j/a +/p +p +Updates in this release include: +/p +p +ul +liBug fixes + (see a href=http://xml.apache.org/xalan-j/readme.html;http://xml.apache.org/xalan-j/readme.html/a + for a list of bugs that have been fixed in this + release)/li +liImprovement in translet initialization time./li +liAddition of a translet versioning mechanism./li +liChanges that allow XSLTC to use other DTM + implementations./li +liChanges in the XML Serializer. The serializer + will no longer put a newline after the xml header + tag unless indent=yes. See bugzilla 24304./li +liRename of Xalan Java's xalan:doc-cache-off processing + instruction to xalan-doc-cache-off. This change was + necessary due to a recent change in Xerces. Xerces + has started detecting the Namespace well-formedness + rule that a processing instruction's PITarget must not + contain a colon. The old-style PI will be accepted + provided that the XML parser does not report is as + an error. See bugzilla 26217./li +liEnhancement to XSLTC's URIResolvers and the general + mechanishm to resolve relative URIs. XSLTC is now + compatible with Xalan Interpretive./li +liAddition of a TransformThread sample that + demonstrates how to use different transformers on + different threads and in different modes./li +liUpgrade to Xerces-Java 2.6.2/li +liElimination of enum as a name to allow + compilation under JDK 1.5/li +liDocumentation updates/li +liUpgrade to the Apache Software License Version 2.0/li +/ul +/p +hr noshade=noshade size=1 / +a name=20040223.1 h323 February 2004 - Subversion 1.0.0 Released/h3 /a
cvs commit: jakarta-site2/xdocs/site cvsindex.xml mail2.xml
bodewig 2004/03/01 07:54:53 Modified:docs/site cvsindex.html mail2.html xdocs/site cvsindex.xml mail2.xml Log: Adapt to new Gump infrastructure Revision ChangesPath 1.116 +2 -2 jakarta-site2/docs/site/cvsindex.html Index: cvsindex.html === RCS file: /home/cvs/jakarta-site2/docs/site/cvsindex.html,v retrieving revision 1.115 retrieving revision 1.116 diff -u -r1.115 -r1.116 --- cvsindex.html 18 Feb 2004 13:29:12 - 1.115 +++ cvsindex.html 1 Mar 2004 15:54:53 - 1.116 @@ -287,8 +287,8 @@ jakarta-ecs/a/li lia href=http://cvs.apache.org/viewcvs/jakarta-ecs2/; jakarta-ecs2/a/li -lia href=http://cvs.apache.org/viewcvs/jakarta-gump/; -jakarta-gump/a/li +lia href=http://cvs.apache.org/viewcvs/gump/; +gump/a/li lia href=http://cvs.apache.org/viewcvs/jakarta-jetspeed/; jakarta-jetspeed/a/li lia href=http://cvs.apache.org/viewcvs/jakarta-jetspeed-2/; 1.141 +2 -2 jakarta-site2/docs/site/mail2.html Index: mail2.html === RCS file: /home/cvs/jakarta-site2/docs/site/mail2.html,v retrieving revision 1.140 retrieving revision 1.141 diff -u -r1.140 -r1.141 --- mail2.html18 Feb 2004 13:29:13 - 1.140 +++ mail2.html1 Mar 2004 15:54:53 - 1.141 @@ -563,8 +563,8 @@ p bThe Gump/bbr / bMedium Traffic/b -a href=mailto:[EMAIL PROTECTED]Subscribe/a -a href=mailto:[EMAIL PROTECTED]Unsubscribe/a +a href=mailto:[EMAIL PROTECTED]Subscribe/a +a href=mailto:[EMAIL PROTECTED]Unsubscribe/a a href=./mail.htmlGuidelines/a a href=http://www.mail-archive.com/[EMAIL PROTECTED]/Archive/a /p 1.50 +2 -2 jakarta-site2/xdocs/site/cvsindex.xml Index: cvsindex.xml === RCS file: /home/cvs/jakarta-site2/xdocs/site/cvsindex.xml,v retrieving revision 1.49 retrieving revision 1.50 diff -u -r1.49 -r1.50 --- cvsindex.xml 6 Oct 2003 22:54:25 - 1.49 +++ cvsindex.xml 1 Mar 2004 15:54:53 - 1.50 @@ -64,8 +64,8 @@ jakarta-ecs/a/li lia href=http://cvs.apache.org/viewcvs/jakarta-ecs2/; jakarta-ecs2/a/li -lia href=http://cvs.apache.org/viewcvs/jakarta-gump/; -jakarta-gump/a/li +lia href=http://cvs.apache.org/viewcvs/gump/; +gump/a/li lia href=http://cvs.apache.org/viewcvs/jakarta-jetspeed/; jakarta-jetspeed/a/li lia href=http://cvs.apache.org/viewcvs/jakarta-jetspeed-2/; 1.82 +2 -2 jakarta-site2/xdocs/site/mail2.xml Index: mail2.xml === RCS file: /home/cvs/jakarta-site2/xdocs/site/mail2.xml,v retrieving revision 1.81 retrieving revision 1.82 diff -u -r1.81 -r1.82 --- mail2.xml 22 Jan 2004 21:01:07 - 1.81 +++ mail2.xml 1 Mar 2004 15:54:53 - 1.82 @@ -293,8 +293,8 @@ p bThe Gump/bbr/ bMedium Traffic/b -a href=mailto:[EMAIL PROTECTED]Subscribe/a -a href=mailto:[EMAIL PROTECTED]Unsubscribe/a +a href=mailto:[EMAIL PROTECTED]Subscribe/a +a href=mailto:[EMAIL PROTECTED]Unsubscribe/a a href=./mail.htmlGuidelines/a a href=http://www.mail-archive.com/[EMAIL PROTECTED]/Archive/a /p - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: questions license for site documents
Am 01.03.2004 um 12:53 schrieb Tetsuya Kitahata: Use META tag. (e.g. meta name=license value=http://jakarta.apache.org/LICENSE/) Perhaps this can be easily done by editing /xdocs/stylesheets/site.vsl What would you say? If anything, that should be: link rel=license href=http://jakarta.apache.org/LICENSE; (See http://tantek.com/log/2004/02.html#d25t1805) Cheers, Chris -- Christopher Lenz /=/ cmlenz at gmx.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Proposal: Jakarta HiveMind Project
Proposal for Jakarta HiveMind Project (0) Rationale HiveMind is a simple framework for creating pluggable, configurable, reusable services. Simple: HiveMind is a way to create a network of services in terms of Java interfaces and classes; it cherry picks the most useful ideas from Service Oriented Architectures such as J2EE, JMX and SOAP, but removes the aspects that are typically overkill for most applications, such as service remoteability and language neutrality. HiveMind creates a natural network of related services and configuration data, all operating within a single JVM. Pluggable: HiveMind enforces a complete separation of service definition and implementation. This is manifested by a division of services into an interface definition and a service implementation as well as a split between defining a service (as part of a HiveMind module) and providing the implementation of that service (potentially, in a different module). Configurable: HiveMind integrates a service oriented architecture to a sophisticated configuration architecture; the configuration architecture is adapted from the Eclipse plug-in model, wherein modules may define configuration extension points and multiple modules may provide contributions to those extension points. Reusable: HiveMind is a framework and container, but not an application. The HiveMind framework and the services it provides may be easily combined with application-specific services and configurations for use in disparate applications. The API for HiveMind allows thread-safe, easy access to services and configurations with a minimal amount of code. The value-add for HiveMind is not just runtime flexibility: it is overall developer productivity. HiveMind systems will entail less code; key functionality that is frequently an after-thought, such as parsing of XML configuration files, logging of method invocations, and lazy creation of services, is handled by the HiveMind framework in a consistent, robust, and well-documented manner. HiveMind fits into an area that partially overlaps the Apache Avalon project, with significant differences. HiveMind's concept of a distributed configuration is unique among the available service microkernels (Avalon, Keel, Spring, PicoContainer, etc.). Avalon is firmly rooted in a Service Lookup pattern (whereby collaborating services must explicitly, in code, resolve dependencies between each other using a lookup pattern similar to JNDI). HiveMind uses the Dependency Injection pattern, whereby the framework (acting as container) creates connections between services by setting properties of the services (property injection) or making use of particular constructors for the services (constructor injection). HiveMind represents a generous donation of code to the ASF by WebCT (http://www.webct.com). HiveMind originated from internal requirements for a flexible, loosely-coupled configuration management and services framework for WebCT's industry-leading flagship enterprise e-learning product, Vista. Several individuals in WebCT's research and development team in addition to Mr. Howard Lewis Ship contributed to the requirements and concepts behind HiveMind's current set of functionality including Martin Bayly, Diane Bennett, Bill Bilic, Michael Kerr, Prashant Nayak, Bill Richard and Ajay Sharda. HiveMind is already in use as a significant part of Vista. (1) Scope of the package The package shall entail a core framework JAR (containing essential classes and services), a standard library JAR (containing generically useful services), along with ancillary artifacts such as Ant tasks and/or Maven plug-ins and, of course, documentation, all distributed under the Apache Software License. (1.1) Interaction with other packages HiveMind has dependencies on several standard commons packages, including commons-lang and commons-logging. HiveMind makes use of the Javassist bytecode generation library, which is available under the MPL (Mozilla public license). (2) Identify the initial source for the package The initial code base has been developed by Howard M. Lewis Ship within the Jakarta Commons incubator. http://jakarta.apache.org/commons/sandbox/hivemind Note: HiveMind was originally considered for inclusion as part of Jakarta commons. Subsequent research has shown that HiveMind is not a suitable candidate for the commons, and is more appropriate for a top-level Jakarta project. (2.1) Identify the base name for the package org.apache.hivemind (2.2) Identify the coding conventions for this package The code follows a modified version of Sun's standard coding conventions, with the following stylistic changes: - instance variables are prefixed with an underscore - a newline is inserted before all braces (3) Identify any Jakarta resources to be created (3.1) mailing lists [EMAIL PROTECTED] -- User discussions [EMAIL PROTECTED] -- Developer discussions and CVS update notifications (3.2) CVS
Re: news symlinks
On 1 Mar 2004, at 12:15, Marcus Sundman wrote: I think the best solution would be to have one page with news N days old, and then have a completely separate news archive where news are categorized by month/year/whatever. The former could have news from both Jakarta and elsewhere on the same page, preventing people from having to check two URLs when reading news. The latter could have different categories for Jakarta news and other news. that's probably true but it would require active maintenance to keep it up to date. so, probably some sort of consensus would be needed amongst those who'll be doing this extra work before going ahead. Huh? Surely the news items are entries in a database of some sort, or are you implying that someone actually modifies html files directly?! the web site is almost all static. jakarta (and most of the apache stuff) is generated using anakia from xml source by volunteers on their own machines and then committed into CVS. a major reason for this is that (until recently) the apache website ran on a very low specification machine (infrastructure's httpd gurus could even make a pig fly ;). we now have a better web server but running a lot of dynamic content on it would probably be problematic. IIRC there was talk (in infrastructure) about being able to loan some better machines from sponsors on which jakarta (and the other ASF projects) could run dynamic content but i'm no longer in the infrastructure loop so now would be good time for better informed people to jump in... maybe it'd be cool to have a complete latest-first index of all news stories in the news index page. that way, not only would it be a useful resource but also it'd be a fixed page for people to book mark. Yes. (Well, it would be cool in the sense that it is cool that you can edit text in a text editor.) cool in the sense of a-useful-resource-that-jakartaens-might-feel-motivated-to-maintain. anyone else have any opinions on this? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: questions license for site documents
i've had a quick google and i'm not sure that there's a consensus out there on this. i like the idea of modifying the .vsl file and i'd be inclined to add both formulations. maybe this would be a good question to raise on community... - robert On 1 Mar 2004, at 17:25, Christopher Lenz wrote: Am 01.03.2004 um 12:53 schrieb Tetsuya Kitahata: Use META tag. (e.g. meta name=license value=http://jakarta.apache.org/LICENSE/) Perhaps this can be easily done by editing /xdocs/stylesheets/site.vsl What would you say? If anything, that should be: link rel=license href=http://jakarta.apache.org/LICENSE; (See http://tantek.com/log/2004/02.html#d25t1805) Cheers, Chris -- Christopher Lenz /=/ cmlenz at gmx.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-site2/xdocs/site legal.xml
tetsuya 2004/03/01 14:38:54 Modified:docs/site legal.html xdocs/site legal.xml Log: Added Legal notice -- Link to Apache License 2.0 Revision ChangesPath 1.80 +16 -0 jakarta-site2/docs/site/legal.html Index: legal.html === RCS file: /home/cvs/jakarta-site2/docs/site/legal.html,v retrieving revision 1.79 retrieving revision 1.80 diff -u -r1.79 -r1.80 --- legal.html18 Feb 2004 13:29:13 - 1.79 +++ legal.html1 Mar 2004 22:38:54 - 1.80 @@ -210,6 +210,22 @@ /td/tr trtdbr//td/tr /table +table border=0 cellspacing=0 cellpadding=2 width=100% + trtd bgcolor=#525D76 +font color=#ff face=arial,helvetica,sanserif + a name=The Apache LicensestrongThe Apache License/strong/a +/font + /td/tr + trtd +blockquote +p +All software produced by The Apache Software Foundation or any of its projects or subjects is licensed according to the terms of a href=http://www.apache.org/licenses/LICENSE-2.0;Apache License, Version 2.0 (current) /a. +/p +/blockquote +/p + /td/tr + trtdbr//td/tr +/table /td /tr 1.7 +8 -0 jakarta-site2/xdocs/site/legal.xml Index: legal.xml === RCS file: /home/cvs/jakarta-site2/xdocs/site/legal.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- legal.xml 24 Jan 2004 01:43:34 - 1.6 +++ legal.xml 1 Mar 2004 22:38:54 - 1.7 @@ -28,6 +28,14 @@ /section + section name=The Apache License + +p +All software produced by The Apache Software Foundation or any of its projects or subjects is licensed according to the terms of a href=http://www.apache.org/licenses/LICENSE-2.0;Apache License, Version 2.0 (current) /a. +/p + + /section + /body /document - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: questions license for site documents
On Mon, 1 Mar 2004 22:24:02 + robert burrell donkin wrote: i've had a quick google and i'm not sure that there's a consensus out there on this. i like the idea of modifying the .vsl file and i'd be inclined to add both formulations. maybe this would be a good question to raise on community... Go ahead. I suspect it that we should modify site.vsl in either case. :-) If we decide to modify all the xml files in /xdocs/, appending link rel=license href=http://jakarta.apache.org/LICENSE/ line would be more practical ... under /document/properties/ element. (generated htmls should have meta tag, link tag or something equivalent) -- Tetsuya. ([EMAIL PROTECTED]) - robert On 1 Mar 2004, at 17:25, Christopher Lenz wrote: Am 01.03.2004 um 12:53 schrieb Tetsuya Kitahata: Use META tag. (e.g. meta name=license value=http://jakarta.apache.org/LICENSE/) Perhaps this can be easily done by editing /xdocs/stylesheets/site.vsl What would you say? If anything, that should be: link rel=license href=http://jakarta.apache.org/LICENSE; (See http://tantek.com/log/2004/02.html#d25t1805) Cheers, Chris -- Christopher Lenz /=/ cmlenz at gmx.de - Tetsuya Kitahata -- Terra-International, Inc. E-mail: [EMAIL PROTECTED] http://www.terra-intl.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-site2/xdocs index.xml
tetsuya 2004/03/01 15:37:27 Modified:docs index.html xdocsindex.xml Log: Apache Software Foundation = The Apache Software Foundation In the eyes of the law, we should append The. Revision ChangesPath 1.379 +2 -2 jakarta-site2/docs/index.html Index: index.html === RCS file: /home/cvs/jakarta-site2/docs/index.html,v retrieving revision 1.378 retrieving revision 1.379 diff -u -r1.378 -r1.379 --- index.html1 Mar 2004 15:52:53 - 1.378 +++ index.html1 Mar 2004 23:37:27 - 1.379 @@ -206,7 +206,7 @@ br /Related projects have their own project management, developers, committers, their own websites and mailing lists. /p p -strongTo catch up with the major releases and important information from The Jakarta Project, we recommend you to a href=mailto:[EMAIL PROTECTED]subscribe/a to mailing list for the a href=./site/mail2.html#AnnouncementAnnouncements/a. To keep informed about the news from Apache Software Foundation and its projects, please a href=mailto:[EMAIL PROTECTED]subscribe/a to a href=http://www.apache.org/foundation/mailinglists.html#foundation-announce;Apache Announcement List/a as well./strong +strongTo catch up with the major releases and important information from The Jakarta Project, we recommend you to a href=mailto:[EMAIL PROTECTED]subscribe/a to mailing list for the a href=./site/mail2.html#AnnouncementAnnouncements/a. To keep informed about the news from The Apache Software Foundation and its projects, please a href=mailto:[EMAIL PROTECTED]subscribe/a to a href=http://www.apache.org/foundation/mailinglists.html#foundation-announce;Apache Announcement List/a as well./strong /p p strongAll Jakarta product support/strong is provided through the subproject @@ -216,7 +216,7 @@ before asking our volunteers to donate additional time and energy to your project. /p p -Jakarta is a project of The Apache Software Foundation(ASF), and like all Apache Projects, encourages a collaborative, consensus-based +Jakarta is a project of The Apache Software Foundation (ASF), and like all Apache Projects, encourages a collaborative, consensus-based development process, offers an open and pragmatic a href=http://www.apache.org/foundation/licence-FAQ.html;software license/a, and strives to create software of the highest quality. br / 1.316 +2 -2 jakarta-site2/xdocs/index.xml Index: index.xml === RCS file: /home/cvs/jakarta-site2/xdocs/index.xml,v retrieving revision 1.315 retrieving revision 1.316 diff -u -r1.315 -r1.316 --- index.xml 1 Mar 2004 15:52:53 - 1.315 +++ index.xml 1 Mar 2004 23:37:27 - 1.316 @@ -22,7 +22,7 @@ br/Related projects have their own project management, developers, committers, their own websites and mailing lists. /p p -strongTo catch up with the major releases and important information from The Jakarta Project, we recommend you to a href=mailto:[EMAIL PROTECTED]subscribe/a to mailing list for the a href=./site/mail2.html#AnnouncementAnnouncements/a. To keep informed about the news from Apache Software Foundation and its projects, please a href=mailto:[EMAIL PROTECTED]subscribe/a to a href=http://www.apache.org/foundation/mailinglists.html#foundation-announce;Apache Announcement List/a as well./strong +strongTo catch up with the major releases and important information from The Jakarta Project, we recommend you to a href=mailto:[EMAIL PROTECTED]subscribe/a to mailing list for the a href=./site/mail2.html#AnnouncementAnnouncements/a. To keep informed about the news from The Apache Software Foundation and its projects, please a href=mailto:[EMAIL PROTECTED]subscribe/a to a href=http://www.apache.org/foundation/mailinglists.html#foundation-announce;Apache Announcement List/a as well./strong /p p strongAll Jakarta product support/strong is provided through the subproject @@ -33,7 +33,7 @@ /p p -Jakarta is a project of The Apache Software Foundation(ASF), and like all Apache Projects, encourages a collaborative, consensus-based +Jakarta is a project of The Apache Software Foundation (ASF), and like all Apache Projects, encourages a collaborative, consensus-based development process, offers an open and pragmatic a href=http://www.apache.org/foundation/licence-FAQ.html;software license/a, and strives to create software of the highest quality. br/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: questions license for site documents
Quoting Tetsuya Kitahata [EMAIL PROTECTED]: On Mon, 1 Mar 2004 22:24:02 + robert burrell donkin wrote: i've had a quick google and i'm not sure that there's a consensus out there on this. i like the idea of modifying the .vsl file and i'd be inclined to add both formulations. maybe this would be a good question to raise on community... Go ahead. I suspect it that we should modify site.vsl in either case. :-) If we decide to modify all the xml files in /xdocs/, appending link rel=license href=http://jakarta.apache.org/LICENSE/ line would be more practical ... under /document/properties/ element. (generated htmls should have meta tag, link tag or something equivalent) The instructions at the very end of http://www.apache.org/licenses/LICENSE-2.0.html describe *exactly* what to do to documentation files, and adding a link in the manner you described is the wrong answer. Instead, you should enclose the same boilerplate text at the top of each such document that is included at the top of Java sources, enclosed in the appropriate comment characters for your format (i.e. for XML, surround by !--. and --, for properties files, prefix by #, and so on). -- Tetsuya. ([EMAIL PROTECTED]) Craig McClanahan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
