Add governance page and links from homepage

config.yaml

@@ -150,20 +150,26 @@ languages:
             links:
               - text: Community
                 link: /communication
-              - text: Contribute
-                link: /contribute
               - text: Code of conduct
                 link: /code-of-conduct
+              - text: Contribute
+                link: /contribute
+              - text: Core Developers
+                link: /core_developers
           column3:
             links:
               - text: OpenMS Inc.
                 link: /about
-              - text: Help
-                link: /help
+              - text: Executive committee
+                link: /exec_committee
+              - text: Governance
+                link: /governance
               - text: Jobs
                 link: /jobs
           column4:
             links:
+              - text: Help
+                link: /help
               - text: Terms of use
                 link: /terms
               - text: Privacy
@@ -191,8 +197,8 @@ languages:
           url: /community
         - title: About Us
           sublinks:
-            - title: OpenMS Inc.
-              url: /about
+            - title: Governance
+              url: /governance
             - title: Contributors
               url: /contributors
           url: /about

content/en/contributors.md

@@ -11,4 +11,4 @@ communities worldwide by building quality, open-source software.
 
 # Governance
 
-For information about the Executive Committee, please see [here]({{< relref "/about" >}}).
+For information about the Executive Committee, please see [here]({{< relref "/exec_committee" >}}).

content/en/core_developers.md

@@ -0,0 +1,110 @@
+# Core Developers
+
+Core developers are trusted contributors who play a central role in maintaining and guiding the OpenMS project. They are active participants in the development of the software and the governance of the project.
+
+Core developers collectively form the **Executive Committee**, which is responsible for the long-term direction and governance of OpenMS.
+
+---
+
+## Role of Core Developers
+
+Core developers serve as maintainers and technical leaders within the project. Their role is to help ensure the quality, sustainability, and collaborative spirit of OpenMS.
+
+Core developers typically:
+
+- Review and approve contributions to the codebase
+- Maintain parts of the software and its infrastructure
+- Guide contributors and help new developers get involved
+- Participate in discussions about project direction
+- Vote on governance matters when required
+
+---
+
+## Responsibilities
+
+Core developers are expected to contribute to the health of the project in several ways.
+
+### Code Review
+
+Core developers review pull requests and help maintain code quality across the project.
+
+Reviews should aim to:
+
+- ensure correctness and maintainability
+- maintain consistency with project architecture
+- provide constructive feedback to contributors
+
+### Collaboration
+
+Core developers help foster a welcoming and collaborative community by:
+
+- providing helpful feedback
+- assisting new contributors
+- encouraging high-quality contributions
+
+### Governance Participation
+
+Core developers participate in project governance through the Executive Committee. This includes:
+
+- discussing project direction
+- participating in votes when necessary
+- helping guide long-term development priorities
+
+---
+
+## Merge Practices
+
+Core developers typically have permission to merge pull requests into the project repositories.
+
+To maintain code quality and transparency, the project follows these norms:
+
+- Pull requests should generally receive review from at least one other core developer before merging.
+- Core developers should avoid merging their own pull requests without review whenever possible.
+
+These practices help ensure that important changes receive adequate oversight.
+
+---
+
+## Becoming a Core Developer
+
+Core developers are individuals who have demonstrated sustained, high-quality contributions to the project and a strong commitment to the OpenMS community.
+
+Typical characteristics include:
+
+- significant technical contributions
+- familiarity with the architecture of the project
+- constructive collaboration with other contributors
+- consistent participation in development discussions
+
+New core developers are added by a **majority vote of a quorum of the Executive Committee**, as defined in the project bylaws.
+
+---
+
+## Activity Expectations
+
+Core developers are expected to remain active participants in the project.
+
+Activity may include:
+
+- contributing code
+- reviewing pull requests
+- participating in governance discussions
+- helping guide the development of the project
+
+Members who become inactive for extended periods may be removed by a vote of the Executive Committee as described in the bylaws.
+
+---
+
+## Transparency
+
+The OpenMS project values transparency in its governance.
+
+Core developers participate in Executive Committee meetings where project governance and major decisions are discussed. Minutes from these meetings are recorded and made publicly available unless the committee decides otherwise.
+
+---
+
+## Current Core Developers
+
+Coming soon
+
+This list is maintained by the Executive Committee and updated as membership changes.

content/en/exec_committee.md

@@ -0,0 +1,100 @@
+# OpenMS Executive Committee
+
+The **Executive Committee** is the primary governance body of the OpenMS project. It is responsible for guiding the technical direction, long-term sustainability, and community governance of OpenMS.
+
+The committee is composed of the **core developers of the project** and is led by an **Executive Chairperson** elected from among its members.
+
+---
+
+## Purpose
+
+The Executive Committee provides leadership for the OpenMS project by:
+
+- Defining the mission, direction, and long-term vision of OpenMS
+- Ensuring the continued sustainability of the project
+- Coordinating development priorities and resources
+- Maintaining governance policies for the project
+- Supporting a healthy and welcoming open-source community
+
+---
+
+## Responsibilities
+
+The Executive Committee is responsible for:
+
+- Determining the **mission, direction, and vision** of the OpenMS project  
+- Planning for the **long-term continuity** of the project  
+- Directing **development resources** in line with the project vision  
+- Maintaining and updating the **project bylaws**  
+- Enhancing the **public image and reputation** of OpenMS  
+- Forming additional committees as needed  
+- Electing the **Executive Chairperson**  
+- Managing the **list of core developers**  
+- Addressing **Code of Conduct issues**
+
+---
+
+## Composition
+
+The Executive Committee consists of the **core developers** of OpenMS.
+
+Core developers are individuals who are active and key participants in the project and who help maintain the software, guide development, and support the community.
+
+### Adding Core Developers
+
+New core developers may be added by a **simple majority vote of a quorum of the Executive Committee**.
+
+### Removal of Core Developers
+
+Core developers may be removed due to inactivity or violation of the Code of Conduct by a **two-thirds majority vote of a quorum of the Executive Committee**, or by request of the member.
+
+---
+
+## Executive Chairperson
+
+The Executive Committee elects an **Executive Chairperson** from among its members for a **one-year term**.
+
+The responsibilities of the Executive Chairperson include:
+
+- Convening and chairing meetings of the Executive Committee
+- Providing notice of meetings to committee members
+- Breaking tie votes when necessary
+
+The Executive Chairperson may be removed by a **two-thirds vote of the Executive Committee**.
+
+---
+
+## Meetings
+
+The Executive Committee meets regularly to coordinate the governance and development of the project.
+
+Meeting rules:
+
+- The committee meets **at least once per calendar month**
+- Meetings are scheduled by the **Executive Chairperson**, or by any committee member if the position is vacant
+- Members must receive **at least 48 hours notice** of meetings
+- A **quorum of five members** is required for votes
+- Proceedings follow **Robert’s Rules of Order Newly Revised** if requested by any committee member
+
+---
+
+## Amendments to the Bylaws
+
+Any member of the Executive Committee may propose amendments to the project bylaws.
+
+The amendment process:
+
+1. A proposed amendment is circulated to all committee members.
+2. The amendment is discussed and voted on at the next regular meeting.
+3. Adoption requires a **two-thirds majority of the quorum**.
+
+---
+
+## Transparency
+
+In keeping with the principles of open science and open-source collaboration:
+
+- Minutes are recorded for meetings of governance committees
+- Meeting minutes are made publicly available unless the committee votes otherwise
+
+This commitment ensures transparency and accountability in the governance of the OpenMS project.

content/en/governance.md

@@ -0,0 +1,133 @@
+
+# Governance Structure of OpenMS
+
+This page describes the governance structure of the OpenMS project and its legal entity. For more information, see:
+
+- [OpenMS Inc.](/about) - The nonprofit corporation supporting the project
+- [Executive Committee](/exec_committee) - The technical governance body
+- [Core Developers](/core_developers) - Maintainers of the project
+
+## Legal Entity: OpenMS Inc.
+
+OpenMS Inc. is a U.S. nonprofit corporation organized under section 501(c)(3) of the Internal Revenue Code. Its mission is to develop open-source scientific software and collaborate with academic institutions to improve experimental data analysis.
+
+Key characteristics:
+
+- nonprofit public-benefit corporation
+- operates for scientific, educational, and charitable purposes
+- may provide internships or volunteer opportunities to support those goals
+- cannot distribute profits to individuals except as reasonable compensation for services
+
+The corporation has no members, meaning governance authority rests entirely with the Board of Directors.
+
+### Board of Directors
+
+The Board of Directors is the governing body of the nonprofit corporation.
+
+Initial directors:
+
+- Samuel Wein
+- Timo Sachsenberg
+- Oliver Kohlbacher
+
+Responsibilities include:
+
+- fiduciary oversight of the corporation
+- legal compliance
+- financial oversight
+- approving amendments to the Articles of Incorporation (2/3 vote)
+- selecting asset recipients if the organization dissolves
+
+This body governs the corporate entity, not the day-to-day development of the software project.
+
+## Executive (Steering) Committee
+
+The Executive Committee governs the OpenMS project itself, separate from the legal corporate board.
+
+Composition:
+
+- core developers of the project
+- led by an Executive Chairperson
+
+Responsibilities include:
+
+- defining project mission, direction, and vision
+- long-term continuity planning
+- directing development resources
+- maintaining project bylaws
+- managing the list of core developers
+- forming committees
+- handling code-of-conduct issues
+
+This committee is effectively the technical and community governance body of the OpenMS project.
+### Core Developers
+
+- Core developers are defined as active and key participants in the project. They collectively form the Executive Committee.
+
+### Executive Chairperson
+
+The chairperson:
+
+- must be a member of the executive committee
+- serves 1-year term
+- is elected by the committee
+- breaks tie votes
+
+Responsibilities:
+
+- convene and chair meetings
+- notify members of meetings
+- coordinate committee activities
+
+Removal requires a 2/3 vote of the executive committee.
+Rules:
+
+**Adding a core developer:**
+
+- simple majority vote of a quorum
+
+**Removing a core developer:**
+
+- 2/3 vote of quorum or voluntary departure
+
+## Executive Committee Operations
+
+**Meeting requirements:**
+
+- at least one meeting per month
+- 48 hours notice
+- quorum: five members
+
+**Decision process:**
+
+- majority vote unless otherwise specified
+- Robert's Rules of Order may be invoked if requested
+
+**Transparency requirement:**
+
+- meeting minutes should be recorded
+- minutes are public unless the committee votes otherwise
+
+## Relationship Between OpenMS Inc. and the OpenMS Executive Committee
+
+### Corporate Governance
+
+Handled by: **Board of Directors**
+
+Responsible for:
+
+- legal entity
+- finances
+- compliance
+- nonprofit obligations
+
+### Project Governance
+
+Handled by: **Executive (Steering) Committee**
+
+Responsible for:
+
+- software development
+- project roadmap
+- community management
+- technical leadership