-
Notifications
You must be signed in to change notification settings - Fork 6
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
Reduce filecoin-project org ownership #47
Comments
While this captures my current thinking, I don't expect to take any action until this repo is made public per #45 |
Also started documented why the current set of members are there. This is being done now because there have been various permissions/access issues of late as part of cleaning up repos that FilOz owns/maintainers (e.g., improving CI, updating dependencies, adding dependabot). This set of members will also get reviewed and improved as part of #47
* Add rvagg as a member to "githut-mgmt stewards" Also started documented why the current set of members are there. This is being done now because there have been various permissions/access issues of late as part of cleaning up repos that FilOz owns/maintainers (e.g., improving CI, updating dependencies, adding dependabot). This set of members will also get reviewed and improved as part of #47 * Moved galargh and jennijuju to be maintainers given org ownership * fix@10256317436 [skip fix] --------- Co-authored-by: filecoin-project-mgmt-read-write[bot] <124318806+filecoin-project-mgmt-read-write[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
I'm supportive of reducing org owners and also project admins - especially folks not actively involved in the day-to-day project today. I'd propose moving these folks from "admin" to "member" Would also propose moving these folks to security mgr + moderator Also, who is dr-bizz and do they need to be an admin? cc @smagdali @jennijuju for feedback. |
Temporary org ownership is needed to complete #47 It enables me to 1. Access the (audit log)[https://docs.github.com/en/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization] so I can be sure I'm not advocating for removing owner ownership of someone who has been very active on administering the org 2. Give the "github-mgmt Stewards" team [moderator](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-moderators) and [security manager](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#security-managers) roles. Access here will be revoked as part of completing #47, which should happen no later than the week of 2024-09-02.
@momack2 and @smagdali : thanks for the feedback. I put my proposal for reducing org ownership here: #61 I had just been planning to give "moderator" and "security manager" roles to the "github-mgmt Stewards" team, but I think it makes sense to have dedicated teams for each of these and for now to have moderators include Sead folks and security managers include FF security folks. I'll make that change now. |
Temporary org ownership is needed to complete #47 It enables me to 1. Access the (audit log)[https://docs.github.com/en/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization] so I can be sure I'm not advocating for removing owner ownership of someone who has been very active on administering the org 2. Give the "github-mgmt Stewards" team [moderator](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-moderators) and [security manager](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#security-managers) roles. Access here will be revoked as part of completing #47, which should happen no later than the week of 2024-09-02.
For closing out this issue, I need to get 2 required approvals going per #65 . I'm going to wait a bit on this to see how much this is needed in practice and to allow me to tackle some other loose ends. |
Done Criteria
Why Important
This is the lowest-hanging fruit to protect the filecoin-project org around overly generous permissions. We're obviously not seeking to restrict access to code itself, and this isn't about checking some box for "good OpSec". Some reasons we care about the OpSec here include:
Communication Channels
This issue and the connected PRs are intended to be the main communication channels.
Background
The filecoin-project org has accumulated a lot of permissions over the years. This was somewhat acceptable/mitigated in the past by Protocol Labs Inc being a single company. As Protocol Labs Inc moves to an innovation network of companies (related blog) and projects like Filecoin having more and more independent teams, we're overdue on cleaning up permissions and reevaluating past assumptions.
Notes
Tasks
The text was updated successfully, but these errors were encountered: