diff --git a/config.yaml b/config.yaml index 1f99991..508ce79 100644 --- a/config.yaml +++ b/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/___) @@ -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 diff --git a/content/en/communication.md b/content/en/communication.md index 3a0cd8b..deb590c 100644 --- a/content/en/communication.md +++ b/content/en/communication.md @@ -13,7 +13,7 @@ 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) @@ -21,7 +21,7 @@ We offer several communication channels to learn, share your knowledge and conne *** -### Discord +### Discord Discord allows the users to communicate in different channels, publicly as well as privately diff --git a/content/en/contribute.md b/content/en/contribute.md index d7060ba..5244aae 100644 --- a/content/en/contribute.md +++ b/content/en/contribute.md @@ -1,93 +1,215 @@ --- -title: Contribute to openms +title: Contributing to OpenMS sidebar: false --- -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. +# Contributing to OpenMS -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 -[GitHub](http://github.com/openms/openms) (open an -[issue](https://github.com/openms/openms/issues) or comment on a relevant -issue). +Welcome! The OpenMS project welcomes your expertise and enthusiasm. This guide helps you understand how to get involved, whether you're writing code, improving documentation, helping with community outreach, or contributing in other ways. -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). +OpenMS is an open-source project focused on developing software for mass spectrometry data analysis and management. The project brings together researchers, developers, and users from across academia and industry. + +--- + +## Getting Started + +If you are new to the project, here are good first steps: + +1. Learn about the **project structure and governance** +2. Join the **communication channels** +3. Explore **ways to contribute** +4. Find a **good first contribution** + +You do not need to understand the entire codebase before contributing—many contributors begin with documentation improvements, bug reports, or small fixes. + +**For code contributors**: See the [CONTRIBUTING.md guide](https://github.com/OpenMS/OpenMS/blob/develop/CONTRIBUTING.md) in the main repository for specific instructions on reporting issues, submitting pull requests, and following OpenMS coding conventions. + +**For technical documentation**: See the [OpenMS Developer Guide](https://openms.readthedocs.io/en/latest/manual/develop.html) for coding conventions, building OpenMS, and architectural details. + +--- + +## Communication Channels + +Most project discussions take place through the OpenMS GitHub organization and the OpenMS Discord server. + +### GitHub Issues and Pull Requests + +Used for **formal discussions** related to the project: + +- bug reports +- feature requests +- development discussions +- proposing code changes +- reviewing contributions + +If you encounter a problem with OpenMS or want to propose an improvement, opening a [GitHub issue](https://github.com/openms/openms/issues) is usually the best place to start. + +### Discord + +For **informal discussions and quick questions**, join the OpenMS Discord server: + +https://discord.gg/v9tv5BxPch + +Discord is useful for: + +- asking quick questions +- discussing ideas before opening an issue +- connecting with other contributors +- general community interaction + +While Discord is helpful for informal communication, important technical discussions and decisions should generally be recorded on GitHub so they remain searchable and accessible to the wider community. + +### Mailing Lists + +If you're unsure where to start or how your skills fit in, you can also ask on the [mailing list](https://lists.sourceforge.net/lists/listinfo/open-ms-general/). 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). -Our community aspires to treat everyone equally and to value all -contributions. We have a [Code of Conduct](/code-of-conduct) to foster an open -and welcoming environment. +### Project Meetings + +Governance discussions also take place during meetings of the Executive Committee. Minutes from these meetings are recorded and made publicly available. -### Writing code +--- + +## Code of Conduct + +Our community aspires to treat everyone equally and to value all contributions. We have a [Code of Conduct](/code-of-conduct) to foster an open and welcoming environment. + +--- -Programmers, this -[guide](https://github.com/OpenMS/OpenMS/blob/develop/CONTRIBUTING.md) -explains how to contribute to the OpenMS codebase. +## Ways to Contribute + +Your choices aren't limited to programming—there are many areas where we need **your** help. + +### Writing Code + +Programmers, the [CONTRIBUTING.md guide](https://github.com/OpenMS/OpenMS/blob/develop/CONTRIBUTING.md) explains how to contribute to the OpenMS codebase. + +### Reviewing Pull Requests + +The project has more than 45+ open pull requests—meaning many potential improvements and many open-source contributors waiting for feedback. If you're a developer who knows OpenMS, you can help even if you're not familiar with the entire codebase. You can: -### Reviewing pull requests -The project has more than 45+ open pull requests -- meaning many potential -improvements and many open-source contributors waiting for feedback. If you're -a developer who knows openms, you can help even if you're not familiar with the -codebase. You can: * summarize a long-running discussion * triage documentation PRs * test proposed changes +### Developing Educational Materials -### Developing educational materials +OpenMS's [User Guide](https://github.com/OpenMS/OpenMS/wiki) is undergoing rehabilitation. We're in need of new tutorials, how-to's, and deep-dive explanations, and the site needs restructuring. Opportunities aren't limited to writers. We'd also welcome worked examples, notebooks, and videos. [OpenMS-Docs](https://github.com/OpenMS/OpenMS-docs/issues) lays out our ideas—and you may have others. -openms's [User Guide](https://github.com/OpenMS/OpenMS/wiki) is undergoing rehabilitation. -We're in need of new tutorials, how-to's, and deep-dive explanations, and the -site needs restructuring. Opportunities aren't limited to writers. We'd also -welcome worked examples, notebooks, and videos. [OpenMS-Docs](https://github.com/OpenMS/OpenMS-docs/issues) -lays out our ideas -- and you may have others. +### Issue Triaging - -### Issue triaging - -The [OpenMS issue tracker](https://github.com/openms/openms/issues) has a _lot_ -of open issues. Some are no longer valid, some should be prioritized, and some -would make good issues for new contributors. You can: +The [OpenMS issue tracker](https://github.com/openms/openms/issues) has a _lot_ of open issues. Some are no longer valid, some should be prioritized, and some would make good issues for new contributors. You can: * check if older bugs are still present * find duplicate issues and link related ones * add good self-contained reproducers to issues -* label issues correctly (this requires triage rights -- just ask) +* label issues correctly (this requires triage rights—just ask) Please just dive in. +### Website Development -### Website development +We've just revamped our website, but we're far from done. If you love web development, these [issues](https://github.com/openms/openms.de/issues) list some of our unmet needs—and feel free to share your own ideas. -We've just revamped our website, but we're far from done. If you love web -development, these -[issues](https://github.com/openms/openms.de/issues) -list some of our unmet needs -- and feel free to share your own ideas. +### Graphic Design +We can barely begin to list the contributions a graphic designer can make here. Our docs are parched for illustration; our growing website craves images—opportunities abound. -### Graphic design +### Community Coordination and Outreach -We can barely begin to list the contributions a graphic designer can make here. -Our docs are parched for illustration; our growing website craves images -- -opportunities abound. +Through community contact we share our work more widely and learn where we're falling short. We're eager to get more people involved in efforts like our [Twitter](https://twitter.com/OpenMSTeam) account, organizing events, a newsletter, and perhaps a blog. -### Community coordination and outreach +### Fundraising -Through community contact we share our work more widely and learn where we're -falling short. We're eager to get more people involved in efforts like our -[Twitter](https://twitter.com/OpenMSTeam) account, organizing openms, a newsletter, and perhaps a blog. +OpenMS was all-volunteer for many years, but as its importance grew it became clear that to ensure stability and growth we'd need financial support. Like all the nonprofit world, we're constantly searching for grants, sponsorships, and other kinds of support. We have a number of ideas and of course we welcome more. Fundraising is a scarce skill here—we'd appreciate your help. -### Fundraising +You can also donate using our [OpenCollective](https://opencollective.com/openms) account. + +--- + +## Understanding the Project + +OpenMS is organized as both an **open-source software project** and a **nonprofit organization** that supports its development. + +### Governance + +The governance of the project is described in the following documents: + +- [Governance]({{< relref "/governance" >}}) — overview of project governance structure +- [Executive Committee]({{< relref "/exec_committee" >}}) — primary governance body of the project +- [Core Developers]({{< relref "/core_developers" >}}) — trusted maintainers who guide the project + +In general: + +- **Core developers** maintain the project and participate in governance +- The **Executive Committee** guides the direction of the project +- **Contributors** submit improvements, fixes, and new features + +Anyone is welcome (and encouraged!) to contribute to OpenMS. + +### Main Repositories + +The most important repositories in the OpenMS GitHub organization are: + +- **[OpenMS](https://github.com/OpenMS/OpenMS/)** — The main codebase containing algorithms, tools, and core libraries, as well as Python bindings for PyOpenMS + +- **[OpenMS-docs](https://github.com/OpenMS/OpenMS-docs)** — Documentation sources for the OpenMS ReadTheDocs site + +- **[pyopenms-docs](https://github.com/OpenMS/pyopenms-docs)** — Documentation sources for the pyOpenMS Python interface + +- **[streamlit-template](https://github.com/OpenMS/streamlit-template)** — A template for building lightweight web applications around OpenMS tools + +- **[OpenMS-website](https://github.com/OpenMS/OpenMS-website)** — Source repository for the OpenMS project website + +There are additional repositories for tutorials, experimental features, and supporting infrastructure. + +--- + +## Finding Something to Work On + +If you would like to contribute but are unsure where to start, there are many possible ways to get involved. + +Examples include: + +- improving documentation +- fixing bugs +- adding tests +- improving build infrastructure +- implementing new algorithms + +Issues labeled **"good first issue"** are often a good place for new contributors to begin. + +If you are unsure where to start, feel free to ask for suggestions on the [OpenMS Discord Server](https://discord.gg/v9tv5BxPch), or by opening a [GitHub issue](https://github.com/OpenMS/OpenMS/issues). + +--- + +## Contributor Path + +Many contributors start by reporting issues or submitting small fixes. Over time, contributors may become more involved in the development of the project. + +A typical progression in open-source projects looks like this: + +- **User** — uses the software and provides feedback +- **Contributor** — submits improvements, bug reports, or fixes +- **Frequent contributor** — regularly contributes to the project +- **Core developer** — trusted maintainer who guides the project + +Core developers are trusted maintainers who help guide the project and participate in governance. + +More information about this role is available on the [Core Developers]({{< relref "/core_developers" >}}) page. + +--- + +## Next Steps + +To continue exploring the project, you may want to: + +- read the [CONTRIBUTING.md guide](https://github.com/OpenMS/OpenMS/blob/develop/CONTRIBUTING.md) for code contribution guidelines +- read the [developer documentation](https://openms.readthedocs.io/en/latest/manual/develop.html) for technical details +- explore the [OpenMS repositories](https://github.com/OpenMS) +- review [open issues](https://github.com/OpenMS/OpenMS/issues) +- submit your first [pull request](https://github.com/OpenMS/OpenMS/pulls) -OpenMS was all-volunteer for many years, but as its importance grew it became -clear that to ensure stability and growth we'd need financial support. Like all the nonprofit world, we're -constantly searching for grants, sponsorships, and other kinds of support. We -have a number of ideas and of course we welcome more. Fundraising is a scarce -skill here -- we'd appreciate your help. +We are glad you are interested in contributing to OpenMS! -You can also donate using our [opencollective](https://opencollective.com/openms) account. diff --git a/content/en/contributors.md b/content/en/contributors.md index 8a35016..b1d140e 100644 --- a/content/en/contributors.md +++ b/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" >}}). + diff --git a/content/en/core_developers.md b/content/en/core_developers.md new file mode 100644 index 0000000..c22ea25 --- /dev/null +++ b/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 [Contributing Guide]({{< relref "/contribute" >}}). diff --git a/content/en/exec_committee.md b/content/en/exec_committee.md new file mode 100644 index 0000000..5884b7e --- /dev/null +++ b/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 [Contributing Guide]({{< relref "/contribute" >}}). diff --git a/content/en/governance.md b/content/en/governance.md new file mode 100644 index 0000000..70ebafa --- /dev/null +++ b/content/en/governance.md @@ -0,0 +1,70 @@ +--- +title: "Governance" +--- + +# Governance Structure of OpenMS + +OpenMS is governed through two complementary structures: a **nonprofit corporation** that provides legal and financial support, and an **Executive Committee** that guides the technical development and community governance of the project. + +This page provides an overview of how the project is organized and makes decisions. + +--- + +## OpenMS Inc. + +[OpenMS Inc.]({{< relref "/about" >}}) is a U.S. nonprofit corporation organized under section 501(c)(3) of the Internal Revenue Code. It provides legal and financial infrastructure to support the development of the OpenMS software project. + +The corporation is governed by a **Board of Directors** responsible for fiduciary oversight, legal compliance, and financial management. + +For more information about the nonprofit entity, see the [about page]({{< relref "/about" >}}). + +--- + +## Executive Committee + +The [Executive Committee]({{< relref "/exec_committee" >}}) is the primary governance body of the OpenMS project itself. It is composed of the **core developers** and is led by an elected **Executive Chairperson**. + +The Executive Committee is responsible for: + +- Defining the mission, direction, and vision of OpenMS +- Guiding technical development and resource allocation +- Maintaining project bylaws and governance policies +- Managing the list of core developers +- Addressing Code of Conduct issues + +The committee meets regularly to coordinate project development and governance. Meeting minutes are made publicly available to ensure transparency. + +For detailed information about the committee's responsibilities, meeting procedures, and decision-making processes, see the [Executive Committee page]({{< relref "/exec_committee" >}}). + +--- + +## Core Developers + +[Core developers]({{< relref "/core_developers" >}}) are trusted maintainers who play a central role in the development and governance of OpenMS. They collectively form the Executive Committee. + +Core developers: + +- Review and approve contributions to the codebase +- Help guide the technical direction of the project +- Support and mentor new contributors +- Participate in governance decisions + +New core developers are added by a majority vote of the Executive Committee. Core developers may step down voluntarily or be removed due to inactivity or Code of Conduct violations by a two-thirds vote of the committee. + +For more information about the role and responsibilities of core developers, see the [Core Developers page]({{< relref "/core_developers" >}}). + +--- + +## Relationship Between the Corporation and the Project + +**Corporate governance** (handled by the Board of Directors) focuses on the legal entity, finances, and nonprofit compliance. + +**Project governance** (handled by the Executive Committee) focuses on software development, technical direction, and community management. + +This separation allows the project to benefit from the legal and financial stability provided by the nonprofit corporation while maintaining independent technical governance by the community of core developers. + +--- + +## See Also + +For guidance on getting started as a contributor, see the [Contributing Guide]({{< relref "/contribute" >}}). diff --git a/content/en/news/GSoC2025.md b/content/en/news/GSoC2025.md index 6876b21..53ad112 100644 --- a/content/en/news/GSoC2025.md +++ b/content/en/news/GSoC2025.md @@ -19,7 +19,7 @@ summary: The OpenMS team applies as an organization for GSoC 2025 and invites th - remember the [GSOC 2025 timeline](https://developers.google.com/open-source/gsoc/timeline) - Read the [DOs and DON'Ts document](https://opensource.googleblog.com/2011/03/dos-and-donts-of-google-summer-of-code.html) to gauge your interest in participating in this year's GSoC 2025. - remember the [GSOC 2025 timeline](https://developers.google.com/open-source/gsoc/timeline) -- Review the list of themes and the projects available within. If you have specific questions about a project, our mentors are active on [Discord](https://discord.com/invite/4TAGhqJ7s5) and we will happily assist you. +- Review the list of themes and the projects available within. If you have specific questions about a project, our mentors are active on [Discord](https://discord.gg/v9tv5BxPch) and we will happily assist you. - Follow our instructions below on how to submit a proposal to us. --- diff --git a/content/en/news/GSoC2026.md b/content/en/news/GSoC2026.md index cf018e9..9ec3500 100644 --- a/content/en/news/GSoC2026.md +++ b/content/en/news/GSoC2026.md @@ -14,7 +14,7 @@ summary: The OpenMS team applies as an organization for GSoC 2026 and invites th ## GSoC Contributors - Make sure you are [eligible](https://summerofcode.withgoogle.com/get-started) to participate in GSoC 2026. -- Review the list of themes and the projects available within. If you have specific questions about a project, our mentors are active on [Discord](https://discord.com/invite/4TAGhqJ7s5) and we will happily assist you. +- Review the list of themes and the projects available within. If you have specific questions about a project, our mentors are active on [Discord](https://discord.gg/v9tv5BxPch) and we will happily assist you. - Follow our instructions below on how to submit a proposal to us. ---