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
pauloxnet
reviewed
Apr 9, 2026
jefftriplett
approved these changes
Apr 9, 2026
Member
jefftriplett
left a comment
jefftriplett
left a comment
There was a problem hiding this comment.
This was reviewed by the Django Software Foundation board today and approved during our meeting. Great work and congratulations.
@pauloxnet has some really good feedback to follow up on regarding ensuring events have multiple organizer contact details.
- Add In-Person Event Requirements section to events.md covering personal space, appropriate items (per local/cultural norms), photography/recording, and event-specific policy extensions - Require sponsored events to designate named CoC point(s) of contact with practical on-site reporting guidance - Add reference to Event Organizer Support Guide in CODE_OF_CONDUCT.md - Require affiliated programs to designate a named CoC point of contact and provide their individual email address to the working group on file - Add Affiliated Programs Register to working group manual (shared Google Drive spreadsheet tracking programs and CoC contacts) - Update working group manual scope summaries for events and affiliated programs to reflect new contact requirements
|
En 14 de abril de 2026 12:53:26 GMT-05:00, Dan Ryan ***@***.***> escribió:
…
@dryan commented on this pull request.
> +
+We recognize that violations can have disproportionate impact. Behaviors that may seem minor to some community members can have a significantly greater impact on those from marginalized or underrepresented groups who face these patterns repeatedly. We take this into account when addressing incidents.
+
+The enforcement ladder includes the following levels:
+
+1. **Warning** - A private, written warning from the Code of Conduct Working Group.
+2. **Temporary Suspension (Short-term)** - A temporary suspension from Django community spaces for a defined period (typically 30-90 days).
+3. **Temporary Suspension (Extended)** - An extended temporary suspension for a longer defined period (typically 90 days or more) with specific conditions for return.
+4. **Permanent Ban** - Permanent removal from all Django community spaces, tools, and communication channels.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of the Code of Conduct Working Group to use their discretion and judgment, in keeping with the best interests of our community.
+
+For complete details about our enforcement process, please see our [Enforcement Guide](https://github.com/django/code-of-conduct/blob/main/enforcement-ladder.md).
+
+## Scope
+
Per a conversation @pauloxnet and I had on Slack we will go forward with this as-is and if he has more feedback later we'll do another PR.
--
Reply to this email directly or view it on GitHub:
#97 (comment)
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
dryan
added a commit
to dryan/djangoproject.com
that referenced
this pull request
Apr 15, 2026
Updates the djangoproject.com Code of Conduct page to reflect the current version maintained at django/code-of-conduct. Refs django/code-of-conduct#97 Closes django/code-of-conduct#83
This was referenced Apr 15, 2026
SaptakS
pushed a commit
to django/djangoproject.com
that referenced
this pull request
Apr 22, 2026
Updates the djangoproject.com Code of Conduct page to reflect the current version maintained at django/code-of-conduct. Refs django/code-of-conduct#97 Closes django/code-of-conduct#83
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
5 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