mirror of
https://github.com/directus/directus.git
synced 2026-04-03 03:00:39 -04:00
5cf2c0d724
* Point to docs hosted C&C
* Point to hosted contributing guidelines
* Remove outdated information
This is incorrect, so does more harm than good imo
* Update contributing guidelines to add feature requests flow
* Lil nicer to read
* Add missing words to dict
* Update docs/contributing/code-of-conduct.md
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Update docs/contributing/introduction.md
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Update docs/contributing/pull-request-process.md
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Update docs/contributing/feature-request-process.md
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
* Update docs/contributing/feature-request-process.md
Co-authored-by: Kevin Lewis <kvn@lws.io>
* Update docs/contributing/pull-request-process.md
Co-authored-by: Kevin Lewis <kvn@lws.io>
* Fix license/version for new packages (#18536)
* Standardize TSConfig use (#18538)
* Use tsconfig.prod.json in packages
* Use prod tsconfig in api
* Install node types in storage
* Use vitest run instead of --watch=false (#18540)
* Remove local file
* Revert "Use vitest run instead of --watch=false (#18540)" (#18542)
This reverts commit 97f0af669e.
* Setup boilerplate for data (#18541)
* Setup boilerplate for data
* Update readme
* Fix directory link
* Final tweaks from Ben
---------
Co-authored-by: Pascal Jufer <pascal-jufer@bluewin.ch>
Co-authored-by: Kevin Lewis <kvn@lws.io>
33 lines
1.9 KiB
Markdown
33 lines
1.9 KiB
Markdown
# Request a Feature
|
|
|
|
If you have a great idea for an improvement of the platform, or any other feedback, please make sure to open a new
|
|
Discussion on [our GitHub Discussions board](https://github.com/directus/directus/discussions).
|
|
|
|
## Opening a New Feature Request
|
|
|
|
New feature requests can be opened under the Feature Requests section of
|
|
[GitHub Discussions](https://github.com/directus/directus/discussions). Feature Requests follow a Request-for-Comment
|
|
(RFC) format that allows anybody to fully understand what you're proposing, and help speed up the review and triaging
|
|
process.
|
|
|
|
**While the form might seem intimidating at first, please do fill out all sections with as much detail as possible. The
|
|
less ambiguity around _how_ a feature should work, the easier it is to review, triage, and develop a feature.**
|
|
|
|
## Review Process
|
|
|
|
Once a feature request gets 15 or more upvotes, it will be moved to the "Under Review" status at which point the
|
|
Directus Core team will review it, and decide if it will be approved, denied, or if changes are required. If the feature
|
|
request is accepted, it will be moved to the "Approved Requests" status, at which point the feature is ready to be
|
|
implemented.
|
|
|
|
However, if a feature request doesn't reach at least 15 upvotes within 3 months of it being created, it will be closed
|
|
due to a lack of community interest.
|
|
|
|
## Implementing Accepted Feature Requests
|
|
|
|
It's important to note that Accepted Feature Requests are _not_ an ordered list of things that will be worked on next.
|
|
Even though we strive to prioritize what's being worked on based on community feedback, it's likely that there will be
|
|
times when a feature request is blocked by something else that's prioritized by the team. The implementation of accepted
|
|
feature request is triaged based on a combination of popularity, team availability, timelines, scope of the feature, and
|
|
overall project goals.
|