Page tree
Skip to end of metadata
Go to start of metadata

Overview of Proposal

These are amendments to the existing incubation exit criteria. They were brought up during "incubation entry proposal"

  1. Prepare a checklist for incubation exit criteria.
  2. The project must comply to meet file structure repository requirement as listed at https://tsc.hyperledger.org/repository-structure.html within 6 months of graduation.
  3. The project has followed at least one release taxonomy as discussed at https://tsc.hyperledger.org/release-taxonomy.html.

TODO ~ more to come.

  1. Update the following statement under "Infrastructure" in the Project Incubation Exit Criteria - tsc (hyperledger.org) to reflect the common repository structure.
    1. "All information necessary for someone to join the community and be able to start contributing is duly documented (location of repo, list of maintainers, mailing lists addresses, slack channels if used, etc) following Hyperledger standard practice (CONTRIBUTING.md, MAINTAINERS.txt, etc)"
  2. Work with community architects to create a checklist under Checklists - Community Architects - Hyperledger Confluence for graduated projects.

Some items to consider adding to a checklist

  • TSC Approval completed (via TSC meeting)
  • Update wiki to reflect graduated status on project home page (CA to complete)
  • Update landscape to reflect graduated status (CA to complete)
  • PR plan completed (marketing to complete)

Original comments can be found at Incubation entry considerations.

Formal Proposal(s)

Include the clauses discussed as formal requirement at https://tsc.hyperledger.org/project-incubation-exit.html

Action Items

  • Type your task here, using "@" to assign to a user and "//" to select a due date

Reviewed By


9 Comments

  1. "Prepare a checklist for incubation exit criteria."

    I don't understand what this refers to. Is that a request to the applicant? That they provide a checklist? Historically I think that's what people have done.


    1. No, I should have expanded it. The action item is on us (either TSC or Hyperledger CA) to get the checklist in place. Add that checklist here in the proposal. This proposal should have been still under construction status.

      1. I recommend working with the community architects to create a checklist under Checklists - Community Architects - Hyperledger Confluence for graduated projects. I assume it would be something similar to First Major Release Checklist - Community Architects - Hyperledger Confluence. Once a project has graduated, the Hyperledger organization typically handles PR and moving the project to graduated status in the wiki and other places.

        Some items to consider adding to a checklist

        • TSC Approval completed (via TSC meeting)
        • Update wiki to reflect graduated status on project home page (CA to complete)
        • Update landscape to reflect graduated status (CA to complete)
        • PR plan completed (marketing to complete)

  2. "The project must comply to meet file structure repository requirement as listed at https://tsc.hyperledger.org/repository-structure.html within 6 months of graduation."

    I think projects ought to be compliant to graduate. They should be required to comply within 6 months of entering incubation.

    1. Right. How do we capture that or the better question is where do we capture it? We did not mention this in the incubation entry considerations. It was skipped stating that this should not be a mandatory criteria for incubation. Is there a process where any new project, has mandatory actionable items for the first 6 months upon incubation?

      1. All we need is to add compliance to the common repository structure to the list of criteria for graduation.

        1. We can update the following statement under "Infrastructure" in the Project Incubation Exit Criteria - tsc (hyperledger.org) to reflect the common repository structure

          • "All information necessary for someone to join the community and be able to start contributing is duly documented (location of repo, list of maintainers, mailing lists addresses, slack channels if used, etc) following Hyperledger standard practice (CONTRIBUTING.md, MAINTAINERS.txt, etc)"
  3. "The project has followed at least one release taxonomy as discussed at https://tsc.hyperledger.org/release-taxonomy.html"

    This is captured in the Project Incubation Exit Criteria - tsc (hyperledger.org) under Alignment as: "Project must make a release, even a “developer preview”, before graduation."