...
When a project, whether in Incubation or Active status, has not had any activities for over 6 months, it will be put on notice (via email to the project list) that it is on the path of being moved to "End of Life" (EOL) status out. After an additional 6 months have passed, if no activity has taken place, pending TSC approval, the project will effectively be moved to EOL. Software releases and quarterly TSC reports will be considered as signs of "activities".
...
Project Maintainers may submit to the TSC a request for moving their project to EOL. Pending TSC approval, a notification will be sent out to the project mailing list that the project is being placed on the path to EOL. After 6 months have passed, if no one has objected, pending TSC approval, the project will effectively be moved to EOL.
Issue 2: What are the criteria for a "First Major Release"? How does Dave's proposed Project Readiness fit in? FWIW, I created this set of criteria for the Fabric 1.0 release.
Proposed/Draft Resolution 2:
<insert here any criteria from Dave's Project Readiness proposal that do not pertain to what would be considered for graduating to "Active" status, which is handled separately.>
...
Proposed/Draft Resolution 3:
TBD
Issue 4: Under what circumstances can (or what are the criteria for) a project (to) be moved back to Incubation? to a lab?
...
No. Projects can either start as a lab or be proposed to the TSC as a project entering Incubation. The TSC however may choose to direct a proposed project to a lab instead.
Issue 7: How/when does a project get officially names? (Early → easier to set up repository, Later → marketing committee can be involved, see mailing list for discussion)
Proposed/Draft Resolution 7:
To start, a proposal should come with a temporary "code name" (e.g. a geographical location) that can be used for the repository with low risk of trademark violation. On approval, the marketing committee will work with the proposers to create a long term name and will do all the necessary checks. The repository name can be changed.
ISSUES STILL NEEDING DISCUSSION/WORK
Issue 2: What are the criteria for a "First Major Release"? How does Dave's proposed Project Readiness fit in? FWIW, I created this set of criteria for the Fabric 1.0 release.
Proposed/Draft Resolution 2:
<insert here any criteria from Dave's Project Readiness proposal that do not pertain to what would be considered for graduating to "Active" status, which is handled separately.>
Issue 3: What criteria/steps/policies must releases after the First Major Release adhere to?
Proposed/Draft Resolution 3:
TBD
Issue 6: Should we have subprojects (and fewer toplevel projects)?
...
Proposed/Draft Related Resolution 6.2:
Existing projects that were originally started via a HIP but that in practice are not being managed as "top level projects" should will be officially rescinded from the top level nomination for house keeping purposes.
...
Subproject status and reporting should be reported through the top level project. For example, Fabric Explorer status would be included in the Fabric quarterly reports..
Issue
...
Proposed/Draft Resolution 7:
To start, a proposal should come with a temporary "code name" (e.g. a geographical location) that can be used for the repository with low risk of trademark violation. On approval, the marketing committee will work with the proposers to create a long term name and will do all the necessary checks. The repository name can be changed.
Issue 8: How do we deal with a new project coming in that is already a shipping product for a company?
...
Proposed/Draft Resolution 8:
All new projects proposed to the TSC are considered to be starting in Incubation status. If a project happens to fulfill the criteria to move to Active status at the time a HIP is submitted to the TSC, the proposer of the project may submit a request to move to Active status at the same time or shortly after.
The same goes with the first major release.TBD
Comments
Hart:
I'd like our project lifecycle to satisfy three basic requirements:
...