Skip to content

Commit 12f3acc

Browse files
committed
Document expedited DEP process out of the feature review process.
1 parent 53968e6 commit 12f3acc

File tree

1 file changed

+38
-3
lines changed

1 file changed

+38
-3
lines changed

README.md

Lines changed: 38 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,6 @@
44

55
- Write up instructions for SC / Feature Review team for each phase
66
- Generate URLs for various queues for people to bookmark
7-
- Write up instructions for an expedited DEP process
87

98
## Have an idea for Django?
109

@@ -124,7 +123,7 @@ This is to the Steering Council's discretion.
124123

125124
The phase after it's agreed upon that the feature belongs in Django is
126125
determining whether the feature can be implemented. Advancing beyond this
127-
phase requires a [DEP](https://github.com/django/deps/) to be created.
126+
phase requires a [DEP](#expedited-dep-process) to be created.
128127
The [Steering Council](https://docs.djangoproject.com/en/dev/internals/organization/#steering-council) or a community
129128
member can create the first draft. It should contain everything but the
130129
technical details of implementation (unless those are known already).
@@ -159,9 +158,45 @@ ecosystem.
159158

160159
It's possible that a feature can't be a third-party package due to the nature
161160
of the feature or limitations of Django. In this case, the DEP process should
162-
be followed. This [DEP](https://github.com/django/deps/) must be written by
161+
be followed. This [DEP](#expedited-dep-process) must be written by
163162
a community member rather than the [Steering Council](https://docs.djangoproject.com/en/dev/internals/organization/#steering-council).
164163

164+
165+
## Expedited DEP process
166+
167+
This new feature process has overlap with the existing [DEP process](https://github.com/django/deps/).
168+
This allows us to expedite the DEP process depending on the size of the feature
169+
according to the table below. It's still important to use DEPs to identify
170+
the rationale, motivation and considerations of features. We're all shepherds
171+
of Django, and we owe it to future maintainers to explain why we choose to add things.
172+
173+
| Feature Size | Days to Weeks | Months | Quarters |
174+
|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
175+
| [Pre-posal](https://github.com/django/deps/blob/main/final/0001-dep-process.rst#pre-proposal) | Completed in [Is there community support](#is-there-community-support) | Completed in [Is there community support](#is-there-community-support) | Completed in [Is there community support](#is-there-community-support) |
176+
| [Forming the team](https://github.com/django/deps/blob/main/final/0001-dep-process.rst#forming-the-team) | Author: Steering Council.<br/>Implementation team: Feature proposer or community member<br/>Shepherd: N/A | Author: Steering Council.<br/>Implementation team: Feature proposer or community member<br/>Shepherd: Community member, Fellow, Steering Council member | Author: Steering Council.<br/>Implementation team: Feature proposer or community member<br/>Shepherd: Community member, Fellow, Steering Council member |
177+
| [Submitting the draft](https://github.com/django/deps/blob/main/final/0001-dep-process.rst#submitting-the-draft) | No forum discussion, just create draft Pull Request | No forum discussion, just create draft Pull Request | Follow DEP process |
178+
| [Discussion, development, and updates](https://github.com/django/deps/blob/main/final/0001-dep-process.rst#discussion-development-and-updates) | N/A unless the Steering Council pushes it back | N/A unless the Steering Council pushes it back | Follow DEP process |
179+
| [Review & Resolution](https://github.com/django/deps/blob/main/final/0001-dep-process.rst#review-resolution) | Follow DEP process | Follow DEP process | Follow DEP process |
180+
| [Implementation](https://github.com/django/deps/blob/main/final/0001-dep-process.rst#implementation) | Follow DEP process | Follow DEP process | Follow DEP process |
181+
182+
The Steering Council can draft DEPs on behalf of the community because when an idea passes
183+
through [Is this expected in Django?](#is-this-expected-in-django), the following sections
184+
will have been discussed and determined:
185+
186+
- Title
187+
- Preamble
188+
- Abstract
189+
- Motivation
190+
- Rationale
191+
- Copyright
192+
193+
The remaining three sections will need to be written by a community member,
194+
likely the person or group of people who will be implementing the feature.
195+
196+
- Specification
197+
- Backwards Compatibility
198+
- Reference Implementation
199+
165200
## Do you have feedback about the process?
166201

167202
Please share your opinions on the [Forum](https://forum.djangoproject.com/c/internals/5).

0 commit comments

Comments
 (0)