https://github.com/processwire/processwire-requests
ProcessWire feature requests.
https://github.com/processwire/processwire-requests
Last synced: 2 months ago
JSON representation
ProcessWire feature requests.
- Host: GitHub
- URL: https://github.com/processwire/processwire-requests
- Owner: processwire
- Created: 2016-09-22T13:49:03.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2016-10-02T09:37:51.000Z (over 9 years ago)
- Last Synced: 2024-04-14T18:21:51.671Z (almost 2 years ago)
- Size: 8.79 KB
- Stars: 39
- Watchers: 21
- Forks: 0
- Open Issues: 362
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Feature Requests
Thank you for your interest in submitting a feature request to ProcessWire. We manage these
feature requests in this separate repository so that they don't get mixed up with issue
reports. It also enables us to maintain a collaborative team to help manage them.
- Please note that we generally avoid adding features that aren't going to be used by at least
30% of the ProcessWire audience. Often new features can be better accommodated with modules.
- If we close your feature request, this does not mean it won't ever be implemented. It just means
that we aren't ready to implement it just yet. Closed feature requests aren't ever deleted, so
consider closed feature requests to just be on the back burner.
- Sometimes we will leave a feature request open for awhile to see how much interest it gains from
others before we decide whether it should be implemented.
- Comments consisting solely of the string "+1" will be removed to keep the thread of the feature request tidy. Please use [GitHub’s built-in comment emojis](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments) to express a reaction/feeling.
- See also the [Wishlist & Roadmap board](https://processwire.com/talk/forum/5-wishlist-roadmap/).