-
Notifications
You must be signed in to change notification settings - Fork 23
Contributor guidelines
Wiki ▸ Documentation ▸ Contributor guidelines
First off, we're excited you're here! Buoy is a very ambitious project. To succeed, it needs a lot more than just computer code (although that's useful, too). Below, you'll find links to information about how we work on Buoy itself. This includes everything from lists of the free and open source software we use, conventions we use to name files or folders, even tips and tricks.
There’s always a lot of work for everyone to do. We especially love collaborating with folks who want to try out and improve new skills by working on a real world project they care about. We welcome and encourage people of all skill levels to participate.
- Have questions? See if it's answered in the FAQ!
- Found a bug? Read our helpful bug submission guidelines first.
- Have a feature request? Read our helpful feature request guidelines first.
</tr>
Writer | Translator | QA Tester | Artist | Event planner | Programmer |
---|---|---|---|---|---|
Write articles about Buoy or improve its documentation. | Translate Buoy's interface, help pages, and other text from one language to another. | Test pre-release versions of the software to find bugs or other problems. | Design beautiful icons and images for Buoy's interface, website, or wiki. | Host events in my community to help people install, improve, and use Buoy. | Code new features and fix bugs. |
TK-TODO | TK-TODO | TK-TODO | TK-TODO | TK-TODO | TK-TODO |
Questions? Double-check the Frequently Asked Questions. Otherwise, if you want help from other users, try the Buoy Support Forum. To contact the developers, open a new issue.