From f0123ba60ea4e511dc07de544c0b9a65fbf7c533 Mon Sep 17 00:00:00 2001 From: Jeff Diecks <55294502+GeauxJD@users.noreply.github.com> Date: Tue, 14 Oct 2025 17:22:24 -0400 Subject: [PATCH 1/4] Add CONTRIBUTING.md guide Signed-off-by: Jeff Diecks <55294502+GeauxJD@users.noreply.github.com> --- CONTRIBUTING.md | 54 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 00000000..4e97dfa9 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,54 @@ +# Contributing to the OpenSSF Best Practices for Open Source Developers Working Group + +Welcome! We're excited that you're interested in contributing to the Best Practices for Open Source Developers Working Group. We aim to create a supportive, inclusive environment where everyone can thrive and make meaningful contributions. + +## How to Connect with Us + +- **Public Calendar:** Stay informed about our meetings, events, and activities by checking our [public calendar](https://openssf.org/calendar/). + +- **Slack Channel:** Join the conversation on our #wg-best-practices-ossdev [OpenSSF Slack channel](https://openssf.slack.com/archives/C01AHCRP8BT). This is the best place to ask questions, share ideas, and collaborate. + +## How to Contribute + +We value all contributions, from improving documentation to participating in discussions and developing new initiatives. Here’s how you can get started: + +### 1. Participate in Discussions + +- Join our #wg-best-practices-ossdev channel via the [OpenSSF Slack channel](https://openssf.slack.com/archives/C01AHCRP8BT). + +- Attend working group meetings listed on the public calendar. + +### 2. Report Issues or Suggest Enhancements + +- Use the [GitHub Issues](https://github.com/ossf/wg-best-practices-os-developers/issues) tab to report problems or suggest ideas. +- Follow our issue template to provide clear and detailed information. + +### 3. Submit Pull Requests + +- Fork the repository. +- Create a feature branch (`git checkout -b feature/your-feature-name`). +- Commit changes (`git commit -m 'Add your message here'`). +- See here for more information on [signing your commit](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits). +- Push your branch (`git push origin feature/your-feature-name`). +- Open a Pull Request (PR) with a detailed description. +- + +### 4. Review Process + +- All PRs are reviewed by maintainers. +- Ensure your PR is well-documented and follows project guidelines. +- Be open to feedback and ready to make improvements. + +## Code of Conduct + +We are committed to maintaining a welcoming, inclusive, and respectful environment. Please read and follow our [Code of Conduct](https://github.com/ossf/wg-best-practices-os-developers/blob/main/code-of-conduct.md) to ensure a positive experience for everyone. + +## Community Expectations + +- **Be Respectful:** Value each other's ideas and contributions. +- **Be Collaborative:** Work together to solve problems and build new initiatives. +- **Be Open:** Share your knowledge and be open to learning from others. + +We’re excited to collaborate with you and appreciate your support in advancing open source cybersecurity! + +For any questions or additional guidance, contact us through Slack or during our working group meetings. \ No newline at end of file From 52c9cf1975f8e7c92b3e6a2f8c62ab1e35ba53c3 Mon Sep 17 00:00:00 2001 From: Jeff Diecks <55294502+GeauxJD@users.noreply.github.com> Date: Tue, 14 Oct 2025 17:31:22 -0400 Subject: [PATCH 2/4] Fix lint markdown issue Signed-off-by: Jeff Diecks <55294502+GeauxJD@users.noreply.github.com> --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4e97dfa9..b1ec1e38 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -51,4 +51,4 @@ We are committed to maintaining a welcoming, inclusive, and respectful environme We’re excited to collaborate with you and appreciate your support in advancing open source cybersecurity! -For any questions or additional guidance, contact us through Slack or during our working group meetings. \ No newline at end of file +For any questions or additional guidance, contact us through Slack or during our working group meetings. From d56e68425db17da08a3a6091a6e5117ccfc5ed81 Mon Sep 17 00:00:00 2001 From: Jeff Diecks <55294502+GeauxJD@users.noreply.github.com> Date: Tue, 21 Oct 2025 10:03:28 -0400 Subject: [PATCH 3/4] Update CONTRIBUTING.md Co-authored-by: Georg Kunz Signed-off-by: Jeff Diecks <55294502+GeauxJD@users.noreply.github.com> --- CONTRIBUTING.md | 1 - 1 file changed, 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b1ec1e38..7a52317f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -31,7 +31,6 @@ We value all contributions, from improving documentation to participating in dis - See here for more information on [signing your commit](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits). - Push your branch (`git push origin feature/your-feature-name`). - Open a Pull Request (PR) with a detailed description. -- ### 4. Review Process From 23eaabccf5fdcaa7460bafdbf8cd19ae148211db Mon Sep 17 00:00:00 2001 From: Jeff Diecks <55294502+GeauxJD@users.noreply.github.com> Date: Tue, 21 Oct 2025 10:03:40 -0400 Subject: [PATCH 4/4] Update CONTRIBUTING.md Co-authored-by: Georg Kunz Signed-off-by: Jeff Diecks <55294502+GeauxJD@users.noreply.github.com> --- CONTRIBUTING.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 7a52317f..2cf0ba43 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -37,6 +37,7 @@ We value all contributions, from improving documentation to participating in dis - All PRs are reviewed by maintainers. - Ensure your PR is well-documented and follows project guidelines. - Be open to feedback and ready to make improvements. +- Don't hesitate to post a reminder if you didn't get any feedback after some time, e.g. two weeks. ## Code of Conduct