update charts; fix adoption date

Author: auhlig

CHARTER.md

@@ -1,42 +1,116 @@
-# CloudOperators Charter
+# Technical Charter (the “Charter”) for Greenhouse
 
-## Mission Statement
-We aim to simplify and secure the operation of globally distributed bare-metal operating system through a unified, transparent, and extensible managed service platform. Greenhouse empowers teams by reducing operations complexity, standardizing configurations, and delivering built-in observability, security, and compliance solutions—enabling organizations to run their cloud environments efficiently, confidently, and sustainably.
+Adopted 04.06.2025 (June 4, 2025)
 
-## Project Description
-Greenhouse is a comprehensive platform designed to address the challenges of operating large-scale cloud infrastructures.  
-It offers a holistic dashboard and API to manage various operational aspects efficiently and transparently. Moreover, it enables operations of a globally distributed cloud infrastructure in compliance with industry standards. The platform addresses common operational challenges such as the complexity of tools, fragmentation of configuration, visibility and permission management.
-Several plugins extend the core platform, providing cloud-native observability, security & compliance tooling and more. These plugins come with sane default configurations and include all necessary components for application-specific needs such as production-proven alerts, playbooks, metric visualization dashboards.
+This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the Greenhouse open source project, which has been established as a project of Linux Foundation Europe, a Belgian private stichting headquartered at Kunstlaan 56, Brussels  (“LF Europe”) (the “Project”).  All contributors and other participants in the Project (collectively, “Collaborators”) must comply with the terms of this Charter.
 
-## Benefit to NeoNephos
+Throughout this document, we use terms as defined in the GitHub Glossary.  
+https://docs.github.com/en/get-started/learning-about-github/github-glossary (as of 01.03.2025)
 
-The cloud-edge continuum requires physical hardware which can be housed in centralized, secure data centers or in more compact form factor at near and far edges, all with appropriate energy supply (preferably renewable) and cooling.   
-Alongside the physical setup of cloud and edge locations, a software system is essential for managing this hardware - the Baremetal Operating System (BOS). The BOS is designed to create a stable and robust foundation that seamlessly integrates with the Cloud Operating System (COS). As spending on cloud infrastructure services continues to grow, BOS aims to facilitate an easily reproducible, fully automated, and end-to-end lifecycle for compute, storage, and network hardware from build to decommissioning. In addition to documentation, BOS will provide a reference implementation on qualified hardware, allowing companies to join the continuum.
+## Mission and Scope of the Project
 
-BOS extends the traditional definition of machine-centric Infrastructure-as-a-service (IaaS) by operationalizing and combining cloud-native concepts with robust and known open-source components. It is primarily provided via projects IronCore and CobaltCore, whereas other projects assist with its production-grade monitoring and operations.
+The mission of the Project is to simplify and secure the operation of globally distributed bare-metal operating system through a unified, transparent, and extensible managed service platform. Greenhouse empowers teams by reducing operations complexity, standardizing configurations, and delivering built-in observability, security, and compliance solutions—enabling organizations to run their cloud environments efficiently, confidently, and sustainably.
 
-# Benefits to Project
+The scope of the Project includes collaborative development under the Project Licenses, as defined in the project’s code repositories supporting the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source project.
 
-1. Visibility and credibility
-Being accepted into a foundation signals maturity and open governance. It gives the project a stamp of approval that builds trust with users, contributors, and companies. It also increases visibility through the foundation’s events, website, and communication channels.
+## Technical Steering Committee
 
+The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project.
 
-2. Community growth
-Foundations help projects attract more contributors by connecting them to a larger ecosystem. Collaboration becomes easier, and it’s more likely that the project will get code contributions, bug reports, documentation help, and broader adoption.
+The initial TSC voting members are individuals listed on PLACEHOLDER.  The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the CONTRIBUTING file.
 
+At the inception of the project, details concerning organization and decision making of sub-projects will be documented by the TSC in a TSC or similar repository maintained for this purpose.
 
-3. Neutral governance
-The project is no longer controlled by a single company or individual. A foundation provides a neutral home with shared decision-making and technical steering, which is important for long-term sustainability and fairness.
+Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person.
 
+TSC projects generally will involve Contributors and Code Owners. The TSC may adopt or modify roles so long as the roles are documented publicly. Unless otherwise documented:
 
-4. Easier adoption
-Companies are more likely to adopt foundation-hosted projects because they are seen as stable, vendor-neutral, and well-maintained. Being part of an ecosystem of related projects also makes integration and deployment easier.
+Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project;
 
+Code Owners are Contributors who have earned the ability to modify (“commit”) source code, documentation or other technical artifacts in a project’s repository; and
 
-5. Technical and infrastructure support
-Foundations often provide services like CI/CD pipelines, security audits, and release infrastructure. This lets the maintainers focus more on development and less on operations.
 
+A Contributor may become a Code Owners by a majority approval of the existing Code Owners. A Code Owner may be removed by a majority approval of the other existing Code Owners.
 
-6. Roadmap alignment and standards
-Foundations encourage transparent development processes, open roadmaps, and alignment with broader industry standards. This helps keep the project relevant and interoperable with others.
+Participation in the Project through becoming a Contributor and Code Owner is open to anyone so long as they abide by the terms of this Charter.
 
+The TSC may (1) establish work flow procedures for the submission, approval, and closure/archiving of projects, (2) set requirements for the promotion of Contributors to Code Owner status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, and Code Owners, and create new roles, and publicly document any TSC roles, as it sees fit.
+
+The TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC.  The TSC Chair, or any other TSC member so designated by the TSC, will serve as the primary communication contact between the Project and NeoNephos Foundation, a directed fund of The Linux Foundation.
+
+Responsibilities: The TSC will be responsible for all aspects of oversight relating to the Project, which may include:
+
+- coordinating the technical direction of the Project;
+- approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope);
+- organizing sub-projects and removing sub-projects;
+- creating sub-committees or working groups to focus on cross-project technical issues and requirements;
+- appointing representatives to work with other open source or open standards communities;
+- establishing community norms, workflows, issuing releases, and security issue reporting policies;
+- approving and implementing policies and processes for contributing to be published publicly and coordinating with LF Europe to resolve matters or concerns that may arise as set forth in Section 7 of this Charter;
+- discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and
+- coordinating any marketing, events, or communications regarding the Project.
+
+## TSC Voting
+
+While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis.
+
+Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met but will be prevented from making any decisions at the meeting.
+
+Except as provided in Section 7.c. and 8.a, decisions by vote at a meeting require a majority vote of those in attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TSC.
+
+In the event a vote cannot be resolved by the TSC, TSC goes to TAC to resolve it.
+
+## Compliance with Policies
+
+Contributors will comply with the policies of LF Europe as may be adopted and amended by LF Europe, including, without limitation the policies listed at https://linuxfoundation.eu/policies/.
+
+The TSC may adopt a code of conduct (“CoC”) for the Project, which is subject to approval by LF Europe.  In the event that a Project-specific CoC has not been approved, the LF Europe Code of Conduct listed at https://linuxfoundation.eu/policies/ will apply for all Collaborators in the Project.
+
+When amending or adopting any policy applicable to the Project, LF Europe will publish such policy, as to be amended or adopted, on its web site at least 30 days prior to such policy taking effect; provided, however, that in the case of any amendment of the Trademark Policy or Terms of Use of LF Europe, any such amendment is effective upon publication on LF Project’s web site.
+
+All Collaborators must allow open participation from any individual or organization meeting the requirements for contributing under this Charter and any policies adopted for all Collaborators by the TSC, regardless of competitive interests. Put another way, the Project community must not seek to exclude any participant based on any criteria, requirement, or reason other than those that are reasonable and applied on a non-discriminatory basis to all Collaborators in the Project community.
+
+The Project will operate in a transparent, open, collaborative, and ethical manner at all times. The output of all Project discussions, proposals, timelines, decisions, and status should be made open and easily visible to all. Any potential violations of this requirement should be reported immediately to LF Europe.
+
+## Community Assets
+
+LF Europe will hold title to all trade or service marks used by the Project (“Project Trademarks”), whether based on common law or registered rights.  Project Trademarks will be transferred and assigned to LF Europe to hold on behalf of the Project. Any use of any Project Trademarks by Collaborators in the Project will be in accordance with the license from LF Europe and inure to the benefit of LF Europe.
+
+The Project will, as permitted and in accordance with such license from LF Europe, develop and own all Project GitHub and social media accounts, and domain name registrations created by the Project community.
+
+Under no circumstances will LF Europe be expected or required to undertake any action on behalf of the Project that is inconsistent with the tax-exempt status or purpose, as applicable, of LF Europe.
+
+## General Rules and Operations.
+
+The Project will:
+- engage in the work of the Project in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of LF Europe and other partner organizations in the open source community; and
+- respect the rights of all trademark owners, including any branding and trademark usage guidelines.
+
+
+## Intellectual Property Policy
+
+Collaborators acknowledge that the copyright in all new contributions will be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the Project.
+
+Except as described in Section 7.c., all contributions to the Project are subject to the following:
+
+All new inbound code contributions to the Project must be made using Apache 2.0 or MIT (Project Licenses).
+
+All new inbound code contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate.org) sign-off in the source code system that is submitted through a TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license;
+
+All outbound code will be made available under the Project Licenses.
+
+
+
+Documentation will be received and made available by the Project under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/).
+
+
+
+The Project may seek to integrate and contribute back to other open source projects (“Upstream Projects”). In such cases, the Project will conform to all license requirements of the Upstream Projects, including dependencies, leveraged by the Project.  Upstream Project code contributions not stored within the Project’s code repositories will comply with the contribution process and license terms for the applicable Upstream Project.
+
+The TSC may approve the use of an alternative open license or licenses for inbound or outbound contributions on an exception basis, provided, however, that any use of non-permissive open license must be thoroughly documented and described to the TSC and it is expected that such approved exceptions will be limited. To request an exception, please describe the contribution, the alternative open source license(s), and the justification for using an alternative open source license for the Project. License exceptions must be approved by a two-thirds vote of the entire TSC.
+
+Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file.
+
+## Amendments
+
+This charter may be amended by a two-thirds vote of the entire TSC and is subject to approval by LF Europe.