nicolaken 2003/11/28 06:46:34
Modified: site/incubation Process_Description.cwiki
Log:
Fix header level nesting and remove draft status.
Revision Changes Path
1.3 +7 -11 incubator/site/incubation/Process_Description.cwiki
Index: Process_Description.cwiki
===================================================================
RCS file: /home/cvs/incubator/site/incubation/Process_Description.cwiki,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Process_Description.cwiki 25 Oct 2003 04:43:58 -0000 1.2
+++ Process_Description.cwiki 28 Nov 2003 14:46:34 -0000 1.3
@@ -1,9 +1,5 @@
!!!The Process of Incubation
-__This is currently a draft, and has no official status.__
-
-!!!Overview of the Process
-
The incubation process covers the establishment of a candidate, acceptance
(or rejection) of a candidate leading to the potential establishment of a
Podling and associated incubation process, which ultimately leads to the
establishment or a new Apache Top-Level-Project (TLP) or sub-project within an
existing Apache Project.
{{{
@@ -22,7 +18,7 @@
Readers should also review the [Roles and Responsibilities
|Roles_and_Responsibilities] document for a description of the various parties
involved in the Incubation process.
-!!!Establishment
+!!Establishment
The first thing you will want to do is find a __Champion __ for your
project. One way to do this is to explore the Apache site to find similar
projects. Spend some time reading both the projects' web pages and mailing
lists. By simply lurking on the mailing lists (see Mailing Lists section in
this document), you may get ideas about who you would like to ask to help you
with your project proposal. However, Champions must either be ASF [members
|http://www.apache.org/foundation/members.html] or [officers
|http://www.apache.org/foundation/index.html] (see the Champion section later
in this document for more on Champion criteria and responsibilities). Once you
have found an eligible person who is willing to act as Champion, you can use
this person to help you determine if and how your proposal can complement the
ASF. If you and your Champion are convinced that your candidate project would
fit with the "Apache Way", your Champion can help you to get it established.
@@ -32,7 +28,7 @@
As a proposer you should consider the feedback and attempt to gauge a sense
of consensus. Do not be put off by extended threads under your initial post
that have little or nothing to do with you proposal - however, if you feel that
your candidate project is not being addresed you may want to specifically
request a decision on the Candidate by the Sponsor by posting a request to the
decision making list (either [EMAIL PROTECTED] or [EMAIL PROTECTED]; see
Mailing List section for more details). Sometimes a vote will be announced
without you asking for it (perhaps you have done some homework and have a PMC
member assisting you though the process), other times you may need to cut
through discussions and push your request forward for a decision.
-!!! Acceptance
+!! Acceptance
The decision to accept a project is taken on a vote by the Sponsor. The
format of this vote will depend on the rules of the entity in question. Here
again it helps if you have a PMC Member (or board member if the Sponsor is the
ASF board) aligned with your project (preferably as your Champion) because you
stand a better chance of getting feedback about what is actually happening.
The Sponsor will typically take about 7-10 days before announcing a vote
result.
@@ -44,7 +40,7 @@
Your Sponsor, represented by your Mentor, has specific responsibilities
towards you and the Incubator PMC. There are a bunch of administrative and
technical actions to take care of. Your Mentor is responsible for ensuring
that these things happen quickly and efficiently. Also, your Mentor is going
to help you out with the getting in place of the policies and procedures you
use for introducing new comitters, decision making, etc. These aspects will be
watched closely by the Incubator PMC as they provide a good indication of
community dynamics, health and correlation with Apache practices.
-!!!Review
+!!Review
As your project sorts things out and things stabilize (infrastructure,
communications, decision making) you will inevitably come under an assessment
by the Incubator PMC concerning the exit of your project from the incubator.
Keep in mind that exit can be a good things and bad thing. Exit via escalation
to a top-level project or perhaps a subproject of an existing PMC would
typically be viewed as a positive exit. On the other-hand, termination is also
an exit condition that may be considered. With an upcoming assessment it is
generally a good idea to have your STATUS file right up to-date and to ensure
that your Mentor is doing his/her job of evangelizing your project and has good
picture of where you are relative to acceptance or the last assessment point.
This information will help the Incubator PMC to recommend the best action for
for your project.
@@ -62,13 +58,13 @@
!!Continuation
-A recommendation by the Incubator PMC for continuation of incubation shall
include development recommendations. The Incubator PMC has a responsibility to
ensure that the recommended actions are tangible and quantifiable. For
example, an assessment could be that your project has not established a
sufficient community to be viable, in which case the Incubator PMC is obliged
to state specific targets that they consider as viable. This does not
necessarily mean that if you meet this target by the next review that you are
out of incubation - but it does give you concrete achievements that you can
site. Your Mentor is also specifically accountable to you for ensuring that the
recommendations for continuation are usable, substantive and tangible. If this
is not the case, you have every right to appeal an Incubator decision to the
Apache Board - however, if your Mentor is doing a good job, neither of these
scenarios should arise.
+A recommendation by the Incubator PMC for continuation of incubation shall
include development recommendations. The Incubator PMC has a responsibility to
ensure that the recommended actions are tangible and quantifiable. For
example, an assessment could be that your project has not established a
sufficient community to be viable, in which case the Incubator PMC is obliged
to state specific targets that they consider as viable. This does not
necessarily mean that if you meet this target by the next review that you are
out of incubation - but it does give you concrete achievements that you can
site. Your Mentor is also specifically accountable to you for ensuring that the
recommendations for continuation are usable, substantive and tangible. If this
is not the case, you have every right to appeal an Incubator decision to the
Apache Board. However, if your Mentor is doing a good job, neither of these
scenarios should arise.
!!Escalation
-For Podlings that aim to establish sub-projects or products within existing
communities you are almost home-free. The main issues you need to deal with now
is migration of you code into the target project - something you should be
confident in doing based on the contacts and understanding you gained during
initial establishment and incubation.
+For Podlings that aim to establish sub-projects or products within existing
communities you are almost home-free. The main issues you need to deal with now
is migration of you code into the target project, something you should be
confident in doing based on the contacts and understanding you gained during
initial establishment and incubation.
-For projects aiming to be a Top-Level-Project (TLP), you have an additional
obstacle - namely the ASF Board. While the ASF Board might be your Sponsor,
this does not mean they have formally accepted you as a TLP. To establish a
TLP you need to draft a board motion that identifies the project scope, mission
and charter. You can submit the motion to the Board using the [EMAIL
PROTECTED] email address. Well-prepared projects will have already developed
contacts with members of the Board so this should not be a surprise agenda
item. Keep in mind that the Board can approve your motion as supplied, amend
it, or reject it. If you are rejected then you need to sort this out with the
Incubator PMC and allies you have developed during the incubation process -
i.e. for a TLP objective the Incubator PMC OK is only half of the story.
+For projects aiming to be a Top-Level-Project (TLP), you have an additional
obstacle, namely the ASF Board. While the ASF Board might be your Sponsor,
this does not mean they have formally accepted you as a TLP. To establish a
TLP you need to draft a board motion that identifies the project scope, mission
and charter. You can submit the motion to the Board using the [EMAIL
PROTECTED] email address. Well prepared projects will have already developed
contacts with members of the Board so this should not be a surprise agenda
item. Keep in mind that the Board can approve your motion as supplied, amend
it, or reject it. If you are rejected then you need to sort this out with the
Incubator PMC and allies you have developed during the incubation process. In
other words, for a TLP objective the Incubator PMC OK is only half of the
story.
-However, in practice, assuming you are building contacts with members in
Apache, the Incubator PMC, and the ASF Board - the transition from Podling to
TLP should be a smooth and painless process.
+However, in practice, assuming you are building contacts with members in
Apache, the Incubator PMC, and the ASF Board, the transition from Podling to
TLP should be a smooth and painless process.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
