Update DEPs terminology to match current landscape #95
+54
−45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tim-schilling
approved these changes
Dec 31, 2024
|
+1 |
LilyFoote
approved these changes
Jan 6, 2025
| unmaintained), we want to identify it early and start looking for backup plans. | ||
| This might mean removing the dependency, taking over maintenance ourselves, | ||
| looking for funding to pay new maintainers, etc. | ||
| core contributors should re-evaluate all existing dependencies. If some |
There was a problem hiding this comment.
I wonder if this should be more specific:
Suggested change
| core contributors should re-evaluate all existing dependencies. If some | |
| Steering Council and Fellows should re-evaluate all existing dependencies. If some |
Otherwise, it's not really clear whose responsibility it is.
But maybe this is straying a bit far from the point of this particular PR...
Comment on lines
-154
to
+155
| Django core team, and a de-facto policy emerged of only requiring the lowest | ||
| common denominator: installation via direct download and ``python setup.py | ||
| Django core contributors, and a de-facto policy emerged of only requiring the | ||
| lowest common denominator: installation via direct download and ``python setup.py |
There was a problem hiding this comment.
Given this is a historical section I think it would be OK not to update the terminology here. That said, that's not a strong opinion.
There was a problem hiding this comment.
I notice we have two DEP 7s:
final/0007-official-projects.rstdraft/0007-dependency-policy.rst
It's probably out of scope of this PR to fix this, but I think the draft DEP 7 should be re-numbered.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #81, and #91, updating the terminology in use to reflect current governance, with the exception of DEP 10.