Open
Conversation
Member
|
It seems an excellent idea to me. I'll try to find the time to review this one. :) |
Added item 7 to the Other Restrictions section to address repeatedly reporting the same or similar incidents after they have been deemed not to be violations, or otherwise submitting reports intended to harass or burden the working group or reported parties.
- Add comprehensive transparency report section to conferences.md - Include guidance on when to release, how to publish, what to include/exclude - Add PSF Transparency Report Guidelines to sources.md - Inspired by Python Software Foundation best practices
- Rename conferences.md to events.md to be more inclusive of all event types - Update all references from conferences.md to events.md across documentation - Update language to use 'event' instead of 'conference' where appropriate - Retain 'Conference Chairs' as it's a specific role title
Co-authored-by: Priya <pahwa.priya19@gmail.com>
Co-authored-by: Priya <pahwa.priya19@gmail.com>
Co-authored-by: Priya <pahwa.priya19@gmail.com>
Co-authored-by: Priya <pahwa.priya19@gmail.com>
Co-authored-by: Priya <pahwa.priya19@gmail.com>
Co-authored-by: Priya <pahwa.priya19@gmail.com>
Co-authored-by: Priya <pahwa.priya19@gmail.com>
Co-authored-by: Priya <pahwa.priya19@gmail.com>
…this makes more sense as guidance for affiliated events so I'll move it there in the process-docs PR
pauloxnet
reviewed
Mar 24, 2026
Member
pauloxnet
left a comment
pauloxnet
left a comment
There was a problem hiding this comment.
Still reviewing but I wanted to add these comments.
Co-authored-by: Paolo Melchiorre <pmelchiorre@rippling.com>
dryan
commented
Mar 24, 2026
Co-authored-by: Paolo Melchiorre <pmelchiorre@rippling.com>
Co-authored-by: Paolo Melchiorre <pmelchiorre@rippling.com>
dryan
added
enhancement
documentation
priyapahwa
approved these changes
Mar 27, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The Code of Conduct Working Group has spent the past year discussing how we might best update our CoC for the first time since its creating in 2014. We were inspired by the BeeWare Project's adoption of Contributor Covenant and recognized it as a strong foundation for Django's needs.
We chose Contributor Covenant 3 because:
We plan to merge this proposal on April 15 pending DSF Board approval.
Closes #82