-
Notifications
You must be signed in to change notification settings - Fork 6
/
incubation.html
78 lines (54 loc) · 6 KB
/
incubation.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
---
---
<!DOCTYPE html>
<html>
<head>
<title>Codice: Incubation</title>
{% include head.html %}
</head>
<body>
<div class="shadow-wrapper">
<div class="content-wrap">
{% include header.html %}
<div class="container">
<div class="main-content-wrap">
<h2>Codice Incubation Process</h2>
<p>So...how do projects get into Codice?</p>
<p>The Codice incubation process, like the rest of the Codice fundamentals looks to the Apache Foundation for its initial operating principles and practices. While there are lots of details, the basic process is really straight forward: submit a proposal, the Codice BoD (to include the sponsor) will vote on entrance, incubate until ready for promotion to top-level project (or terminate), then promote and operate.</p>
<h3>The Process</h3>
<p>The process begins with communicating the need, your project, or just an idea with a Codice member (BoD or PMC). It is really important to involve the Codice foundation as early as possible in the process, ideally before any code is written. This will ensure a smooth transition of the project into the Codice Incubation Process. Then, assuming it's all good, you'll submit a proposal. We've put together a <a href="proposal.html">Proposal Template</a>, which you are free to use. We actually recommend using our wiki environment for developing the proposal then using it to generate the final submission. This way we can help provide feedback and the community can comment in realtime. Once the proposal is received and reviewed by the Codice BoD, we'll collectively iterate over the details of Incubator inclusion. It is normal for the incubating project to maintain it's state in transition from incubator to top-level, for the first period of operation.</p>
<h3>The Vote</h3>
<p>We're still trying to figure out what the right timeframe is for submission, or even what the appropriate duration is for the vote. However the vote will be put to the Codice BoD and (for now) we'll return the vote results to the IPMC Chair as quickly as possible with any feedback available.</p>
<h3>Who</h3>
<p>Each incubating project will be required to form the committee that is responsible for operating the project towards top-level inclusion at Codice. The committee will define a chairperson who well act as the liaison between the Codice BoD, the committee and the community at-large. The Chair is responsible for all documentation requirements and coordinating the incubation process with the community.</p>
<h3>Incubator Project Management Committee (PMC)</h3>
<p>The Project Management Committee is responsible to the Board for administering the Incubator Project in the manner specified in the founding resolution. It is expected that the incubating project's PMC will transition directly to the top-level project's PMC.</p>
<h3>Chair of the Incubator PMC</h3>
<p>The person appointed by the Board of Directors to have primary responsibility for oversight of the Incubator Project, its policies, and policy implementation.</p>
<h3>Candidate (project)</h3>
<p>A proposal for incubation. Described in detail <a href="pdfs/ProposalTemplate.pdf"></a>here.</p>
<h3>Champion</h3>
<p>A Member of the Codice Foundation who supports a Candidate's application for Incubation and who supports and assists the Podling through the Incubation process.</p>
<h3>Sponsor</h3>
<p>A Sponsor SHALL be either:</p>
<p>the Board of the Codice Foundation;
a Top Level Project (TLP) within the Codice Foundation (where the TLP considers the Candidate to be a suitable sub-project); or
the Incubator PMC.
This role and its responsibilities are discussed [here].</p>
<h3>Mentor</h3>
<p>An incubator project has one or more Mentors, one of which MUST be an Codice Member. Mentors are chosen by the Sponsor to actively monitor the project, guide the project, and report its status to the Sponsor and the Incubator PMC. All Mentors must be members of the Incubator PMC. A Mentor has responsibilities toward the Incubator PMC, the Sponsor, and the community of the assigned project.</p>
<h3>Committers</h3>
<p>The candidate shall declare an initial set of committers. On acceptance of a candidate project, the assigned Mentors shall be given access to the project's repository for the duration of the incubation process. This is to allow the Mentors to perform their incubation duties, and is for administrative purposes only. To be given full committer privileges, such as the right to add new code to the repository, the Mentor must earn them as would any other potential new committer. In some cases, the Mentor may be part of the initial set of declared committers, but this is not a requirement of the Incubation process.</p>
<h3>Operating Notes</h3>
<p>This process, in particular the proposal submission, is evolutionary... It is likely to improve and become optimized for efficiency over time. In order for the evolution to occur, we're trying to stay away from as many "hard" rules as possible. That said, until an incubation-specific board is formulated to handle the incoming projects and projects in incubation the BoD will have final say.</p>
<h3>Disputes?</h3>
<p>Any disputes between a proposal, incubating project, or members thereof will be handle directly between the Codice BoD and the submitting/acting IPMC Chairperson only. Any "out-of-bounds" commentary in any of the Codice tools will not be tolerated, and will be removed at the discretion of the BoD.</p>
<p>Any disputes between the IPMC and the community should be handle professionally, and transparently in the community communication forums.</p>
<p>If it is deemed that an IPMC Chairperson is ineffectively managing the project proposal/incubation, the BoD reserves the right to resolve directly, or to open the position for nomination by the IPMC. Note, that is in everyone's best interest that we try to grow individuals as well as projects.</p>
</div><!-- /main-content-wrap -->
</div><!-- /container -->
{% include footer.html %}
</div>
</div><!-- /shadow-wrapper -->
</body>
</html>