-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update DEP 7 terminology to match current landscape #91
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks right. Thanks @thibaudcolas
👋 I’m not sure if this needs further review, or someone with appropriate permissions to merge? |
@django/steering-council - any feedback? If not, I say yeah let's merge in about a week. |
I’ve also opened #95 as a follow-up with even more terminology updates. The only one I’ve left out for now is DEP 10. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small comment, otherwise LGTM
Co-authored-by: Adam Johnson <[email protected]>
Looks like this is now ready to merge if anyone with write access is around? |
Perhaps this should wait until after the SC election so they can properly vote on whether to accept the changes? |
@ubernostrum I was under the impression the changes here would fall in the "housekeeping" bucket and wouldn’t require a vote, per past advice on similar changes (Updates to DEPs 1, 10, and 12 to reflect current governance). |
This is a follow-up to @jacobian’s #81, updating DEP 7 so its terminology matches current operations.
As of today I believe the relevant projects are:
This policy also came up as part of Django ticket #33620 Accessibility in pipeline.