incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r446955 - in /incubator/public/trunk: site-author/guides/proposal.xml site-author/style/style.css site-publish/guides/proposal.html site-publish/style/style.css
Date Sat, 16 Sep 2006 21:31:42 GMT
Author: rdonkin
Date: Sat Sep 16 14:31:42 2006
New Revision: 446955

URL: http://svn.apache.org/viewvc?view=rev&rev=446955
Log:
Cosmetic improvements. Replaced abuse of blockquote by note and source elements. Reformated preformated example code so that the different sections all have the same size. Tweaked the style sheet so that notes are a little more obviously different from source.

Modified:
    incubator/public/trunk/site-author/guides/proposal.xml
    incubator/public/trunk/site-author/style/style.css
    incubator/public/trunk/site-publish/guides/proposal.html
    incubator/public/trunk/site-publish/style/style.css

Modified: incubator/public/trunk/site-author/guides/proposal.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/proposal.xml?view=diff&rev=446955&r1=446954&r2=446955
==============================================================================
--- incubator/public/trunk/site-author/guides/proposal.xml (original)
+++ incubator/public/trunk/site-author/guides/proposal.xml Sat Sep 16 14:31:42 2006
@@ -164,18 +164,18 @@
       <p>
 In the following sections:
       </p>
-      <blockquote>
-      <p>
+      <note>
+      	<p>
 Commentary is thus.
-      </p>
-      <p>
-<pre>Examples are thus.</pre>
-      </p>
-      </blockquote>
+		</p>
+      </note>
+      <source>
+Examples are thus.
+      </source>
       <section id='template'><title>Template</title>
 
        <section id='template-abstract'><title>Abstract</title>
-       <blockquote>
+       <note>
 <p>
 A short descriptive summary of the
 project. A short paragraph, ideally one sentence in length.
@@ -185,37 +185,36 @@
 as the first paragraph on the podling <a href='website.html'>web site</a> 
 and in the <a href='http://projects.apache.org/create.html'>DOAP</a> document.
 </p>
-<pre>
+	</note>
+<source>
 Examples:
 
   Geronimo will be a J2EE compliant container.
        
-  Heraldry will develop technologies around the emerging  
-    user-centric identity space.
+  Heraldry will develop technologies around the emerging user-centric 
+  identity space.
            
   Yoko will be a CORBA server.
-</pre>
-       </blockquote>
+</source>
         </section>
         <section id='template-proposal'><title>Proposal</title>
-        <blockquote>
+        <note>
 <p>
 A lengthier description of the proposal. Should be reasonably declarative.
 More discursive material should be included in the <a href='#template-rationale'>rationale</a>
 (or other later sections).
 </p>
-<pre>
+		</note>
+<source>
 Example (XAP):
-  XAP is to provide an XML-based declarative framework 
-  for building, deploying and maintaining rich, interactive, 
-  Ajax-powered web applications. A basic principal of XAP 
-  is to leverage existing Ajax 
+  XAP is to provide an XML-based declarative framework for building, 
+  deploying and maintaining rich, interactive, Ajax-powered web 
+  applications. A basic principal of XAP is to leverage existing Ajax
   ...
-</pre>
-        </blockquote>
+</source>
         </section>
         <section id='template-background'><title>Background</title>
-        <blockquote>
+        <note>
 <p>
 Provides context for those unfamiliar with the problem space and history. 
 </p><p>
@@ -226,36 +225,36 @@
 This content should be capable of being safely ignored by domain experts.
 It should probably find an eventual home on the Podling website.
 </p>
-<pre>
+		</note>
+<source>
 Example (Heraldry):
-  To provide some background, the Higgins Project is being actively
+  To provide some background, the Higgins Project is being actively 
   developed within Eclipse and is a framework that will enable users
-  and enterprises to integrate identity, profile, and relationship 
+  and enterprises to integrate identity, profile, and relationship
   information across multiple systems. Using context providers, 
-  existing and new systems such as directories, collaboration spaces, 
+  existing and new systems such as directories, collaboration spaces
   ...
-</pre>
-        </blockquote>
+</source>
         </section>
         <section id='template-rationale'><title>Rationale</title>
-        <blockquote>
+        <note>
 <p>
 Explains why this project needs to exist and why should it be adopted by Apache.
 This is the right place for discursive material.
 </p>
-<pre>
+		</note>
+<source>
 Example (Beehive):
-  There is a strong need for a cohesive, easy-to-use programming model 
-  for building J2EE applications. Developers new to Java are forced to 
-  learn a myriad of APIs just to build simple applications; advanced J2EE
-  developers are forced to write tedious plumbing code; and tools authors
-  are limited in what they can do to simplify the experience due to the 
-  underlying complexity.
-</pre>
-        </blockquote>
+  There is a strong need for a cohesive, easy-to-use programming model
+  for building J2EE applications. Developers new to Java are forced to
+  learn a myriad of APIs just to build simple applications; advanced 
+  J2EE developers are forced to write tedious plumbing code; and tools
+  authors are limited in what they can do to simplify the experience 
+  due to the underlying complexity.
+</source>
         </section>
         <section id='template-initial-goals'><title>Initial Goals</title>
-        	<blockquote>
+        	<note>
 <p>
 A complex proposal (involving multiple existing code bases, for example)
 may cause concerns about its practicality. A good way
@@ -265,22 +264,20 @@
 <p>
 Many projects will not need this section.
 </p>
-<pre>
+			</note>
+<source>
 Example (Heraldry):
-  * Expansion of Yadis and OpenID libraries into additional
-     languages beyond the existing Python, Ruby, Perl, and 
-     PHP libraries
-  * OpenID authentication specification revision to fix known
-     security considerations, investigate compatibility with 
-     the DIX IETF proposal, describe Yadis integration, and 
-     allow either an URL or XRI be used as the End User's 
-     Identifier
-   ...
-</pre>
-        	</blockquote>
+  * Expansion of Yadis and OpenID libraries into additional languages 
+    beyond the existing Python, Ruby, Perl, and PHP libraries
+  * OpenID authentication specification revision to fix known security
+    considerations, investigate compatibility with the DIX IETF 
+    proposal, describe Yadis integration, and allow either an URL or 
+    XRI be used as the End User's Identifier
+    ...
+</source>
         </section>
         <section id='template-current-status'><title>Current Status</title>
-        	<blockquote>
+        	<note>
 <p>
 This section (and the contained topics) describes
 the candidate's current status and development practices.
@@ -295,9 +292,9 @@
 </p><p>
 Some proposals name this section <em>criteria</em> (though the term is a little misleading).
 </p>
-        	</blockquote>
+        	</note>
         <section id='template-meritocracy'><title>Meritocracy</title>
-        	<blockquote>
+        	<note>
 	     <p>
 Apache is a 
 <a href='http://www.apache.org/foundation/how-it-works.html#meritocracy'>meritocracy</a>. 
@@ -311,28 +308,28 @@
 This is the right place to demonstrate that this process is understood 
 by the proposers.
         </p>
-        <pre>
+        	</note>
+        <source>
 Example (OFBiz):
   OFBiz was originally created by David E. Jones and Andy Zeneski in 
-  May 2001. The project now has committers and users from around the world. 
-  The newer committers of the project joined in subsequent years by initially
-  submitting patches, then having commit privileges for some of the applications, 
-  and then privileges over a larger range of applications
-  ... 
+  May 2001. The project now has committers and users from around the 
+  world. The newer committers of the project joined in subsequent
+  years by initially submitting patches, then having commit privileges
+  for some of the applications, and then privileges over a larger 
+  range of applications...
 
 Example (Beehive):
   We plan to do everything possible to encourage an environment that
-  supports a meritocracy. One of the lessons that the XMLBeans committers 
-  have learned is that meritocracies don't just evolve from good intentions; 
-  they require actively asking the community for help, listing/specifying the 
-  work that needs to be done, and keeping track of and encouraging 
-  members of the community who make any contributions
-  ...
-       </pre>
-    		</blockquote>
+  supports a meritocracy. One of the lessons that the XMLBeans 
+  committers have learned is that meritocracies don't just evolve 
+  from good intentions; they require actively asking the community 
+  for help, listing/specifying the work that needs to be done, and 
+  keeping track of and encouraging members of the community who make 
+  any contributions...
+       </source>
         </section>
         <section id='template-community'><title>Community</title>
-	        <blockquote>
+	        <note>
         <p>
 Apache is interested only in communities. 
 		</p><p>
@@ -340,28 +337,25 @@
 community and have the potential to grow and renew this community by
 attracting new users and developers. Explain how the proposal fits this vision.
         </p>
-<pre>
+        	</note>
+<source>
 Example (Beehive):
   BEA has been building a community around predecessors to this 
-  framework for the last two years. There is currently an active  
-  newsgroup that should help us build a new community at Apache
-  ...
+  framework for the last two years. There is currently an active 
+  newsgroup that should help us build a new community at Apache...
 
 Example (WebWork2):
-  The WebWork 2 community has a strong following with active 
-  mailing lists and forums
-  ...
+  The WebWork 2 community has a strong following with active mailing
+  lists and forums...
 
 Example (WADI):
-  The need for a full service clustering and caching component in the 
+  The need for a full service clustering and caching component in the
   open source is tremendous as its use can be applied in many areas, 
-  thus providing the potential for an incredibly large community. 
-  ...
-</pre>
-			</blockquote>
+  thus providing the potential for an incredibly large community...
+</source>
         </section>
         <section id='template-core-developers'><title>Core Developers</title>
-    	    <blockquote>
+    	    <note>
         <p>
 Apache is composed of <a href='http://www.apache.org/foundation/how-it-works.html#hats'>individuals</a>. 
 		</p>
@@ -371,68 +365,67 @@
 This is best done here (and not in that section). This section may be used to discuss 
 the diversity of the core development team.
         </p>
- <pre>
+        	</note>
+ <source>
 Example (ServiceMix)
-  The core developers are a diverse group of developers many of which are 
-  already very experienced open source developers. There is at least one 
-  Apache Member together with a number of other existing Apache Committers 
-  along with folks from various companies. http://servicemix.org/Team
+  The core developers are a diverse group of developers many of which 
+  are already very experienced open source developers. There is at 
+  least one Apache Member together with a number of other existing 
+  Apache Committers along with folks from various companies. 
+  http://servicemix.org/Team
  
 Example (WADI) 
-  WADI was founded by Jules Gosnell in 2004, it now has a strong base of 
-  developers from Geronimo, Castor, OpenEJB, Mojo, Jetty, ActiveCluster, 
-  ActiveMQ, and ServiceMix.
-</pre>
-			</blockquote>
+  WADI was founded by Jules Gosnell in 2004, it now has a strong base
+  of developers from Geronimo, Castor, OpenEJB, Mojo, Jetty, 
+  ActiveCluster, ActiveMQ, and ServiceMix.
+</source>
         </section>
         <section id='template-alignment'><title>Alignment</title>
-        	<blockquote>
+        	<note>
         <p>
 Describe why Apache is a good match for the proposal.
 An opportunity to highlight links with Apache 
 <a href='http://projects.apache.org'>projects</a>
 and <a href='http://www.apache.org/foundation/how-it-works.html'>development philosophy</a>.
         </p>
-<pre>
+        	</note>
+<source>
 Example (Beehive):
-  The initial code base is targeted to run within Tomcat, 
-  but the goal is to allow the framework to run on any 
-  compliant Servlet or J2EE container. The Web services 
-  component, based on JSR-181, will leverage Axis. 
-  The NetUI component builds on top of Struts. The 
-  underlying Controls component framework uses Velocity. 
-  There are other projects that we will need to work with, 
-  such as the Portals and Maven projects.
-</pre>
-			</blockquote>
+  The initial code base is targeted to run within Tomcat, but the goal 
+  is to allow the framework to run on any compliant Servlet or J2EE 
+  container. The Web services component, based on JSR-181, will 
+  leverage Axis. The NetUI component builds on top of Struts. The 
+  underlying Controls component framework uses Velocity. There are 
+  other projects that we will need to work with, such as the Portals 
+  and Maven projects.
+</source>
         </section>
         </section>
         <section id='template-known-risks'><title>Known Risks</title>
-        <blockquote>
+        <note>
 <p>
 An exercise in self-knowledge.
 Risks don't mean that a project is unacceptable. 
 If they are recognized and noted then they can be addressed during incubation. 
 </p>
-        </blockquote>
+        </note>
         <section id='template-orphaned-products'><title>Orphaned products</title>
-        <blockquote>
+        <note>
             <p>
 A public commitment to future development. 
 			</p><p>
 Recruiting a diverse development community and strong user base takes time. 
 Apache needs to be confident that the proposers are committed.
             </p>
-<pre>
+        </note>
+<source>
 Example (Yoko):
-  The contributors are leading vendors in this space.
-  There is no risk of any of the usual warning signs of orphaned 
-  or abandoned code.
-</pre>
-        </blockquote>
+  The contributors are leading vendors in this space. There is no risk
+  of any of the usual warning signs of orphaned or abandoned code.
+</source>
         </section>
         <section id='template-inexperience-with-open-source'><title>Inexperience with Open Source</title>
-        <blockquote>
+        <note>
         <p>
 If the proposal is is based on an existing open source project with a history of open development, 
 then highlight this here.
@@ -449,20 +442,20 @@
 around a closed project and comes with very little understand of the open source space,
 then acknowledge this and demonstrate a willingness to learn.
 		</p>
- <pre>
+		</note>
+<source>
 Example (Cayenne):
   Cayenne was started as an open source project in 2001 and has 
   remained so for 5 years.
 	 
 Example (Beehive):
   Many of the committers have experience working on open source 
-  projects. Five of them have experience as committers on other 
+  projects. Five of them have experience as committers on other
   Apache projects.
- </pre>
-        </blockquote>
+ </source>
         </section>
         <section id='template-homogenuous-developers'><title>Homogenous Developers</title>
-            <blockquote>
+            <note>
                 <p>
 Healthy projects need a mix of developers. Open development requires a commitment 
 to encouraging a diverse mixture. This includes the art of working as part of 
@@ -473,17 +466,17 @@
 But for those projects, a commitment to creating a diverse mix of developers is useful.
 Those projects who already have a mix should take this chance to highlight that they do.
                 </p>
-<pre>
+           </note>
+<source>
 Example (Beehive):
-  The current list of committers includes developers from several different 
-  companies plus many independent volunteers. The committers are geographically 
-  distributed across the U.S., Europe, and Asia. They are experienced with working
-  in a distributed environment.
-</pre>
-            </blockquote>
+  The current list of committers includes developers from several 
+  different companies plus many independent volunteers. The committers 
+  are geographically distributed across the U.S., Europe, and Asia. 
+  They are experienced with working in a distributed environment.
+</source>
         </section>
         <section id='template-reliance-on-salaried-developers'><title>Reliance on Salaried Developers</title>            
-            <blockquote>
+            <note>
                 <p> 
 A project dominated by salaried developers who are interested in the code 
 only whilst they are employed to do so risks its long term health. 
@@ -496,18 +489,18 @@
 This is a right place to indicate the initial balance between salaried developers 
 and volunteers. It's also good to talk about the level of commitment of the developers.
                 </p>
-<pre>
+            </note>
+<source>
 Example (OpenJPA):
-  Most of the developers are paid by their employer to contribute 
-  to this project, but given the anticipation from the Java community 
-  for the a JPA implementation and the committers' sense of ownership 
-  for the code, the project would continue without issue if no salaried 
+  Most of the developers are paid by their employer to contribute to
+  this project, but given the anticipation from the Java community for 
+  the a JPA implementation and the committers' sense of ownership for 
+  the code, the project would continue without issue if no salaried 
   developers contributed to the project.
-</pre>
-            </blockquote>
+</source>
         </section>
         <section id='template-other-producrs'><title>Relationships with Other Apache Products</title>  
-            <blockquote>
+            <note>
                 <p>
 Apache projects should be open to collaboration with other open source projects both 
 within Apache and without. Candidates should be willing to reach outside their own little bubbles.
@@ -524,16 +517,16 @@
 important that the abstract describes accurately the niche. Direct competitors should expect 
 to be asked to summarize architectural differences and similarities to existing projects.
 				</p>
-<pre>
+			</note>
+<source>
 Example (OpenJPA):
   Open JPA will likely be used by Geronimo, requires some Apache 
   products (regexp, commons collections, commons lang, commons pool), 
   and supports Apache commons logging.
-</pre>
-            </blockquote>
+</source>
         </section>
         <section id='template-brand-fascination'><title>A Excessive Fascination with the Apache Brand</title>  
-            <blockquote>
+            <note>
                 <p>
 Concerns have been raised in the past that some projects appear to have been proposed 
 just to generate positive publicity for the proposers. This is the right place
@@ -544,34 +537,34 @@
 with the proposal have - in the past - sort to associate themselves with the Apache brand in
 factually incorrect ways) and promise good conduct for the future.
                 </p>
-<pre>
+            </note>
+<source>
 Example (CeltiXfire):
-  While we expect the Apache brand may help attract more 
-  contributors, our interests in starting this project is based 
-  on the factors mentioned in the Rationale section. However, 
-  we will be sensitive to inadvertent abuse of the Apache brand 
-  and will work with the Incubator PMC and the PRC to ensure 
-  the brand policies are respected.
+  While we expect the Apache brand may help attract more contributors,
+  our interests in starting this project is based on the factors
+  mentioned in the Rationale section. However, we will be sensitive to
+  inadvertent abuse of the Apache brand and will work with the 
+  Incubator PMC and the PRC to ensure the brand policies are respected.
   
 Example (Wicket):
-  The ASF has a strong brand, and that brand is in itself attractive. 
-  However, the developers of Wicket have been quite successful
-  on their own and could continue on that path with no problems
-  at all. We are interested in joining the ASF in order to increase 
-  our contacts and visibility in the open source world. Furthermore, 
-  we have been enthusiastic users of Apache from the earliest hour
+  The ASF has a strong brand, and that brand is in itself attractive.
+  However, the developers of Wicket have been quite successful on 
+  their own and could continue on that path with no problems at all. 
+  We are interested in joining the ASF in order to increase our 
+  contacts and visibility in the open source world. Furthermore, we 
+  have been enthusiastic users of Apache from the earliest hour 
   (remember JServ anyone?), and feel honored at getting the 
   opportunity to join the club.
-</pre>
-            </blockquote>
+</source>
         </section>
         </section>
         <section id='template-documentation'><title>Documentation</title>
-            <blockquote>
+            <note>
                 <p>
 References to further reading material.
                 </p>
-<pre>
+            </note>
+<source>
 Examples (Heraldry):
   [1] Information on Yadis can be found at:
     http://yadis.org 
@@ -584,11 +577,10 @@
   The mailing list for both OpenID and Yadis is located at:
     http://lists.danga.com/mailman/listinfo/yadis
   ...
-</pre>
-            </blockquote>
+</source>
         </section>
         <section id='template-initial-source'><title>Initial Source</title>
-            <blockquote>
+            <note>
 <p>
 Describes the origin of the proposed code base. If the initial code arrives
 from more than one source, this is the right place to outline the different
@@ -596,48 +588,47 @@
 </p><p>
 If there is no initial source, note that here. 
 </p>
-<pre>
+			</note>
+<source>
 Example (Heraldry):
-  OpenID has been in development since the summer of 2005. 
-  It currently has an active community (over 15 million enabled
-  accounts) and libraries in a variety of languages. Additionally
-  it is supported by LiveJournal.com and is continuing to gain 
-  traction in the Open Source Community.
+  OpenID has been in development since the summer of 2005. It currently
+  has an active community (over 15 million enabled accounts) and 
+  libraries in a variety of languages. Additionally it is supported by
+  LiveJournal.com and is continuing to gain traction in the Open 
+  Source Community.
 
-  Yadis has been in development since late 2005 and the 
-  specification has not changed since early 2006. Like OpenID, 
-  it has libraries in various languages and there is a large 
-  overlap between the two communities. The specification is
-  ... 
- </pre>
-             </blockquote>
+  Yadis has been in development since late 2005 and the specification 
+  has not changed since early 2006. Like OpenID, it has libraries in 
+  various languages and there is a large overlap between the two 
+  communities. The specification is... 
+ </source>
         </section>
         <section id='template-ip'><title>Source and Intellectual Property Submission Plan</title>
-            <blockquote>
+            <note>
 <p>
 Complex proposals (typically involving multiple code bases) may find it useful
 to draw up an initial plan for the submission of the code here. 
 Demonstrate that the proposal is practical.
 </p>
-<pre>
+			</note>
+<source>
 Example (Heraldry):
-  * The OpenID specification and content on openid.net from 
-    Brad Fitzpatrick of Six Apart, Ltd. and David Recordon of 
-    VeriSign, Inc.
-  * The domains openid.net and yadis.org from Brad Fitzpatrick 
-     of Six Apart, Ltd. and Johannes Ernst of NetMesh, Inc.
-  * OpenID libraries in Python, Ruby, Perl, PHP, and C# from 
-     JanRain, Inc.
-  ...
+  * The OpenID specification and content on openid.net from Brad 
+    Fitzpatrick of Six Apart, Ltd. and David Recordon of VeriSign, 
+    Inc.
+  * The domains openid.net and yadis.org from Brad Fitzpatrick of 
+    Six Apart, Ltd. and Johannes Ernst of NetMesh, Inc.
+  * OpenID libraries in Python, Ruby, Perl, PHP, and C# from JanRain, 
+    Inc.
+    ...
   * Yadis conformance test suite from NetMesh and VeriSign, Inc.
    
   We will also be soliciting contributions of further plugins and 
   patches to various pieces of Open Source software.
-</pre>
-            </blockquote>
+</source>
         </section>
         <section id='template-external-dependencies'><title>External Dependencies</title>
-            <blockquote>
+            <note>
 <p>
 External dependencies for the initial source is important. Only some external dependencies
 are allowed by Apache <a href='http://www.apache.org/legal/3party.html'>policy</a>. 
@@ -648,30 +639,30 @@
 If the initial source has dependencies which would prevent graduation 
 then this is the right place to indicate how these issues will be resolved.
 </p>
-<pre>
+		  </note>
+<source>
 Example (CeltiXfire):
-  The dependencies all have Apache compatible licenses. These include BSD, 
-  CDDL, CPL, MPL and MIT licensed dependencies.
-</pre>
-            </blockquote>
+  The dependencies all have Apache compatible licenses. These include 
+  BSD, CDDL, CPL, MPL and MIT licensed dependencies.
+</source>
         </section>
         <section id='template-cryptography'><title>Cryptography</title>
-            <blockquote>
+            <note>
 <p>
 If the proposal involves cryptographic code either directly or indirectly,
 Apache needs to know so that the 
 <a href='http://www.apache.org/dev/crypto.html'>relevant paperwork</a> can be obtained.
 </p>
-            </blockquote>
+			</note>
         </section>
         <section id='template-required-resources'><title>Required Resources</title>
-            <blockquote>
+            <note>
 <p>
 Resources that infrastructure will be asked to supply for this project.
 </p>
-            </blockquote>
+            </note>
         <section id='template-mailing-lists'><title>Mailing lists</title>
-            <blockquote>
+            <note>
                 <p>
 The minimum required lists are <em>project</em>-private 
 (for confidential <a href='ppmc.html'>PPMC</a> discussions) 
@@ -701,43 +692,43 @@
 It is conventional to use an all lower case, dash-separated (<code>-</code>)  prefix
 based on the project name. 
                 </p>
-<pre>
+                </note>
+<source>
 Example (Beehive):  
   * beehive-private (with moderated subscriptions)
   * beehive-dev
   * beehive-commits
   * beehive-user
-</pre>
-            </blockquote>
+</source>
         </section>
         <section id='template-subversion-directory'><title>Subversion Directory</title>
-        <blockquote>
+        <note>
         	<p>
 It is conventional to use all lower case, dash-separated (<code>-</code>) directory names.
 The directory should be within the incubator directory space 
 (<a href="http://svn.apache.org/repos/asf/incubator">http://svn.apache.org/repos/asf/incubator</a>).
         	</p>
-<pre>
+       	</note>
+<source>
 Example (OpenJPA):
   https://svn.apache.org/repos/asf/incubator/openjpa
-</pre>
-			</blockquote>
+</source>
         </section>
         <section id='template-issue-tracking'><title>Issue Tracking</title>
-            <blockquote>
+            <note>
                 <p>
 Apache runs <a href='https://issues.apache.org/jira/secure/Dashboard.jspa'>JIRA</a>
 and <a href='http://issues.apache.org/bugzilla/'>Bugzilla</a>. Choose one. Indicate the
 name by which project should be known in the issue tracking system.
                 </p>
-<pre>
+            </note>
+<source>
 Example (OpenJPA):
   JIRA Open-JPA (OPEN-JPA)
-</pre>
-            </blockquote>
+</source>
         </section>
         <section id='template-other-resources'><title>Other Resources</title>
-            <blockquote>
+            <note>
             	<p>
 Describe here any other special infrastructure requirements necessary for the proposal.
 Note that the infrastructure team usually requires a compelling argument
@@ -749,11 +740,11 @@
 The <a href='http://www.apache.org/dev'>infrastructure documentation</a> explains 
 the process.
                 </p>
-                </blockquote>
-            </section>
+            </note>
+        </section>
         </section>
         <section id='template-initial-committers'><title>Initial Committers</title>
-            <blockquote>
+            <note>
                 <p>
 List of committers (stating name and an email address) used to bootstrap the community. 
 Mark each which has submitted a 
@@ -773,7 +764,8 @@
 a brief introduction) or ask them to post to the 
 <a href='lists.html#general+at+incubator.apache.org'>general list</a>.
             </p>
-<pre>
+            </note>
+<source>
 Example (OpenJPA):
   Abe White (awhite at bea dot com)
   Marc Prud'hommeaux (mprudhom at bea dot com)
@@ -781,11 +773,10 @@
   ...
   Geir Magnusson Jr (geirm at apache dot org) *
   Craig Russell (clr at apache dot org) *
-</pre>
-            </blockquote>
+</source>
         </section>
         <section id='template-affiliations'><title>Affiliations</title>
-            <blockquote>
+            <note>
                 <p>
 Little bit of a controversial 
 <a href='http://mail-archives.apache.org/mod_mbox/incubator-general/200608.mbox/%3c5c902b9e0608071114i4a63ed67r505691b8d53ce31@mail.gmail.com%3e'>subject</a>.
@@ -806,11 +797,11 @@
 It does not need to be maintained and affiliations of new committers elected 
 after the bootstrap do not need to be listed.
                 </p>
-             </blockquote>
+             </note>
         </section>
         <section id='template-sponsors'><title>Sponsors</title>
             <section id='template-champion'><title>Champion</title>
-                <blockquote>
+                <note>
                 <p>
 The <a href='/incubation/Roles_and_Responsibilities.html#Champion'>Champion</a> is
 a person already associated with Apache who leads the proposal process. It is common 
@@ -820,10 +811,10 @@
 				<p>
 A Champion should be found before the proposal is formally submitted. 
                 </p>
-                </blockquote>
+                </note>
             </section>
             <section id='template-mentors'><title>Nominated Mentors</title>
-                <blockquote>
+                <note>
                     <p>
 Lists <a href='/incubation/Incubation_Policy.html#Mentor'>eligible</a> (and willing)
 individuals nominated as <a href='/incubation/Roles_and_Responsibilities.html#Mentor'>Mentors</a> 
@@ -843,10 +834,10 @@
 at the end of the acceptance process, they have no formal role until the proposal is accepted. 
 But informal enthusiasm from nominee Mentors is taken as a good sign.
 				</p>
-                </blockquote>
+                </note>
             </section>
             <section id='template-sponsoring-entity'><title>Sponsoring Entity</title>
-                <blockquote>
+                <note>
                         <p>
 The <a href='/incubation/Roles_and_Responsibility.html#Sponsor'>Sponsor</a> 
 is the organizational unit within Apache taking responsibility for this proposal.
@@ -865,7 +856,7 @@
 Note that the final destination within the Apache organizational structure
 will be decided upon graduation.
                 </p>
-                </blockquote>
+                </note>
             </section>
         </section>
       </section>

Modified: incubator/public/trunk/site-author/style/style.css
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/style/style.css?view=diff&rev=446955&r1=446954&r2=446955
==============================================================================
--- incubator/public/trunk/site-author/style/style.css (original)
+++ incubator/public/trunk/site-author/style/style.css Sat Sep 16 14:31:42 2006
@@ -59,8 +59,9 @@
 
 .note {
     margin: 1em;
-    padding: 1em;
-    border: 2px solid gray;
+    padding: 0em 1em 0em 1em;
+    border: 2px solid #C0C0FF;
+    background-color: #F3F3FF;
 }
 
 .source {

Modified: incubator/public/trunk/site-publish/guides/proposal.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/proposal.html?view=diff&rev=446955&r1=446954&r2=446955
==============================================================================
--- incubator/public/trunk/site-publish/guides/proposal.html (original)
+++ incubator/public/trunk/site-publish/guides/proposal.html Sat Sep 16 14:31:42 2006
@@ -254,14 +254,17 @@
 <p>
 In the following sections:
       </p>
-<blockquote>
-      <p>
+<div class="note">
+<note>
+      	<p>
 Commentary is thus.
-      </p>
-      <p>
-<pre>Examples are thus.</pre>
-      </p>
-      </blockquote>
+		</p>
+      </note>
+</div>
+<div class="source"><code>
+Examples are thus.
+      </code>
+</div>
 <h3>
    <a name="template">Template</a>
 </h3>
@@ -270,7 +273,8 @@
    <a name="template-abstract">Abstract</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 A short descriptive summary of the
 project. A short paragraph, ideally one sentence in length.
@@ -280,43 +284,48 @@
 as the first paragraph on the podling <a href="website.html">web site</a> 
 and in the <a href="http://projects.apache.org/create.html">DOAP</a> document.
 </p>
-<pre>
+	</note>
+</div>
+<div class="source"><code>
 Examples:
 
   Geronimo will be a J2EE compliant container.
        
-  Heraldry will develop technologies around the emerging  
-    user-centric identity space.
+  Heraldry will develop technologies around the emerging user-centric 
+  identity space.
            
   Yoko will be a CORBA server.
-</pre>
-       </blockquote>
+</code>
+</div>
 </div>
 <h4>
    <a name="template-proposal">Proposal</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 A lengthier description of the proposal. Should be reasonably declarative.
 More discursive material should be included in the <a href="#template-rationale">rationale</a>
 (or other later sections).
 </p>
-<pre>
+		</note>
+</div>
+<div class="source"><code>
 Example (XAP):
-  XAP is to provide an XML-based declarative framework 
-  for building, deploying and maintaining rich, interactive, 
-  Ajax-powered web applications. A basic principal of XAP 
-  is to leverage existing Ajax 
+  XAP is to provide an XML-based declarative framework for building, 
+  deploying and maintaining rich, interactive, Ajax-powered web 
+  applications. A basic principal of XAP is to leverage existing Ajax
   ...
-</pre>
-        </blockquote>
+</code>
+</div>
 </div>
 <h4>
    <a name="template-background">Background</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 Provides context for those unfamiliar with the problem space and history. 
 </p><p>
@@ -327,42 +336,48 @@
 This content should be capable of being safely ignored by domain experts.
 It should probably find an eventual home on the Podling website.
 </p>
-<pre>
+		</note>
+</div>
+<div class="source"><code>
 Example (Heraldry):
-  To provide some background, the Higgins Project is being actively
+  To provide some background, the Higgins Project is being actively 
   developed within Eclipse and is a framework that will enable users
-  and enterprises to integrate identity, profile, and relationship 
+  and enterprises to integrate identity, profile, and relationship
   information across multiple systems. Using context providers, 
-  existing and new systems such as directories, collaboration spaces, 
+  existing and new systems such as directories, collaboration spaces
   ...
-</pre>
-        </blockquote>
+</code>
+</div>
 </div>
 <h4>
    <a name="template-rationale">Rationale</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 Explains why this project needs to exist and why should it be adopted by Apache.
 This is the right place for discursive material.
 </p>
-<pre>
+		</note>
+</div>
+<div class="source"><code>
 Example (Beehive):
-  There is a strong need for a cohesive, easy-to-use programming model 
-  for building J2EE applications. Developers new to Java are forced to 
-  learn a myriad of APIs just to build simple applications; advanced J2EE
-  developers are forced to write tedious plumbing code; and tools authors
-  are limited in what they can do to simplify the experience due to the 
-  underlying complexity.
-</pre>
-        </blockquote>
+  There is a strong need for a cohesive, easy-to-use programming model
+  for building J2EE applications. Developers new to Java are forced to
+  learn a myriad of APIs just to build simple applications; advanced 
+  J2EE developers are forced to write tedious plumbing code; and tools
+  authors are limited in what they can do to simplify the experience 
+  due to the underlying complexity.
+</code>
+</div>
 </div>
 <h4>
    <a name="template-initial-goals">Initial Goals</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 A complex proposal (involving multiple existing code bases, for example)
 may cause concerns about its practicality. A good way
@@ -372,25 +387,26 @@
 <p>
 Many projects will not need this section.
 </p>
-<pre>
+			</note>
+</div>
+<div class="source"><code>
 Example (Heraldry):
-  * Expansion of Yadis and OpenID libraries into additional
-     languages beyond the existing Python, Ruby, Perl, and 
-     PHP libraries
-  * OpenID authentication specification revision to fix known
-     security considerations, investigate compatibility with 
-     the DIX IETF proposal, describe Yadis integration, and 
-     allow either an URL or XRI be used as the End User's 
-     Identifier
-   ...
-</pre>
-        	</blockquote>
+  * Expansion of Yadis and OpenID libraries into additional languages 
+    beyond the existing Python, Ruby, Perl, and PHP libraries
+  * OpenID authentication specification revision to fix known security
+    considerations, investigate compatibility with the DIX IETF 
+    proposal, describe Yadis integration, and allow either an URL or 
+    XRI be used as the End User's Identifier
+    ...
+</code>
+</div>
 </div>
 <h4>
    <a name="template-current-status">Current Status</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 This section (and the contained topics) describes
 the candidate's current status and development practices.
@@ -405,12 +421,14 @@
 </p><p>
 Some proposals name this section <em>criteria</em> (though the term is a little misleading).
 </p>
-        	</blockquote>
+        	</note>
+</div>
 <h5> 
    <a name="template-meritocracy">Meritocracy</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 	     <p>
 Apache is a 
 <a href="http://www.apache.org/foundation/how-it-works.html#meritocracy">meritocracy</a>. 
@@ -424,31 +442,34 @@
 This is the right place to demonstrate that this process is understood 
 by the proposers.
         </p>
-        <pre>
+        	</note>
+</div>
+<div class="source"><code>
 Example (OFBiz):
   OFBiz was originally created by David E. Jones and Andy Zeneski in 
-  May 2001. The project now has committers and users from around the world. 
-  The newer committers of the project joined in subsequent years by initially
-  submitting patches, then having commit privileges for some of the applications, 
-  and then privileges over a larger range of applications
-  ... 
+  May 2001. The project now has committers and users from around the 
+  world. The newer committers of the project joined in subsequent
+  years by initially submitting patches, then having commit privileges
+  for some of the applications, and then privileges over a larger 
+  range of applications...
 
 Example (Beehive):
   We plan to do everything possible to encourage an environment that
-  supports a meritocracy. One of the lessons that the XMLBeans committers 
-  have learned is that meritocracies don't just evolve from good intentions; 
-  they require actively asking the community for help, listing/specifying the 
-  work that needs to be done, and keeping track of and encouraging 
-  members of the community who make any contributions
-  ...
-       </pre>
-    		</blockquote>
+  supports a meritocracy. One of the lessons that the XMLBeans 
+  committers have learned is that meritocracies don't just evolve 
+  from good intentions; they require actively asking the community 
+  for help, listing/specifying the work that needs to be done, and 
+  keeping track of and encouraging members of the community who make 
+  any contributions...
+       </code>
+</div>
 </div>
 <h5> 
    <a name="template-community">Community</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
         <p>
 Apache is interested only in communities. 
 		</p><p>
@@ -456,31 +477,31 @@
 community and have the potential to grow and renew this community by
 attracting new users and developers. Explain how the proposal fits this vision.
         </p>
-<pre>
+        	</note>
+</div>
+<div class="source"><code>
 Example (Beehive):
   BEA has been building a community around predecessors to this 
-  framework for the last two years. There is currently an active  
-  newsgroup that should help us build a new community at Apache
-  ...
+  framework for the last two years. There is currently an active 
+  newsgroup that should help us build a new community at Apache...
 
 Example (WebWork2):
-  The WebWork 2 community has a strong following with active 
-  mailing lists and forums
-  ...
+  The WebWork 2 community has a strong following with active mailing
+  lists and forums...
 
 Example (WADI):
-  The need for a full service clustering and caching component in the 
+  The need for a full service clustering and caching component in the
   open source is tremendous as its use can be applied in many areas, 
-  thus providing the potential for an incredibly large community. 
-  ...
-</pre>
-			</blockquote>
+  thus providing the potential for an incredibly large community...
+</code>
+</div>
 </div>
 <h5> 
    <a name="template-core-developers">Core Developers</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
         <p>
 Apache is composed of <a href="http://www.apache.org/foundation/how-it-works.html#hats">individuals</a>. 
 		</p>
@@ -490,80 +511,90 @@
 This is best done here (and not in that section). This section may be used to discuss 
 the diversity of the core development team.
         </p>
- <pre>
+        	</note>
+</div>
+<div class="source"><code>
 Example (ServiceMix)
-  The core developers are a diverse group of developers many of which are 
-  already very experienced open source developers. There is at least one 
-  Apache Member together with a number of other existing Apache Committers 
-  along with folks from various companies. http://servicemix.org/Team
+  The core developers are a diverse group of developers many of which 
+  are already very experienced open source developers. There is at 
+  least one Apache Member together with a number of other existing 
+  Apache Committers along with folks from various companies. 
+  http://servicemix.org/Team
  
 Example (WADI) 
-  WADI was founded by Jules Gosnell in 2004, it now has a strong base of 
-  developers from Geronimo, Castor, OpenEJB, Mojo, Jetty, ActiveCluster, 
-  ActiveMQ, and ServiceMix.
-</pre>
-			</blockquote>
+  WADI was founded by Jules Gosnell in 2004, it now has a strong base
+  of developers from Geronimo, Castor, OpenEJB, Mojo, Jetty, 
+  ActiveCluster, ActiveMQ, and ServiceMix.
+</code>
+</div>
 </div>
 <h5> 
    <a name="template-alignment">Alignment</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
         <p>
 Describe why Apache is a good match for the proposal.
 An opportunity to highlight links with Apache 
 <a href="http://projects.apache.org">projects</a>
 and <a href="http://www.apache.org/foundation/how-it-works.html">development philosophy</a>.
         </p>
-<pre>
+        	</note>
+</div>
+<div class="source"><code>
 Example (Beehive):
-  The initial code base is targeted to run within Tomcat, 
-  but the goal is to allow the framework to run on any 
-  compliant Servlet or J2EE container. The Web services 
-  component, based on JSR-181, will leverage Axis. 
-  The NetUI component builds on top of Struts. The 
-  underlying Controls component framework uses Velocity. 
-  There are other projects that we will need to work with, 
-  such as the Portals and Maven projects.
-</pre>
-			</blockquote>
+  The initial code base is targeted to run within Tomcat, but the goal 
+  is to allow the framework to run on any compliant Servlet or J2EE 
+  container. The Web services component, based on JSR-181, will 
+  leverage Axis. The NetUI component builds on top of Struts. The 
+  underlying Controls component framework uses Velocity. There are 
+  other projects that we will need to work with, such as the Portals 
+  and Maven projects.
+</code>
+</div>
 </div>
 </div>
 <h4>
    <a name="template-known-risks">Known Risks</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 An exercise in self-knowledge.
 Risks don't mean that a project is unacceptable. 
 If they are recognized and noted then they can be addressed during incubation. 
 </p>
-        </blockquote>
+        </note>
+</div>
 <h5> 
    <a name="template-orphaned-products">Orphaned products</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
             <p>
 A public commitment to future development. 
 			</p><p>
 Recruiting a diverse development community and strong user base takes time. 
 Apache needs to be confident that the proposers are committed.
             </p>
-<pre>
+        </note>
+</div>
+<div class="source"><code>
 Example (Yoko):
-  The contributors are leading vendors in this space.
-  There is no risk of any of the usual warning signs of orphaned 
-  or abandoned code.
-</pre>
-        </blockquote>
+  The contributors are leading vendors in this space. There is no risk
+  of any of the usual warning signs of orphaned or abandoned code.
+</code>
+</div>
 </div>
 <h5> 
    <a name="template-inexperience-with-open-source">Inexperience with Open Source</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
         <p>
 If the proposal is is based on an existing open source project with a history of open development, 
 then highlight this here.
@@ -580,23 +611,26 @@
 around a closed project and comes with very little understand of the open source space,
 then acknowledge this and demonstrate a willingness to learn.
 		</p>
- <pre>
+		</note>
+</div>
+<div class="source"><code>
 Example (Cayenne):
   Cayenne was started as an open source project in 2001 and has 
   remained so for 5 years.
 	 
 Example (Beehive):
   Many of the committers have experience working on open source 
-  projects. Five of them have experience as committers on other 
+  projects. Five of them have experience as committers on other
   Apache projects.
- </pre>
-        </blockquote>
+ </code>
+</div>
 </div>
 <h5> 
    <a name="template-homogenuous-developers">Homogenous Developers</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                 <p>
 Healthy projects need a mix of developers. Open development requires a commitment 
 to encouraging a diverse mixture. This includes the art of working as part of 
@@ -607,20 +641,23 @@
 But for those projects, a commitment to creating a diverse mix of developers is useful.
 Those projects who already have a mix should take this chance to highlight that they do.
                 </p>
-<pre>
+           </note>
+</div>
+<div class="source"><code>
 Example (Beehive):
-  The current list of committers includes developers from several different 
-  companies plus many independent volunteers. The committers are geographically 
-  distributed across the U.S., Europe, and Asia. They are experienced with working
-  in a distributed environment.
-</pre>
-            </blockquote>
+  The current list of committers includes developers from several 
+  different companies plus many independent volunteers. The committers 
+  are geographically distributed across the U.S., Europe, and Asia. 
+  They are experienced with working in a distributed environment.
+</code>
+</div>
 </div>
 <h5> 
    <a name="template-reliance-on-salaried-developers">Reliance on Salaried Developers</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                 <p> 
 A project dominated by salaried developers who are interested in the code 
 only whilst they are employed to do so risks its long term health. 
@@ -633,21 +670,24 @@
 This is a right place to indicate the initial balance between salaried developers 
 and volunteers. It's also good to talk about the level of commitment of the developers.
                 </p>
-<pre>
+            </note>
+</div>
+<div class="source"><code>
 Example (OpenJPA):
-  Most of the developers are paid by their employer to contribute 
-  to this project, but given the anticipation from the Java community 
-  for the a JPA implementation and the committers' sense of ownership 
-  for the code, the project would continue without issue if no salaried 
+  Most of the developers are paid by their employer to contribute to
+  this project, but given the anticipation from the Java community for 
+  the a JPA implementation and the committers' sense of ownership for 
+  the code, the project would continue without issue if no salaried 
   developers contributed to the project.
-</pre>
-            </blockquote>
+</code>
+</div>
 </div>
 <h5> 
    <a name="template-other-producrs">Relationships with Other Apache Products</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                 <p>
 Apache projects should be open to collaboration with other open source projects both 
 within Apache and without. Candidates should be willing to reach outside their own little bubbles.
@@ -664,19 +704,22 @@
 important that the abstract describes accurately the niche. Direct competitors should expect 
 to be asked to summarize architectural differences and similarities to existing projects.
 				</p>
-<pre>
+			</note>
+</div>
+<div class="source"><code>
 Example (OpenJPA):
   Open JPA will likely be used by Geronimo, requires some Apache 
   products (regexp, commons collections, commons lang, commons pool), 
   and supports Apache commons logging.
-</pre>
-            </blockquote>
+</code>
+</div>
 </div>
 <h5> 
    <a name="template-brand-fascination">A Excessive Fascination with the Apache Brand</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                 <p>
 Concerns have been raised in the past that some projects appear to have been proposed 
 just to generate positive publicity for the proposers. This is the right place
@@ -687,37 +730,41 @@
 with the proposal have - in the past - sort to associate themselves with the Apache brand in
 factually incorrect ways) and promise good conduct for the future.
                 </p>
-<pre>
+            </note>
+</div>
+<div class="source"><code>
 Example (CeltiXfire):
-  While we expect the Apache brand may help attract more 
-  contributors, our interests in starting this project is based 
-  on the factors mentioned in the Rationale section. However, 
-  we will be sensitive to inadvertent abuse of the Apache brand 
-  and will work with the Incubator PMC and the PRC to ensure 
-  the brand policies are respected.
+  While we expect the Apache brand may help attract more contributors,
+  our interests in starting this project is based on the factors
+  mentioned in the Rationale section. However, we will be sensitive to
+  inadvertent abuse of the Apache brand and will work with the 
+  Incubator PMC and the PRC to ensure the brand policies are respected.
   
 Example (Wicket):
-  The ASF has a strong brand, and that brand is in itself attractive. 
-  However, the developers of Wicket have been quite successful
-  on their own and could continue on that path with no problems
-  at all. We are interested in joining the ASF in order to increase 
-  our contacts and visibility in the open source world. Furthermore, 
-  we have been enthusiastic users of Apache from the earliest hour
+  The ASF has a strong brand, and that brand is in itself attractive.
+  However, the developers of Wicket have been quite successful on 
+  their own and could continue on that path with no problems at all. 
+  We are interested in joining the ASF in order to increase our 
+  contacts and visibility in the open source world. Furthermore, we 
+  have been enthusiastic users of Apache from the earliest hour 
   (remember JServ anyone?), and feel honored at getting the 
   opportunity to join the club.
-</pre>
-            </blockquote>
+</code>
+</div>
 </div>
 </div>
 <h4>
    <a name="template-documentation">Documentation</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                 <p>
 References to further reading material.
                 </p>
-<pre>
+            </note>
+</div>
+<div class="source"><code>
 Examples (Heraldry):
   [1] Information on Yadis can be found at:
     http://yadis.org 
@@ -730,14 +777,15 @@
   The mailing list for both OpenID and Yadis is located at:
     http://lists.danga.com/mailman/listinfo/yadis
   ...
-</pre>
-            </blockquote>
+</code>
+</div>
 </div>
 <h4>
    <a name="template-initial-source">Initial Source</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 Describes the origin of the proposed code base. If the initial code arrives
 from more than one source, this is the right place to outline the different
@@ -745,54 +793,59 @@
 </p><p>
 If there is no initial source, note that here. 
 </p>
-<pre>
+			</note>
+</div>
+<div class="source"><code>
 Example (Heraldry):
-  OpenID has been in development since the summer of 2005. 
-  It currently has an active community (over 15 million enabled
-  accounts) and libraries in a variety of languages. Additionally
-  it is supported by LiveJournal.com and is continuing to gain 
-  traction in the Open Source Community.
+  OpenID has been in development since the summer of 2005. It currently
+  has an active community (over 15 million enabled accounts) and 
+  libraries in a variety of languages. Additionally it is supported by
+  LiveJournal.com and is continuing to gain traction in the Open 
+  Source Community.
 
-  Yadis has been in development since late 2005 and the 
-  specification has not changed since early 2006. Like OpenID, 
-  it has libraries in various languages and there is a large 
-  overlap between the two communities. The specification is
-  ... 
- </pre>
-             </blockquote>
+  Yadis has been in development since late 2005 and the specification 
+  has not changed since early 2006. Like OpenID, it has libraries in 
+  various languages and there is a large overlap between the two 
+  communities. The specification is... 
+ </code>
+</div>
 </div>
 <h4>
    <a name="template-ip">Source and Intellectual Property Submission Plan</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 Complex proposals (typically involving multiple code bases) may find it useful
 to draw up an initial plan for the submission of the code here. 
 Demonstrate that the proposal is practical.
 </p>
-<pre>
+			</note>
+</div>
+<div class="source"><code>
 Example (Heraldry):
-  * The OpenID specification and content on openid.net from 
-    Brad Fitzpatrick of Six Apart, Ltd. and David Recordon of 
-    VeriSign, Inc.
-  * The domains openid.net and yadis.org from Brad Fitzpatrick 
-     of Six Apart, Ltd. and Johannes Ernst of NetMesh, Inc.
-  * OpenID libraries in Python, Ruby, Perl, PHP, and C# from 
-     JanRain, Inc.
-  ...
+  * The OpenID specification and content on openid.net from Brad 
+    Fitzpatrick of Six Apart, Ltd. and David Recordon of VeriSign, 
+    Inc.
+  * The domains openid.net and yadis.org from Brad Fitzpatrick of 
+    Six Apart, Ltd. and Johannes Ernst of NetMesh, Inc.
+  * OpenID libraries in Python, Ruby, Perl, PHP, and C# from JanRain, 
+    Inc.
+    ...
   * Yadis conformance test suite from NetMesh and VeriSign, Inc.
    
   We will also be soliciting contributions of further plugins and 
   patches to various pieces of Open Source software.
-</pre>
-            </blockquote>
+</code>
+</div>
 </div>
 <h4>
    <a name="template-external-dependencies">External Dependencies</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 External dependencies for the initial source is important. Only some external dependencies
 are allowed by Apache <a href="http://www.apache.org/legal/3party.html">policy</a>. 
@@ -803,39 +856,46 @@
 If the initial source has dependencies which would prevent graduation 
 then this is the right place to indicate how these issues will be resolved.
 </p>
-<pre>
+		  </note>
+</div>
+<div class="source"><code>
 Example (CeltiXfire):
-  The dependencies all have Apache compatible licenses. These include BSD, 
-  CDDL, CPL, MPL and MIT licensed dependencies.
-</pre>
-            </blockquote>
+  The dependencies all have Apache compatible licenses. These include 
+  BSD, CDDL, CPL, MPL and MIT licensed dependencies.
+</code>
+</div>
 </div>
 <h4>
    <a name="template-cryptography">Cryptography</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 If the proposal involves cryptographic code either directly or indirectly,
 Apache needs to know so that the 
 <a href="http://www.apache.org/dev/crypto.html">relevant paperwork</a> can be obtained.
 </p>
-            </blockquote>
+			</note>
+</div>
 </div>
 <h4>
    <a name="template-required-resources">Required Resources</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
 <p>
 Resources that infrastructure will be asked to supply for this project.
 </p>
-            </blockquote>
+            </note>
+</div>
 <h5> 
    <a name="template-mailing-lists">Mailing lists</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                 <p>
 The minimum required lists are <em>project</em>-private 
 (for confidential <a href="ppmc.html">PPMC</a> discussions) 
@@ -865,52 +925,61 @@
 It is conventional to use an all lower case, dash-separated (<code>-</code>)  prefix
 based on the project name. 
                 </p>
-<pre>
+                </note>
+</div>
+<div class="source"><code>
 Example (Beehive):  
   * beehive-private (with moderated subscriptions)
   * beehive-dev
   * beehive-commits
   * beehive-user
-</pre>
-            </blockquote>
+</code>
+</div>
 </div>
 <h5> 
    <a name="template-subversion-directory">Subversion Directory</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
         	<p>
 It is conventional to use all lower case, dash-separated (<code>-</code>) directory names.
 The directory should be within the incubator directory space 
 (<a href="http://svn.apache.org/repos/asf/incubator">http://svn.apache.org/repos/asf/incubator</a>).
         	</p>
-<pre>
+       	</note>
+</div>
+<div class="source"><code>
 Example (OpenJPA):
   https://svn.apache.org/repos/asf/incubator/openjpa
-</pre>
-			</blockquote>
+</code>
+</div>
 </div>
 <h5> 
    <a name="template-issue-tracking">Issue Tracking</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                 <p>
 Apache runs <a href="https://issues.apache.org/jira/secure/Dashboard.jspa">JIRA</a>
 and <a href="http://issues.apache.org/bugzilla/">Bugzilla</a>. Choose one. Indicate the
 name by which project should be known in the issue tracking system.
                 </p>
-<pre>
+            </note>
+</div>
+<div class="source"><code>
 Example (OpenJPA):
   JIRA Open-JPA (OPEN-JPA)
-</pre>
-            </blockquote>
+</code>
+</div>
 </div>
 <h5> 
    <a name="template-other-resources">Other Resources</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
             	<p>
 Describe here any other special infrastructure requirements necessary for the proposal.
 Note that the infrastructure team usually requires a compelling argument
@@ -922,14 +991,16 @@
 The <a href="http://www.apache.org/dev">infrastructure documentation</a> explains 
 the process.
                 </p>
-                </blockquote>
+            </note>
+</div>
 </div>
 </div>
 <h4>
    <a name="template-initial-committers">Initial Committers</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                 <p>
 List of committers (stating name and an email address) used to bootstrap the community. 
 Mark each which has submitted a 
@@ -949,7 +1020,9 @@
 a brief introduction) or ask them to post to the 
 <a href="lists.html#general+at+incubator.apache.org">general list</a>.
             </p>
-<pre>
+            </note>
+</div>
+<div class="source"><code>
 Example (OpenJPA):
   Abe White (awhite at bea dot com)
   Marc Prud'hommeaux (mprudhom at bea dot com)
@@ -957,14 +1030,15 @@
   ...
   Geir Magnusson Jr (geirm at apache dot org) *
   Craig Russell (clr at apache dot org) *
-</pre>
-            </blockquote>
+</code>
+</div>
 </div>
 <h4>
    <a name="template-affiliations">Affiliations</a>
 </h4>
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                 <p>
 Little bit of a controversial 
 <a href="http://mail-archives.apache.org/mod_mbox/incubator-general/200608.mbox/%3c5c902b9e0608071114i4a63ed67r505691b8d53ce31@mail.gmail.com%3e">subject</a>.
@@ -985,7 +1059,8 @@
 It does not need to be maintained and affiliations of new committers elected 
 after the bootstrap do not need to be listed.
                 </p>
-             </blockquote>
+             </note>
+</div>
 </div>
 <h4>
    <a name="template-sponsors">Sponsors</a>
@@ -995,7 +1070,8 @@
    <a name="template-champion">Champion</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                 <p>
 The <a href="/incubation/Roles_and_Responsibilities.html#Champion">Champion</a> is
 a person already associated with Apache who leads the proposal process. It is common 
@@ -1005,13 +1081,15 @@
 				<p>
 A Champion should be found before the proposal is formally submitted. 
                 </p>
-                </blockquote>
+                </note>
+</div>
 </div>
 <h5> 
    <a name="template-mentors">Nominated Mentors</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                     <p>
 Lists <a href="/incubation/Incubation_Policy.html#Mentor">eligible</a> (and willing)
 individuals nominated as <a href="/incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a> 
@@ -1031,13 +1109,15 @@
 at the end of the acceptance process, they have no formal role until the proposal is accepted. 
 But informal enthusiasm from nominee Mentors is taken as a good sign.
 				</p>
-                </blockquote>
+                </note>
+</div>
 </div>
 <h5> 
    <a name="template-sponsoring-entity">Sponsoring Entity</a> 
 </h5> 
 <div class="section-content">
-<blockquote>
+<div class="note">
+<note>
                         <p>
 The <a href="/incubation/Roles_and_Responsibility.html#Sponsor">Sponsor</a> 
 is the organizational unit within Apache taking responsibility for this proposal.
@@ -1056,7 +1136,8 @@
 Note that the final destination within the Apache organizational structure
 will be decided upon graduation.
                 </p>
-                </blockquote>
+                </note>
+</div>
 </div>
 </div>
 </div>

Modified: incubator/public/trunk/site-publish/style/style.css
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/style/style.css?view=diff&rev=446955&r1=446954&r2=446955
==============================================================================
--- incubator/public/trunk/site-publish/style/style.css (original)
+++ incubator/public/trunk/site-publish/style/style.css Sat Sep 16 14:31:42 2006
@@ -59,8 +59,9 @@
 
 .note {
     margin: 1em;
-    padding: 1em;
-    border: 2px solid gray;
+    padding: 0em 1em 0em 1em;
+    border: 2px solid #C0C0FF;
+    background-color: #F3F3FF;
 }
 
 .source {



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message