From 39baac8ba267ca90f45c3533e51e1c4ea5343e9d Mon Sep 17 00:00:00 2001 From: iGufrankhan Date: Sun, 7 Dec 2025 12:19:18 +0530 Subject: [PATCH 1/2] docs: improve newcomer onboarding in CONTRIBUTING.md Signed-off-by: iGufrankhan --- CONTRIBUTING.md | 42 +++++++++++++++++++++++++++++++----------- 1 file changed, 31 insertions(+), 11 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4df2a8dff..eb877eac7 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -5,17 +5,37 @@ We love to pull requests from everyone! We follow the standard Git workflow of ` If you are new to open source, we recommend GitHub's excellent guide on "[How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)". In addition, please feel free to reach out to any of the maintainers or other community members if you are struggling as we are here to help you learn! Before getting started, please make sure you've read the [README](README.md) to get a primer on our project. Augur's documentation can be found [here](https://oss-augur.readthedocs.io/en/main/). - -## Join the Community - -We encourage all contributors to join the [CHAOSS Slack workspace](https://chaoss.community/kb-getting-started/) and participate in the `#wg-augur-8knot` channel. This is a great place to ask questions, get help with issues, participate in discussions, and stay updated on community meetings and planning. Don't hesitate to introduce yourself and ask for help if you get stuck! - -## Opening an issue -If you're experiencing an issue with Augur or have a question you'd like help answering, please feel free to open an [issue](https://github.com/chaoss/augur/issues). To help us prevent duplicates, we kindly ask that you briefly search for your problem or question in our [issues](https://github.com/chaoss/augur/issues) before opening a new one. - -Please note that if you open a bug report and your issue **does not** follow our template, we cannot help you until you have provided us all the relevant information in that format. -Respectfully, we do not have the time to try and recreate an error given with minimal or no context, so by providing this information you are helping us help you! - +## Your Journey from Newcomer to Confident Contributor +New to open source or Augur? Here's how most people get started. Go at your own pace. +### 1. Join the Community & Learn How Things Work +- **Join Slack**: Go to the [CHAOSS Community getting started guide](https://chaoss.community/kb-getting-started/) to join the community Slack workspace and introduce yourself in `#wg-augur-8knot`. +- **Read CHAOSS Docs**: Look at the [Code of Conduct](https://chaoss.community/code-of-conduct/) and browse the [CHAOSS website](https://chaoss.community/) +- **Review this CONTRIBUTING.md**: Get familiar with our contribution guidelines and current project policies +- **Attend Meetings**: Check the [CHAOSS calendar](https://chaoss.community/chaoss-calendar/) for meetings like: + - Newcomer Hangout + - Community Call + - Augur/8-Knot Software Working Group +- **Watch Recordings**: Find past meetings on the [CHAOSS YouTube channel](https://www.youtube.com/@CHAOSStube) +- **Request a Tour Guide** (Optional): Not sure where to start? Ask in the `#newcomers` Slack channel for 1:1 help +### 2. Run Augur +- **Read the Docs**: Start at [Augur documentation](https://oss-augur.readthedocs.io/en/main/) (check out the Docker setup guide) +- **Install Augur**: Follow the installation instructions [getting-started-guide](https://oss-augur.readthedocs.io/en/main/getting-started/toc.html) to get it running on your machine +- **Getting Started Video**: Set up and run Augur on [YouTube](https://www.youtube.com/watch?v=SXLnWwwSsSE) +### 3. Start with Good First Issues +1. Go to the [issues page](https://github.com/chaoss/augur/issues). +2. Use the **Labels** filter to narrow down issues: + - [`good first issue`](https://github.com/chaoss/augur/labels/good%20first%20issue) — recommended for new contributors. + - [`first-timers-only`](https://github.com/chaoss/augur/issues?q=state%3Aopen+label%3Afirst-timers-only) — specifically for first-time contributions. +3. Choose an issue that looks manageable and interesting. +4. If you find a bug or something unclear, open an issue or ask for guidance before starting work. +### 4. Need Help? +- Ask questions in the Slack workspace linked above. +- Bring questions to community meetings. +- Comment on the issue or PR you're working on. +### 5. Ready for More? +- Try [`challenging first issue`](https://github.com/chaoss/augur/labels/challenging%20first%20issue) labels +- Look at [`documentation`](https://github.com/chaoss/augur/labels/documentation) or [`tech debt`](https://github.com/chaoss/augur/labels/tech%20debt) issues +- Ask in the Slack workspace linked above what would be a good fit for your interests. ### How to submit a bug report To see the template referred to in the above section, click on **New Issue**, then click on the **Get Started** button on the **Bug Report** option. A dialogue box populated with descriptions of what to put in each section, will pop up on a new page. From 250fb90f943448403de6266bf2e7e8db093760c6 Mon Sep 17 00:00:00 2001 From: iGufrankhan Date: Thu, 12 Feb 2026 16:58:09 +0000 Subject: [PATCH 2/2] docs: improve onboarding flow and refine issue guidance Signed-off-by: iGufrankhan --- CONTRIBUTING.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index eb877eac7..7c4d2857b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -36,6 +36,11 @@ New to open source or Augur? Here's how most people get started. Go at your own - Try [`challenging first issue`](https://github.com/chaoss/augur/labels/challenging%20first%20issue) labels - Look at [`documentation`](https://github.com/chaoss/augur/labels/documentation) or [`tech debt`](https://github.com/chaoss/augur/labels/tech%20debt) issues - Ask in the Slack workspace linked above what would be a good fit for your interests. +## Opening an issue +If you're experiencing an issue with Augur or have a question you'd like help answering, please feel free to open an [issue](https://github.com/chaoss/augur/issues). To help us prevent duplicates, we kindly ask that you briefly search for your problem or question in our [issues](https://github.com/chaoss/augur/issues) before opening a new one. + +Please note that if you open a bug report and your issue **does not** follow our template, we cannot help you until you have provided us all the relevant information in that format. +Respectfully, we do not have the time to try and recreate an error given with minimal or no context, so by providing this information you are helping us help you! ### How to submit a bug report To see the template referred to in the above section, click on **New Issue**, then click on the **Get Started** button on the **Bug Report** option. A dialogue box populated with descriptions of what to put in each section, will pop up on a new page.