Add governance page and links from homepage

config.yaml

@@ -42,7 +42,7 @@ languages:
         # Hero subtitle (optional)
         subtitle: The open-source framework for Mass Spectrometry
         # Button text
-        buttontext: Get started
+        buttontext: Install
         # Where the main hero button links to
         buttonlink: https://openms.readthedocs.io/en/latest/about/installation.html
         # Hero image (from static/images/___)
@@ -84,9 +84,9 @@ languages:
             - title: Create high-performance tools
               subtitle: Develop high-performance tools or algorithms with the C++ OpenMS library
               terminal: true
-              buttonText: Get Started
+              buttonText: Start Contributing
               bottomBorderRadius: true
-              buttonLink: "https://abibuilder.cs.uni-tuebingen.de/archive/openms/Documentation/nightly/html/OpenMS_tutorial.html"
+              buttonLink: "/onboarding"
 
       keyfeatures:
         title: What is OpenMS ?
@@ -133,9 +133,7 @@ languages:
         logo:
         socialmediatitle: ""
         socialmedia:
-          - link: https://github.com/OpenMS/OpenMS
-            icon: github
-          - link: https://discord.com/invite/4TAGhqJ7s5
+          - link: https://discord.gg/v9tv5BxPch
             icon: discord
         quicklinks:
           column1:
@@ -150,20 +148,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 +195,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/communication.md

@@ -13,15 +13,15 @@ Here's how to get started:
 
 - 📚 Browse through the main library code under [OpenMS/OpenMS](https://github.com/openms/openms/issues)
 - 👩‍💻 Check out the [documentation](https://openms.readthedocs.io/en/latest/index.html).
-- 🙋‍♀️ Come and say hi on our [![Discord Shield](https://img.shields.io/discord/832282841836159006?style=flat-square&message=Discord&color=5865F2&logo=Discord&logoColor=FFFFFF&label=Discord)](https://discord.gg/4TAGhqJ7s5) channel.
+- 🙋‍♀️ Come and say hi on our [![Discord Shield](https://img.shields.io/discord/832282841836159006?style=flat-square&message=Discord&color=5865F2&logo=Discord&logoColor=FFFFFF&label=Discord)](https://discord.gg/v9tv5BxPch) channel.
 - 🍿 Tune in for news about developer/user meetings and events, [get involved]({{< ref "news.md" >}})!
 - 🌈 Please abide by our [community code of conduct](https://github.com/OpenMS/OpenMS/blob/develop/CODE_OF_CONDUCT.md)
 
 We offer several communication channels to learn, share your knowledge and connect with others within the OpenMS community.
 
 ***
 
-### <a class="button cta rounded primary-btn raised" href="https://discord.gg/aJyWqf6uCn">Discord</a>
+### <a class="button cta rounded primary-btn raised" href="https://discord.gg/v9tv5BxPch">Discord</a>
 
 Discord allows the users to communicate in different channels, publicly as well as privately
 

content/en/contribute.md

@@ -7,6 +7,8 @@ The OpenMS project welcomes your expertise and enthusiasm!
 Your choices aren't limited to programming, as you can
 see below there are many areas where we need **your** help.
 
+**New to the project?** Check out our [Contributor Onboarding Guide]({{< relref "/onboarding" >}}) to learn about project structure, communication channels, and how to get started.
+
 If you're unsure where to start or how your skills fit in, _reach out!_ You
 can ask on the [mailing
 list](https://lists.sourceforge.net/lists/listinfo/open-ms-general/) or
@@ -15,7 +17,7 @@ list](https://lists.sourceforge.net/lists/listinfo/open-ms-general/) or
 issue).
 
 Those are our preferred channels (open source is open by nature), but
-if you prefer to talk privately, contact our community coordinators on the [OpenMS Discord Server](https://discord.gg/aJyWqf6uCn).
+if you prefer to talk privately, contact our community coordinators on the [OpenMS Discord Server](https://discord.gg/v9tv5BxPch).
 
 If you only want to be informed of new versions of OpenMS, please subscribe to the mailing list [open-ms-announcements](https://lists.sourceforge.net/lists/listinfo/open-ms-announcements).
 

content/en/contributors.md

@@ -11,4 +11,5 @@ 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 the [Executive Committee page]({{< relref "/exec_committee" >}}).
+

content/en/core_developers.md

@@ -0,0 +1,120 @@
+---
+title: "Core Developers"
+---
+
+# 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.
+
+---
+
+## See Also
+
+For guidance on getting started as a contributor, see the [Contributor Onboarding Guide]({{< relref "/onboarding" >}}).

content/en/exec_committee.md

@@ -0,0 +1,110 @@
+---
+title: "Executive Committee"
+---
+
+# 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.
+
+---
+
+## See Also
+
+For guidance on getting started as a contributor, see the [Contributor Onboarding Guide]({{< relref "/onboarding" >}}).