Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
57 lines (35 loc) · 3.13 KB

CONTRIBUTING.md

File metadata and controls

57 lines (35 loc) · 3.13 KB

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.

  • Slack Channel: Join the conversation on our #wg-best-practices-ossdev OpenSSF Slack channel. This is the best place to ask questions, share ideas, and collaborate.

  • Mailing List: Subscribe to the Best Practices mailing list. You can also manage your subscriptions to all OpenSSF mailing lists.

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.

  • Attend working group meetings listed on the public calendar.

2. Report Issues or Suggest Enhancements

  • Use the GitHub Issues tab to report problems or suggest ideas.
  • Follow our issue template to provide clear and detailed information.
  • Check out our Discussions.

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.
  • 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.
  • Don't hesitate to post a reminder if you didn't get any feedback after some time, e.g. two weeks.

Code of Conduct

We are committed to maintaining a welcoming, inclusive, and respectful environment. Please read and follow our Code of Conduct 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.