The goal of incubation is to become an Open Subsurface Data Universe (OSDU) Top-Level project. The OSDU Incubator (currently Shared Backlog workstream) helps projects which want to be entered as The Open Group OSDU platform projects.
It helps those incoming projects (called "podlings") adopt the OSDU governance and operation and guides them to The Open Group services available to platform projects so the podling can become a top-level OSDU project. Incoming projects should review The Open Group IP policies, OSDU OMC and PMC governance charters and confirm that they are able to comply with the OSDU governance and operations policies.
The OMC delegates a few mentors for each podling, as "on the ground" agents to act as liaisons with the various OSDU teams such as PMC, The Open Group support team etc., and facilitate the podling's growth and operations.
To mature into a formal OSDU platform project, an incoming project ("podling") goes through the following steps.
Find a champion and prepare an incubation proposal (detailed here)
Discuss the proposal with the OSDU OMC and PMC members
Provide the list of initial committers and contributors in the proposal
Wait for OSDU forum/OMC vote on the proposal
Upon approval setup the podling's infrastructure
- This includes submitting (uploading) contributed code to The Open Group GitLab infrastructure after ensuring that all submitted code carries the required Apache 2.0 license, passing thru audit, cryptography, legal, TCC and compliance checks, and performing clean-up and repackaging as necessary.
- The podling team should also update and include documentation, build and CI/CD scripts and transition any issue tracking to The Open Group community GitLab
Start building a community around the podling's code by inviting new committers and developer members
- During incubation, the podling is expected to build and expand its community, which includes voting in new committers and developer members.
- Expanding and especially renewing project communities is an essential part of the OSDU's governance, as it fosters project durability.
Make podling releases and document and refine the release process
- A podling is expected to make several software releases during incubation, that gradually progress towards being fully conformant to the OSDU data platform policy. This can include but not limited to adherence to core service principles around identity, authorization, discovery/search, compliance and extensibility in addition to deployment, monitoring and operational consistency with the rest of the platform. Fully conformant releases are a condition for graduation.
- Podling releases must also include the word "incubating" in any release file names and include a DISCLAIMER, to prevent any confusion as to the project's status. As podlings are not yet "real" OSDU projects, it is important to set expectations right.
- Note that OSDU data platform releases need to provide complete distributable/deployable runtime packages along with the code as part of their releases. This needs to be consistent and integrated with the other project deliverables in the platform allowing the platform to be deployed in any of the supported environments. The focus is on the actual source code releases and all deployable packages are based on those "official" releases.
Evaluate compliance to OSDU platform (code integration, CI/CD and release robustness, licenses/copyright, Quality/test rigors, engagement in community and uptake within operators), present results to the OSDU Forum and OMC /PMC.
- The podling votes on the release on internally with their community. The main goal of this vote is for the podling community to practice and learn voting on releases. The vote is successful if there are at least three +1 votes from members, and more +1 than -1 votes from members.
- Then, if this first level vote is successful, a PMC vote is held. This is required to make the vote an Act of the Foundation, as for all OSDU releases.
When this vote is passed (critical mass of engagement is generated), the podling is ready to graduate and can be voted by the OMC to be added formally to the PMC top-level projects list
- Votes from the podling should be carried over to the OMC vote, by explicitly mentioning the podling vote result and including the details in the OMC [VOTE] message.
- Both the podling and OMC votes follow the standard OSDU voting principles: they are majority votes that last at least 72 hours and if people vote several times only their last vote counts.