-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add guidelines for a good conference transparency report #13
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.
two small grammar tweaks
docs/python.org/code-of-conduct/Transparency-Report-Guidelines.md
Outdated
Show resolved
Hide resolved
docs/python.org/code-of-conduct/Transparency-Report-Guidelines.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Drew Winstel <drewbrew@users.noreply.github.com>
|
||
Since it's important to be able to recall details of covered issues accurately, a timely report will be of higher quality. | ||
|
||
Releasing an initial transparency report should be part of the closing ceremony. Following up with affected parties might take time after the event. Therefore, a separate complete report can be provided in writing at a later time. It wouldn't take more than a month after the event to close the loop on the final report. |
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.
My brain is tired, but my gut feeling is we should lean harder on recommending and suggesting using "should" and "would."
Releasing an initial transparency report should be part of the closing ceremony.
Something like, "We recommend including an initial transparency report as part of the closing ceremony."
It wouldn't take more than a month after the event to close the loop on the final report.
I struggled with this sentence. It feels like something we should reword, "We recommend closing the loop on final reports within one month after the event when possible." If we are being 100% transparent here, we have seen reports from conferences take as much as a year or more to fully resolve.
Should we recommend sending these reports to our workgroup? |
Not sure if these should be sent over to us if PSF COC WG escalation or the likes are not needed. |
I only suggest this since we track issues. On the off chance it's a pattern, it might otherwise be harder to spot, but I nod along to your point.
This feels like more of a board discussion than our WG's. If the board wants this, we should add it. I don't want us to pile on or give the Grants WG more work because that feels like we are overstepping. |
This was created in person by representatives of the PSF COC WG at the PyCon US '24 sprints: