The Story of a Podling

Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 21AA1200CB1 for ; Sat, 24 Jun 2017 13:32:35 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 20215160BF9; Sat, 24 Jun 2017 11:32:35 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6EF64160BDA for ; Sat, 24 Jun 2017 13:32:33 +0200 (CEST) Received: (qmail 16804 invoked by uid 500); 24 Jun 2017 11:32:32 -0000 Mailing-List: contact cvs-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list cvs@incubator.apache.org Received: (qmail 16789 invoked by uid 99); 24 Jun 2017 11:32:32 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 Jun 2017 11:32:32 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 7F640DFE22; Sat, 24 Jun 2017 11:32:32 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: git-site-role@apache.org To: cvs@incubator.apache.org Date: Sat, 24 Jun 2017 11:32:32 -0000 Message-Id: X-Mailer: ASF-Git Admin Mailer Subject: [1/4] incubator git commit: Automatic Site Publish by Buildbot archived-at: Sat, 24 Jun 2017 11:32:35 -0000 Repository: incubator Updated Branches: refs/heads/asf-site 7f992557b -> 21a37b7d3 http://git-wip-us.apache.org/repos/asf/incubator/blob/21a37b7d/podling-story.html ---------------------------------------------------------------------- diff --git a/podling-story.html b/podling-story.html new file mode 100644 index 0000000..b22eb8d --- /dev/null +++ b/podling-story.html @@ -0,0 +1,331 @@ + + + + + The Story of a Podling + + + + + + + + + + + + + + + + + + + + + +

+ + + + +

+ + + +

Table of Contents

Proposal
Mentors and initial committers
Incubator entry vote
Podling creation
Initial code and trademarks
First release
Community growth
Exit discussions
Board resolution
Champagne!

This is just a draft for now…still a work in progress

This is an informational overview of the life of a podling, from proposal to graduation.

It is intended for people considering incubating their project at the ASF, or people joining podlings, +as a single page that gives an overview of the incubation process, without going into too much detail.

Links to examples of proposals, discussions etc. are provided +to give a more concrete overview of what happens during incubation.

We won’t include many details - the goal is to keep this short, +so that you consume it in about ten minutes.

Proposal

The first step towards incubation is to create a proposal for the Incubator. +Examples like the Clerezza and +Flex proposals will +give you a feel for what to put in there.

Creating the proposal will usually raise a number of questions about your future +podling, and it’s good to already find an ASF champion +at this stage, +to answer any questions that you might have or make the necessary contacts.

Once your proposal is ready and you have decided to go forward, you can add it +to the wiki and send a [PROPOSAL] +message to the general@a.o list. Incubator PMC members can then give their feedback +to help refine the proposal before voting upon it. +See the Flex discussion for an example.

Mentors and initial committers

In general 2-3 incubation mentors, either ASF members of Incubator PMC members +Need to decide how to manage the list of initial committers

Incubator entry vote

Starts when discussion is done +Point to Flex vote +72 hours as per ASF voting rules +Usually driven by the champion +Usually not contentious, as the previous phases help build consensus

Podling creation

Point to Flex jira issues +Driven by the champion

Initial code and trademarks

If initial code is being donated you need software grants +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 +Any relevant trademarks should be donated at this point

First release

It’s good to make a first release early, even if it’s not of great technical quality. +From the Incubator’s point of view, the release only has to fulfill the ASF’s release requirements, which are primarily legal. +Whether the product is good or useful software doesn’t matter at this stage.

Learning the ASF’s legal rules and customs, adapting the codebase to conform to them, and getting that first release past the Incubator PMC voting stage can be hard, so it’s a good idea to tackle this task during the initial burst of energy as incubation begins. +A secondary goal of making an early release is to document the podling’s release process (link to Flex or Sling process), so that subsequent releases are easy and fast and people who are not core developers may serve as release managers.

Community growth

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?)

TODO: demonstrate openness/diversity

Exit discussions

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.

Discuss with the mentors and community based on the graduation criteria (link - Clerezza discussion?) +== Graduation vote

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. +Community votes first, then IPMC. +Point to policy + example votes

Board resolution

The Incubator PMC acceptance vote is only a recommendation for the board to accept the new project. +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.

Champagne!

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.

+ +

+ + + + + + + + + \ No newline at end of file http://git-wip-us.apache.org/repos/asf/incubator/blob/21a37b7d/policy/incubation.html ---------------------------------------------------------------------- diff --git a/policy/incubation.html b/policy/incubation.html index a9ec81c..0d8d2cb 100644 --- a/policy/incubation.html +++ b/policy/incubation.html @@ -42,7 +42,7 @@ - +

+ + http://git-wip-us.apache.org/repos/asf/incubator/blob/21a37b7d/policy/process.html ---------------------------------------------------------------------- diff --git a/policy/process.html b/policy/process.html index fe964ea..7222383 100644 --- a/policy/process.html +++ b/policy/process.html @@ -42,7 +42,7 @@ - +

+ + http://git-wip-us.apache.org/repos/asf/incubator/blob/21a37b7d/policy/roles_and_responsibilities.html ---------------------------------------------------------------------- diff --git a/policy/roles_and_responsibilities.html b/policy/roles_and_responsibilities.html index 95029d2..1e178fc 100644 --- a/policy/roles_and_responsibilities.html +++ b/policy/roles_and_responsibilities.html @@ -42,7 +42,7 @@ - +

+ + @@ -189,7 +210,7 @@ without their Board hat is not stating policy but expressing a personal opinion.

Incubator Project Management Committee (IPMC)

The Incubator PMC [resolution] is responsible for:

- https://incubator.apache.org/ngtest/guides/about.html + https://incubator.apache.org/ngtest/faq.html 2002-10-16

- https://incubator.apache.org/ngtest/guides/branding.html + https://incubator.apache.org/ngtest/whoweare.html 2002-10-16

- https://incubator.apache.org/ngtest/guides/chair.html + https://incubator.apache.org/ngtest/guides/about.html + 2002-10-16 +

+ https://incubator.apache.org/ngtest/guides/branding.html 2002-10-16

- https://incubator.apache.org/ngtest/guides/lists.html + https://incubator.apache.org/ngtest/guides/names.html 2002-10-16

- https://incubator.apache.org/ngtest/guides/participation.html + https://incubator.apache.org/ngtest/guides/podling_sourcecontrol.html 2002-10-16

- https://incubator.apache.org/ngtest/guides/pmc.html + https://incubator.apache.org/ngtest/guides/ppmc.html 2002-10-16

- https://incubator.apache.org/ngtest/guides/podling_sourcecontrol.html + https://incubator.apache.org/ngtest/guides/press-kit.html 2002-10-16

- https://incubator.apache.org/ngtest/guides/ppmc.html + https://incubator.apache.org/ngtest/guides/releasemanagement.html 2002-10-16

- https://incubator.apache.org/ngtest/guides/press-kit.html + https://incubator.apache.org/ngtest/guides/retirement.html 2002-10-16

- https://incubator.apache.org/ngtest/guides/releasemanagement.html + https://incubator.apache.org/ngtest/guides/sites.html 2002-10-16

- https://incubator.apache.org/ngtest/guides/retirement.html - 2002-10-16 + https://incubator.apache.org/ngtest/guides/proposal.html + 2017-06-24

- https://incubator.apache.org/ngtest/guides/sites.html + https://incubator.apache.org/ngtest/podling-story.html 2002-10-16

+ https://incubator.apache.org/ngtest/guides/chair.html + 2002-10-16 +

+ https://incubator.apache.org/ngtest/guides/lists.html + 2002-10-16 +

+ https://incubator.apache.org/ngtest/guides/participation.html + 2002-10-16 +

+ https://incubator.apache.org/ngtest/guides/pmc.html + 2002-10-16 +

https://incubator.apache.org/ngtest/policy/incubation.html 2002-10-16

Who We Are

+ + + + +

+ + + +

Table of Contents

The Incubator Project Management Commitee (PMC)
Mentors
Incubator Committers

+ + + + + +

Note

We ask that you please do not send us emails privately asking for +support. We are non-paid volunteers who help out with the project and +we do not necessarily have the time or energy to help people on an +individual basis. Instead, we have setup mailing lists which often +contain hundreds of individuals who will help answer detailed +requests for help. The benefit of using mailing lists over private +communication is that it is a shared resource where others can also +learn from common mistakes and as a community we all grow together.

The Incubator Project Management Commitee (PMC)

The Incubator PMC is responsible to the Board +for the management of the Incubator Project. Only votes cast by members of the incubator PMC +are binding upon Apache. The work that this project is charged with overseeing differs from +other projects and so functions a little differently. +For more details read the Incubator PMC guide.

The list of Incubator PMC members can be found at people.apache.org.

Mentors

Each podling status page lists its mentors. Please see the summary of Incubator projects.

Incubator Committers

Each podling status page lists its committers. +Please see the summary of Incubator projects.

The list of all Incubator committers can be found on +people.apache.org.

There is also a +list of all Apache committers.

+ +

Guide :: The Story of a Podling