This repository has been archived by the owner on Feb 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 23
Submitting a feature request
Meitar M edited this page Aug 20, 2016
·
2 revisions
Wiki ▸ Submitting a feature request
So you have a really cool idea for Buoy? That's great! Now, before you submit a new issue ticket in our issue tracker, please read the following guidelines. (Found a bug? Refer to our bug reporting guidelines, instead.)
-
Search before you post! (No duplicates, please.)
Please use the search function to search for similar issues. If you find something that resembles your request, comment on that ticket and discuss your implementation of the idea there. This keeps our issue tracker organized and helps us implement the feature quicker. -
One feature request per ticket! (No multiple requests in a single ticket!)
Please create separate issue tickets for separate requests. Combining different features into one ticket forces our volunteers to do unnecessary work to understand and re-categorize your request, which slows us down and ensures your idea won't get implemented as quickly as it could be. -
Don't add tags in the issue title! (No plaintext metadata in titles!)
Please do not try to add tags like "[Feature]" or "Enhancement:" in your issue ticket's title. We read each and every single ticket and label them ourselves accordingly. Use the ticket title to describe what your ticket is about in as few words as you can. By being succinct and clear, you can help us triage your issue to the appropriate queue as quickly as possible.
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.