Author: jani
Date: Tue May 6 19:47:15 2014
New Revision: 1592853
URL: http://svn.apache.org/r1592853
Log:
textual updates
Modified:
labs/cms/trunk/content/faq.html
Modified: labs/cms/trunk/content/faq.html
URL:
http://svn.apache.org/viewvc/labs/cms/trunk/content/faq.html?rev=1592853&r1=1592852&r2=1592853&view=diff
==============================================================================
--- labs/cms/trunk/content/faq.html (original)
+++ labs/cms/trunk/content/faq.html Tue May 6 19:47:15 2014
@@ -65,7 +65,7 @@
The firsts are efforts that are mostly done by a few individuals,
with a lot of freedom and
peace and it's expected of many of such efforts to fail. The ASF
grew around established projects
and focused its entire incubation efforts around the concept of
nurturing and bootstrapping
- healthy and diverse open development communities. Unfortunately,
it has been duly noted that
+ healthy and diverse open development communities. However, it has
been duly noted that
incubation and innovation can hardly coexist at the same time and
that the foundation didn't
contain a place were its own committers can get together and
bootstrap new ideas and were
forced to go to external locations. Apache Labs was established to
provide a place were trusted
@@ -78,12 +78,12 @@
<h4>3. Why can only apache committers ask for a lab?</h4>
<p>
Apache Labs wants to be a place were it's easy and natural for
people to work on new things
- and collaborate, without fearing that somebody is trying to 'abuse'
the apache brand and
+ and collaborate, without fearing that somebody is trying to 'abuse'
the Apache brand and
boost their web visibility by just placing their stuff overhere.
Since it's really hard to create
a 'trust' filter, Apache Labs is simply reusing the collective
social filtering that
project do in their normal activity by granting commit access. This
drastically simplifies the
labs operations and reduces social friction: you have to earn your
social respect somewhere
- else in the foundation before you can ask for a lab. We are aware
that this might potentially
+ else in the foundation (be a committer in at least one Apache
project) before you can ask for a lab. We are aware that this might potentially
reduce our ability to innovate, but we are willing to pay this
price for a simpler day-to-day
operation.
</p>
@@ -105,7 +105,7 @@
consensus in a 72 hour period of
the <a href="team.html">Apache Labs PMC</a> before it can be
established. This is done
to avoid that committers use labs as their personal 'dumping'
grounds and that labs
- remain topic-specific. Also allows the PMC to force the committers
to express their intention
+ remain topic-specific. It also allows the PMC to force the
committers to express their intention
clearly and in advance, and to make sure that their
machine-readable descriptors are
sound.
</p>
@@ -138,10 +138,10 @@
Apache Labs expects a lot of labs with a few people per lab and not
a lot of need for
public coordination between them. Asking for lab-specific mail
lists has several disadvantages:
<ul>
- <li>it increases the weight of labs on the apache
infrastructure</it>
+ <li>it increases the weight of labs on the Apache
infrastructure</it>
<li>it reduces the ability for people to 'watch over the
shoulder' of labs activity and
become interested serendipitously</li>
- <li>it forces a low threshold for activity that might trigger the
promotion of a lab
+ <li>it encourages a low threshold for activity that might trigger
the promotion of a lab
that has a lot of momentum toward the incubation</li>
</ul>
</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@labs.apache.org
For additional commands, e-mail: commits-h...@labs.apache.org
