incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdelacre...@apache.org
Subject svn commit: r1451011 - in /incubator/public/trunk/content: podling-story.xml stylesheets/project.xml
Date Wed, 27 Feb 2013 22:50:54 GMT
Author: bdelacretaz
Date: Wed Feb 27 22:50:54 2013
New Revision: 1451011

URL: http://svn.apache.org/r1451011
Log:
first outline

Added:
    incubator/public/trunk/content/podling-story.xml   (with props)
Modified:
    incubator/public/trunk/content/stylesheets/project.xml

Added: incubator/public/trunk/content/podling-story.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/podling-story.xml?rev=1451011&view=auto
==============================================================================
--- incubator/public/trunk/content/podling-story.xml (added)
+++ incubator/public/trunk/content/podling-story.xml [utf-8] Wed Feb 27 22:50:54 2013
@@ -0,0 +1,109 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+<!DOCTYPE project
+[
+<!ENTITY project-menu   SYSTEM "../target/project-menu.ent">
+]>
+
+<document>
+  <properties>
+    <atom url="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom">general@incubator.apache.org
Archives</atom>
+    <title>The Story of a Podling</title>
+  </properties>
+  <body>
+    <section id="story">
+      <title>DRAFT - The Story of a Podling</title>
+      <p><b>This is just a draft for now...still a work in progress</b></p>
+      <p>Intended audience: incubator beginners</p>
+      <p>Not policy, only informative</p>
+      <p>Based on the incubation stories of Flex and Clerezza</p>
+      <p>Links are what we consider good examples</p>
+      <p>Keep this short - 10 minutes read?</p>
+        <section id="foo">
+          <title>Proposal</title>
+          <p>champion</p>
+          <p>proposal will cause some questions</p>
+          <p>you might stop here and it's not a failure</p>
+          <p>proposal on the wiki and send for discussion</p>
+        </section>
+        <section id="foo">
+          <title>Mentors and initial committers</title>
+          <p>In general 2-3 incubation mentors, either ASF members of Incubator PMC
members</p>
+          <p>Need to decide how to manage the list of initial committers</p>
+        </section>
+        <section id="foo">
+          <title>Incubator entry vote</title>
+          <p>Starts when discussion is done</p>
+          <p>Point to Flex vote</p>
+          <p>72 hours as per ASF voting rules</p>
+          <p>Usually driven by the champion</p>
+          <p>Usually not contentious, as the previous phases help build consensus</p>
+        </section>
+        <section id="foo">
+          <title>Podling creation</title>
+          <p>Point to Flex jira issues</p>
+          <p>Driven by the champion</p>
+        </section>
+        <section id="foo">
+          <title>Initial code and trademarks</title>
+          <p>If initial code is being donated you need software grants</p>
+          <p>If the donated code has multiple owners or contributors, you might need
to chase them down at this point, or omit the code for which you cannot get permission</p>
+          <p>Any relevant trademarks should be donated at this point</p>
+        </section>
+        <section id="foo">
+          <title>First release</title>
+          <p>It's good to make a first release early, even if it's not of great technical
quality. That helps get acquainted with the incubation release process.</p>
+          <p>From the Incubator's point of view, the release only has to fulfill the
ASF's release requirements. Whether it's good or useful software doesn't matter at this stage.</p>
+          <p>Getting that first release past the Incubator PMC voting stage can be
hard, and it's a good idea to tackle this early in the incubation process, to get it out of
the way
+          and establish and document the podling's release process (link to Flex or Sling
process).</p>
+        </section>
+        <section id="foo">
+          <title>Community growth</title>
+          <p>
+            To graduate, a podling has to demonstrate its ability to grow its community.
In practice, this means attracting and electing new committers and PPMC members.
+            Starting early on this helps. (TODO: reading list, Jukka's posts?)
+          </p>
+          <p>
+            TODO: demonstrate openness/diversity
+          </p>
+        </section>
+        <section id="foo">
+          <title>Exit discussions</title>
+          <p>Incubation can proceed in unexpected directions - the standard exit is
to become a TLP but that's not the only possibility (join a TLP, go elsewhere, retire, ...)
+            - which are not necessarily failures.
+          </p>
+          <p>Discuss with the mentors and community based on the graduation criteria
(link - Clerezza discussion?)</p>
+        </section>
+        <section id="foo">
+          <title>Graduation vote</title>
+          <p>If graduating to TLP, First step is to create the board resolution, discuss
who's on the new PMC (link to flex as one example), 
+            it's good to have at least one ASF member in there.</p>
+          <p>Community votes first, then IPMC.</p>
+          <p>Point to policy + example votes</p>
+        </section>
+        <section id="foo">
+          <title>Board resolution</title>
+          <p>The Incubator PMC acceptance vote is only a recommendation for the board
to accept the new project.</p>
+          <p>The new TLP only exists once the board approves the resolution to establish
it. This is usually announced right after the board meeting, and the new PMC chair
+          can then start the mechanics of establishing the TLP.</p>
+        </section>
+        <section id="foo">
+          <title>Champagne!</title>
+          <p>Congratulations - at this point the new TLP is a full blown Apache project,
and the newly created PMC is fully in charge of its destiny.</p>
+        </section>
+    </section>
+  </body>
+</document>

Propchange: incubator/public/trunk/content/podling-story.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: incubator/public/trunk/content/stylesheets/project.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/stylesheets/project.xml?rev=1451011&r1=1451010&r2=1451011&view=diff
==============================================================================
--- incubator/public/trunk/content/stylesheets/project.xml [utf-8] (original)
+++ incubator/public/trunk/content/stylesheets/project.xml [utf-8] Wed Feb 27 22:50:54 2013
@@ -34,6 +34,7 @@ limitations under the License.
     </projects>
 
     <projects><title href="http://www.apache.org/foundation/glossary.html#Podling">Podlings
(What's that?)</title>
+      <li><a href="/podling-story.html">Story of a Podling</a></li>
       <li><a href="/incubation/Incubation_Policy.html">How? (Policy)</a></li>
       <li><a href="/incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li>
       <li><a href="/incubation/Process_Description.html">When? (Process)</a></li>



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


Mime
View raw message