incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r1232024 - in /incubator/public/trunk: site-author/guides/names.xml site-publish/guides/names.html
Date Mon, 16 Jan 2012 15:22:21 GMT
Author: rdonkin
Date: Mon Jan 16 15:22:21 2012
New Revision: 1232024

URL: http://svn.apache.org/viewvc?rev=1232024&view=rev
Log:
Tightened some language.

Modified:
    incubator/public/trunk/site-author/guides/names.xml
    incubator/public/trunk/site-publish/guides/names.html

Modified: incubator/public/trunk/site-author/guides/names.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/names.xml?rev=1232024&r1=1232023&r2=1232024&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/names.xml [utf-8] (original)
+++ incubator/public/trunk/site-author/guides/names.xml [utf-8] Mon Jan 16 15:22:21 2012
@@ -35,7 +35,6 @@ limitations under the License.
   	<title>The Basics</title>
 	<section>
 	<title>Meet The Apache Branding Team</title>
-	<!-- TODO: Improve introduction before links -->
 <p>
 Names <a href='http://www.apache.org/foundation/marks/#whoweare'>fall</a> within
the responsibilities of the 
 <a href='http://www.apache.org/foundation/'>V.P., Brand Management</a> (and 
@@ -93,11 +92,10 @@ reproducing the content of the NOTICE fi
             <p class='attribution'><a href='http://www.apache.org/licenses/LICENSE-2.0.html#trademarks'>Apache
License, Version 2.0
          	</a></p>
             <p>
-All Apache projects share the Apache License, which issues standard <strong>copy</strong>

+All Apache projects share the Apache License. This issues standard <strong>copy</strong>

 and <strong>patent</strong> rights to 
 downstream consumers. <strong>Trademark</strong> rights for Apache products are
issued and managed independently, 
-beyond the Apache License.
-Apache communities are able to use trademark law to protect their reputation and that of
the 
+beyond the Apache License. This allows Apache communities to use trademark law to protect
their reputation and that of the 
 <a href='http://www.apache.org/foundation/'>Foundation</a>, within the broader
 framework provided by the Brand team.
             </p>
@@ -106,10 +104,11 @@ framework provided by the Brand team.
   
   <section id='naming-hints'>
   <title>What Makes A Name Good</title>
-  <p>Good names for commercial products or <code>UNIX</code> utilities
may work less well for Apache products.
-  Many of our successful open source product names are memorable, unusual and a little 
+  <p>Good names for commercial products or <code>UNIX</code> utilities
have tended to work less well here at Apache.
+  Many successful Apache project names are memorable, unusual and a little 
   <a href='http://www.sdtimes.com/TOP_FIVE_HEAD_SCRATCHINGEST_NAMES_FOR_APACHE_PROJECTS/By_Victoria_Reitano/About_APACHE_and_HADOOP_and_HARMONY_and_MYSQL_and_OODT_and_YAY/35959'>whimsical</a>.
   These qualities are also often good when it comes to securing trademark protection.
+  Have fun. Be creative.
   </p>
   <!-- TODO: Harvest stories behind names -->
   <!-- TODO: Inspiration -->
@@ -117,7 +116,8 @@ framework provided by the Brand team.
   <section><title>Podling Suitable Name Search</title>
     <!-- TODO: rewrite using simpler phrasing -->
   <p>
-The proposal which establishes a new podling includes a (working) name.
+The initial <a href='http://incubator.apache.org/guides/proposal.html'>proposal</a>

+establishes a working name for the new podling.
 Often some discussion and filtering of suitable names happens during the election
 process but this proposed name is <strong>not</strong> final, only <em>provisional</em>.

 The community may choose to change it. Or the community may discover that the name is unsuitable:
@@ -140,7 +140,7 @@ A suitable name search must be successfu
 </p><p>
 Names are an essential part of building a brand and community. 
 Switching names wastes the efforts put into establishing the original name.
-So, it is best to complete this task as soon as possible.
+So complete this task as soon as possible.
 </p>
   
   </section>
@@ -153,7 +153,7 @@ So, it is best to complete this task as 
   <p>
 A suitable name search has public and private elements. 
 The <a href='https://issues.apache.org/jira/browse/PODLINGNAMESEARCH'>tracker</a>
provides the public record.
-Incubator best practice evolves over time, and documentation lags.
+Incubator best practice evolves over time, documentation lags.
 The public records of past searches are a primary source of guidance. 
 Review now the records of previous searches, beginning with the most recent then working
back.
   </p><p>
@@ -196,17 +196,15 @@ Whether the name proved suitable or unsu
          
          <section id='main-sequence'><title>The Main Sequence</title>
          <p>
-Using a <a href='http://outreach.atnf.csiro.au/education/senior/astrophysics/stellarevolution_mainsequence.html'>cosmic</a>
-metaphor, every podling is unique but most fit into a Main Sequence where the processes evolved
-work well (once you give then a chance). For main sequence podlings, most of the bugs should
have been squashed and 
-rough edged documented away. 
-		</p><p>
-In some cases, there may be good reasons for special handling (but not liking the result
is 
-not one of them). Away from the main sequence, process may need to be grown, documentation
is likely be sparse
+Every podling is unique, but using a <a href='http://outreach.atnf.csiro.au/education/senior/astrophysics/stellarevolution_mainsequence.html'>cosmic</a>
+metaphor, most fit into a main sequence. For podlings on the main sequence,
+most of the bugs should have been squashed and rough edges documented away, so expect a smooth
journey. 
+Away from the main sequence, process may need to be grown, documentation is likely be sparse
 and progress less smooth. 
          </p><p>
-This document documents the main sequence. This should be appropriate for most podlings and
represents a well known path.
-If there are good reasons to think that your podling isn't Main Sequence, discuss this with
the
+The main sequence is described. This well known path is
+appropriate for almost all podlings.
+If there are good reasons to think that your podling is a special case, discuss this with
the
 <a href='http://mail-archives.apache.org/mod_mbox/incubator-general/'>Incubator community</a>
 and attempt to reach consensus on the right way forward.
          </p>
@@ -235,7 +233,7 @@ whether anything has been missed. Check 
          <section id='uniqueness-what-and-why'><title>Unique Enough Names</title>
          <p>
 The name needs be unique enough to avoid confusion with software that already exists. 
-For the community to be able to protect its reputation for quality software and openness,
+For the community to be able to protect its reputation for quality and openness,
 its name needs to unique enough to have potential as a trademark.  
          </p>
             <p>

Modified: incubator/public/trunk/site-publish/guides/names.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/names.html?rev=1232024&r1=1232023&r2=1232024&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/names.html [utf-8] (original)
+++ incubator/public/trunk/site-publish/guides/names.html [utf-8] Mon Jan 16 15:22:21 2012
@@ -198,11 +198,10 @@ reproducing the content of the NOTICE fi
 <p class="attribution"><a href="http://www.apache.org/licenses/LICENSE-2.0.html#trademarks">Apache
License, Version 2.0
          	</a></p>
 <p>
-All Apache projects share the Apache License, which issues standard <strong>copy</strong>

+All Apache projects share the Apache License. This issues standard <strong>copy</strong>

 and <strong>patent</strong> rights to 
 downstream consumers. <strong>Trademark</strong> rights for Apache products are
issued and managed independently, 
-beyond the Apache License.
-Apache communities are able to use trademark law to protect their reputation and that of
the 
+beyond the Apache License. This allows Apache communities to use trademark law to protect
their reputation and that of the 
 <a href="http://www.apache.org/foundation/">Foundation</a>, within the broader
 framework provided by the Brand team.
             </p>
@@ -210,16 +209,18 @@ framework provided by the Brand team.
 </div>
 <h3 id='naming-hints'>What Makes A Name Good</h3>
 <div class="section-content">
-<p>Good names for commercial products or <code>UNIX</code> utilities may
work less well for Apache products.
-  Many of our successful open source product names are memorable, unusual and a little 
+<p>Good names for commercial products or <code>UNIX</code> utilities have
tended to work less well here at Apache.
+  Many successful Apache project names are memorable, unusual and a little 
   <a href="http://www.sdtimes.com/TOP_FIVE_HEAD_SCRATCHINGEST_NAMES_FOR_APACHE_PROJECTS/By_Victoria_Reitano/About_APACHE_and_HADOOP_and_HARMONY_and_MYSQL_and_OODT_and_YAY/35959">whimsical</a>.
   These qualities are also often good when it comes to securing trademark protection.
+  Have fun. Be creative.
   </p>
 </div>
 <h3>Podling Suitable Name Search</h3>
 <div class="section-content">
 <p>
-The proposal which establishes a new podling includes a (working) name.
+The initial <a href="http://incubator.apache.org/guides/proposal.html">proposal</a>

+establishes a working name for the new podling.
 Often some discussion and filtering of suitable names happens during the election
 process but this proposed name is <strong>not</strong> final, only <em>provisional</em>.

 The community may choose to change it. Or the community may discover that the name is unsuitable:
@@ -243,7 +244,7 @@ A suitable name search must be successfu
 <p>
 Names are an essential part of building a brand and community. 
 Switching names wastes the efforts put into establishing the original name.
-So, it is best to complete this task as soon as possible.
+So complete this task as soon as possible.
 </p>
 </div>
 </div>
@@ -253,7 +254,7 @@ So, it is best to complete this task as 
 <p>
 A suitable name search has public and private elements. 
 The <a href="https://issues.apache.org/jira/browse/PODLINGNAMESEARCH">tracker</a>
provides the public record.
-Incubator best practice evolves over time, and documentation lags.
+Incubator best practice evolves over time, documentation lags.
 The public records of past searches are a primary source of guidance. 
 Review now the records of previous searches, beginning with the most recent then working
back.
   </p>
@@ -295,19 +296,16 @@ Whether the name proved suitable or unsu
 <h4 id='main-sequence'>The Main Sequence</h4>
 <div class="section-content">
 <p>
-Using a <a href="http://outreach.atnf.csiro.au/education/senior/astrophysics/stellarevolution_mainsequence.html">cosmic</a>
-metaphor, every podling is unique but most fit into a Main Sequence where the processes evolved
-work well (once you give then a chance). For main sequence podlings, most of the bugs should
have been squashed and 
-rough edged documented away. 
-		</p>
-<p>
-In some cases, there may be good reasons for special handling (but not liking the result
is 
-not one of them). Away from the main sequence, process may need to be grown, documentation
is likely be sparse
+Every podling is unique, but using a <a href="http://outreach.atnf.csiro.au/education/senior/astrophysics/stellarevolution_mainsequence.html">cosmic</a>
+metaphor, most fit into a main sequence. For podlings on the main sequence,
+most of the bugs should have been squashed and rough edges documented away, so expect a smooth
journey. 
+Away from the main sequence, process may need to be grown, documentation is likely be sparse
 and progress less smooth. 
          </p>
 <p>
-This document documents the main sequence. This should be appropriate for most podlings and
represents a well known path.
-If there are good reasons to think that your podling isn't Main Sequence, discuss this with
the
+The main sequence is described. This well known path is
+appropriate for almost all podlings.
+If there are good reasons to think that your podling is a special case, discuss this with
the
 <a href="http://mail-archives.apache.org/mod_mbox/incubator-general/">Incubator community</a>
 and attempt to reach consensus on the right way forward.
          </p>
@@ -336,7 +334,7 @@ whether anything has been missed. Check 
 <div class="section-content">
 <p>
 The name needs be unique enough to avoid confusion with software that already exists. 
-For the community to be able to protect its reputation for quality software and openness,
+For the community to be able to protect its reputation for quality and openness,
 its name needs to unique enough to have potential as a trademark.  
          </p>
 <p>



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


Mime
View raw message