Skip to content

Latest commit

 

History

History
66 lines (39 loc) · 3.21 KB

CONTRIBUTING.md

File metadata and controls

66 lines (39 loc) · 3.21 KB
Raw

How to Contribute to the OpenBeta project

👍🎉 First off, thanks for taking the time to contribute! 🎉👍

The following is a set of guidelines for contributing to Open-Tacos and related projects, which are hosted in the OpenBeta Organization on GitHub. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.

Table Of Contents

Code of Conduct

I don't want to read this whole thing, I just have a question!!!

How Can I Contribute?

Code of Conduct

This project and everyone participating in it is governed by the OpenBeta of Conduct. By participating, you are expected to uphold this code.

I don't want to read this whole thing I just have a question!!!

Note: Please don't file an issue to ask a question. You'll get faster results by using the resources below.

We have an official message board where the community chimes in with helpful advice if you have questions.

  • Community — the official OpenBeta community message board

If chat is more your speed, you can join the Discord chat server:

  • Join the Discord chat server
    • Even though Discord is a chat service, sometimes it takes several hours for community members to respond — please be patient!
    • Assign yourself role(s) according the type of climbing often do, eg: bouldering, sport, etc.
    • Under OpenBeta category, use the #general channel for general questions or discussion about contributing to the project.
    • Use the #openbeta-dev channel for technical discussion about our on-going projects.
    • Under Community category, use the #general channel for discussion with other community members.
    • There are many other channels available, check the channel list

How Can I Contribute?

Reporting Bugs

How Do I Submit A (Good) Bug Report?

Explain the problem and include additional details to help maintainers reproduce the problem:

  • Use a clear and descriptive title for the issue to identify the problem.
  • Describe the exact steps which reproduce the problem in as many details as possible.
  • Provide specific examples to demonstrate the steps. Include links to files or GitHub projects, or copy/pasteable snippets.

Note: If you find a Closed issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.

Suggesting Enhancements

  • Use a clear and descriptive title for the issue to identify the suggestion.
  • Provide a step-by-step description of the suggested enhancement in as many details as possible.
  • Explain why this enhancement would be useful to most OpenBeta users.

This guide was adapted from project Atom's

OpenBeta is a volunteer effort. We encourage you to pitch in and join the team!

Thanks! ❤️ ❤️ ❤️

OpenBeta Team