EDS Naturalization: Transition to Incubator state

As a contributor to the OSDU community, I want to move the Naturalization project to the incubator stage, so that it can undergo further development and evaluation in alignment with community standards and processes.

Acceptance Criteria:

1. The Naturalization project is officially transitioned to the incubator stage.
2. All necessary documentation and project details are updated to reflect the transition.
3. The transition aligns with the guidelines outlined in the linked issue: https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/extern-data/home/-/issues/281.
4. Stakeholders are informed of the transition and its implications for the project's roadmap.
5. Clear goals and milestones for the incubator stage are defined and agreed upon and documented in the issue below with all parties.

Technical Notes:

• Ensure compliance with the OSDU governance process for transitioning projects.
• Review and address any prerequisites or dependencies mentioned in the linked issue.
• Establish a plan for community feedback and collaboration during the incubator stage.

Related Links:

• (Previously) EDS Ingest - Certification Progress Updates (#281) · Issues
  • Design Documents/Training/EDS_Handover_Document-Pavithra.docx · master
  • Design Documents/Certification Criteria
• (PMC - Maturity Model) README.adoc
  • Project Capability Maturity :: PMC Home Portal
  • maturity-process.md

Check list from Community Platform Capability Maturity

	Criteria	Criteria Details	Sandbox Status	Incubator Status	Incubator Remark	Graduated Status *Ease Tracking
1	Open Source Code	Be openly licensed in such a a way that allows it to be included freely with other OSDU Data Platform open source code under Apache 2.0	[Required] Drafted	[Required] Drafted	LICENSE · master Shared with OSDU Ingest and EDS Ingest	[Required] Drafted
2	Open Source Code	Be available in OSDU’s community GitLab repository	[Required] Drafted	[Required] Drafted	[Source Code] osdu_airflow/eds/eds_naturalization · master [Airflow DAG File] src/dags/eds_naturalization · master	[Required] Drafted
3	Open Source Code	Have functioning, usable code (beyond just a proposed specification)	[Required] Drafted	[Required] Drafted	Code coverage from Preship Testing since M23 #139 (comment 375912)	[Required]
4	Charter	Have a documented business purpose that reasonably fits within the purpose of the OSDU Forum’s mission	[Required] Drafted	[Required] Drafted	EDS Naturalization - OSDU EDS Documentation	[Required]
5	Charter	Have a named product champion to own the progression of the component	[Required]	[Required] Drafted	ExxonMobil ??? KDM ??? TGS Operators: ExxonMobil –Gathering requirements and prioritization for EDS –Leading the effort for EDS development –Maintaining/Testing the product Providers: KDM –Creates custom dataset wrappers and make it available for utilization –Feedback/input for the product –Testing the product	[Required]
6	Follow PMC Best Practices	Follow the project governance as established in the PMC Home Portal: https://osdu.projects.opengroup.org/pmc/work-products/pmc-portal/pmc-policies/main/index.html		[Required] Drafted	EDS Track lead will update the EDS progress weekly in "PMC Project Status Update" meeting EDS Track lead will lead the discussion weekly in the "EDS Community Meeting" The EDS Track is open for contribution, aligned with PMC Governance "Model Solicit contributions from anyone, anywhere" New contributor can contact EDS track leads and the EDS operating model can be obtained from EDS Working Agreement.	[Required]
7	Alignment with OSDU InfoSec Requirements	Pen Testing requirements		[Recommended] Drafted	Not required as of now as the code is protected by OSDU Workflow service and Airflow Platform Besides, pydantic data validation to ensure inputs are validated	[Recommended]
8	Alignment with OSDU InfoSec Requirements	CI/CD Pipeline security scans		[Recommended] Drafted	osdu-airflow-lib - Unit test cases are in place to ensure the code release are stable osdu-airflow-lib - Security Scanning is in backlog but require support from community	[Recommended]
9	Enterprise Architecture Aligned Autonomy	Have all other services impacted by this project been made aware of its existence?		[Required] Drafted	All the services which are impacted by this project are well aware of its existence. All changes are announced in PMC calls as well	[Required]
10	Enterprise Architecture Aligned Autonomy	Are all dependent services being made aware of the dependency?		[Required] Drafted	A list of EDS dependency services is available publicly EDS Naturalization (Sandbox) is dependent on Dataset Service (Graduated) and Dataset Service (Graduated) is dependent on EDS DMS (Graduated)	[Required]
11	Enterprise Architecture Aligned Autonomy	Does this project leverage/reuse other OSDU services without creating unnecessary redundancy?		[Required] Drafted	Currently, EDS Naturalization is utilizing dataset, storage, search, secrets, and ingestion workflow services, the redundancy is not found.	[Required]
12	Enterprise Architecture Aligned Autonomy	Does this project adhere to published platform-wide ADRs (Architectural Decision Records)?		[Required] Drafted	The EDS project is adhering to the published platform-wide ADRs. As proof, the proposed/published ADRs of EDS Naturalization are unique and don't cater to the already existing problems. We are utilizing the services that are available on OSDU.	[Required]
13	Enterprise Architecture Aligned Autonomy	Has this project documented & published its own ADRs for decision transparency?		[Required] Drafted	Yes ADR for EDS Naturalization A full list of EDS ADR can be found here	[Required]
14	Minimum Committer Organizations	Rationale: This follows Linux Foundation (specifically CNCF) patterns of committer requirements. Requiring multiple committers for Graduated components also enables those components to continue to be maintained through open source without dependence on a single organization.	1	1	ExxonMobil ??? ACCENTURE ??? ??? KDM ??? ??? TGS ???	2
15	Implemented on Community Implementation	(1) In order to provide early access for community feedback and allow a path towards maturity, Incubator software shall be deployed to the open source community implementation (once community implementation is established). (2) In order to provide a singular baseline reference for functionality of the platform.		[Required] Done and release into Mercury M25 release	Community Implementation for EDS Compatibility (#138) · Issue EDS Naturalization for Anthos/CI environment (!367) · Merge requests	[Required] Done and release into Mercury M25 release
16	Ongoing Project Continuity	Has the project been included & supported in the OSDU PMC releases for 6+ months?			Yes, the EDS Naturalization has been tested by the community during pre-ship testing since M23 to M25 (currently). Click Here to see the testing results	[Required]
17	Documentation	Documentation for an OSDU software project includes: Tutorial instructions for using the service		[Required] Done	The tutorial and instruction on the using the EDS Naturalization is available in EDS Configuration Guide/EDS Naturalization - OSDU EDS Documentation	[Required]