-
Notifications
You must be signed in to change notification settings - Fork 8
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
Initial write-up for member audit #100
Draft
RRosio
wants to merge
4
commits into
jupyter:main
Choose a base branch
from
RRosio:member_audit
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# Jupyter Organization Member Auditing | ||
|
||
This document proposes a new security policy concerning member activity within our GitHub organizations. | ||
The Jupyter Security Council aims to routinely review the activity levels of members across our GitHub organizations. | ||
Members who have not engaged in any activity for a specific period will have their privileges adjusted or may be removed from the organization. This process aims to to enhance security by ensuring that only active contributors retain access. GitHub privileges do not indicate membership or status within the Jupyter project, this policy aims to support the Jupyter project's overall security efforts. | ||
|
||
## Scope | ||
|
||
This process applies to *all projects* governed by Jupyter (including those under other organizations) such as: JupyterLab, Jupyter Notebook, Jupyter Server and JupyterHub. | ||
|
||
## Defining Inactivity | ||
|
||
A member is considered inactive if they have not performed any *public* [GitHub events](https://docs.github.com/en/rest/activity/events?apiVersion=2022-11-28#list-public-events-for-a-user) within the last [365] days. Some examples of those public activities include: | ||
|
||
- Commits to public repositories | ||
- Pull requests to public repositoryies | ||
- Participating in issues or pull requests | ||
- Applying or managing labels on issues or pull requests | ||
|
||
## Communication and Feedback | ||
|
||
We understand that contributors may have varying levels of engagement due to numerous factors. Our goal is to implement this policy without disrupting workflows or discouraging contributions. | ||
We will reach out to maintainers and members identified as inactive to discuss their status before making any changes. This ensures that we only adjust privileges for those who have truly been inactive. | ||
We invite all maintainers, contributors and users to [share your thoughts or concerns](https://jupyter.org/security#community-reshttps://github.com/jupyter/security/issues/99) regarding this policy. Your feedback is valuable as we refine our approach to best support the Jupyter community. | ||
|
||
## Reinstatement of Access | ||
|
||
If a member's privileges are adjusted due to inactivity, they can be reinstated upon request. Our goal is to maintain security without hindering future contributions. | ||
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.
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.
As a reader, it's unclear how I should reach out to the Security Council to reinstate my access privileges. We should probably suggest a way to contact us here, for example:
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.
Should this be handled via the subproject instead of the central security email?
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.
Yes! This isn't about a security vulnerability so having it go to the mailing list is better--and more likely to be seen.
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.
Perhaps! This ambiguity is exactly why I think we should document it here first. 😁