Thanks for checking out Bananas Screen Sharing! We're excited to hear and learn from you.
We've put together the following guidelines to help you figure out where you can best be helpful.
- Types of contributions we're looking for
- Ground rules & expectations
- How to contribute
- Style guide
- Documentation
- Code
- Setting up your environment
- Community
There are many ways you can directly contribute to Bananas Screen Sharing:
- Feature requests
- Bug reports
- Code contributions
- Writing or editing documentation
Before we get started, here are a few things we expect from you (and that you should expect from others):
- Be kind and thoughtful in your conversations around this project. We all come from different backgrounds and projects, which means we likely have different perspectives on "how open source is done." Try to listen to others rather than convince them that your way is correct.
- Bananas is released with a Contributor Code of Conduct. By participating in this project, you agree to abide by its terms.
- Please ensure that your contribution passes all tests if you open a pull request. If there are test failures, you will need to address them before we can merge your contribution.
- When adding content, please consider if it is widely valuable. Please don't add references or links to things you or your employer have created, as others will do so if they appreciate it.
If you'd like to contribute, start by searching through the pull requests to see whether someone else has raised a similar idea or question.
If you don't see your idea listed, and you think it fits into the goals of this guide, open a pull request.
If you're writing documentation, see the style guide (which uses vale) to help your prose match the rest of the documentation.
When writing code, please follow these configurations:
Most of them are automatically checked by the CI, so you don't need to worry about them.
Discussions about the Bananas take place on:
- This repository's Issues and Pull Requests sections
- The Bananas Discord server
Anybody is welcome to join these conversations.
Wherever possible, do not take these conversations to private channels, including contacting the maintainers directly.
Keeping communication public means everybody can benefit and learn from the conversation.