| description |
|---|
If you can't contribute directly for any reason, creating thoughtful feature requests is the best way to make Athens better. |
The Athens community uses GitHub's discussions feature to propose, organize around, and track progress around feature requests.
The first step is to search existing discussions to see if your feature has been requested by another member of the Athens community. If it's already there, feel free to add additional context to the existing issue or simply give it an emoji reaction to let the community know that you think it's important.
Click here to create a new feature request.
Enter a descriptive title, then describe the feature you're looking for in the text area, keeping the below tips in mind.
- Make sure you've searched the Athens repository existing feature requests!
- Try to answer the following question: What value does this feature provide to users?
- Describe who will use this feature, as it might not be relevant to everyone.
- Describe the "expected" behavior. What is the user experience around this feature?
- If relevant, include screenshots, videos, or links to similar features in other applications that can help illustrate the feature you're requesting.
Requests are turned into issues on three occasions:
- A member of the Athens development community starts working on the requested feature.
- The Athens core team puts the feature on the roadmap.
- The Athens core team creates a Gitcoin bounty for the issue and lets another member of the community volunteer themselves.
Not every feature request can be worked on right away, either due to lack of resources or because the request isn't defined well enough. In either case, we leave the thread open for further discussion and alignment on how to best implement the requested feature.