Revoke repository write access for inactive accounts #55
Labels
No Label
Service
Buildbot
Service
Chat
Service
Gitea
Service
Translate
Type
Bug
Type
Config
Type
Deployment
Type
Feature
Type
Setup
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-projects-platform#55
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For security reasons, inactive developer accounts should no longer have write access to repositories as those accounts are more likely to get compromised.
There are also many summer of code accounts where the intent was never to give write access to main. Going forward these students only need to work in a forked repository, and can be given commit access when their code lands and they are available to maintain it going forward.
Proposed policy: remove accounts inactive for 2 years. Anyone that previously had commit access can ask for it back without having to go through approval of Blender admins.
We could have a team that has no addition permission and move those developers there.
Sugestion: "All-time Developers".
This was all done.