Maniphest T71696

Policy for removing commit access from inactive accounts
Confirmed, LowDESIGN

Assigned To
None
Authored By
Campbell Barton (campbellbarton)
Nov 20 2019, 8:49 AM
Tags
  • BF Blender
Subscribers
Bastien Montagne (mont29)
Brendon Murphy (meta-androcto)
Campbell Barton (campbellbarton)
Sergey Sharybin (sergey)

Description

Policy for removing inactive developers.

Currently inactive developers tend to keep commit access, while this hasn't been an issue so far, developers move on and if they haven't committed in a very long time, we could periodically remove them.

Since there is some security issues (if their account becomes compromised for example).

This can apply to:

  • Blender's git repository.
  • Blender's git add-on repository.
  • Blender's svn documentation repository.

Others repositories could be included, this is just an initial list.


Proposal:

  • Periodic list developers which haven't committed anything for a long time (suggest 2-3 years, could be done each release).
  • Mail the bf-committers mailing list with a list of these developers, allowing them to request they keep commit access (suggest one month).

This way we're not over-eager in removing developers, and anyone who intends to contribute can request their access be kept.

Related Objects

Event Timeline

Campbell Barton (campbellbarton) triaged this task as Low priority.Nov 20 2019, 8:49 AM
Campbell Barton (campbellbarton) created this task.
Campbell Barton (campbellbarton) mentioned this in T71640: Development Policies.Nov 20 2019, 9:04 AM
Campbell Barton (campbellbarton) updated the task description.
Brendon Murphy (meta-androcto) added a subscriber: Brendon Murphy (meta-androcto).Nov 20 2019, 11:34 AM

hi, I would like to mention that we could do this for the addons project members with inactive accounts too.
Thanks.

Campbell Barton (campbellbarton) updated the task description.Nov 22 2019, 1:30 AM

@Brendon Murphy (meta-androcto) agree, updated.

Campbell Barton (campbellbarton) updated the task description.Nov 22 2019, 1:35 AM
Campbell Barton (campbellbarton) updated the task description.
Sergey Sharybin (sergey) added a subscriber: Sergey Sharybin (sergey).Feb 11 2021, 6:49 PM

I would say it should be applied for all repositories we host. But otherwise +1

Campbell Barton (campbellbarton) added a comment.Feb 16 2021, 12:35 PM

Fine to apply to all repositories too, if that's not controversial.

Bastien Montagne (mont29) added a subscriber: Bastien Montagne (mont29).Feb 17 2021, 11:40 AM

Sounds fine to me as well (would rather send the warning on bf-committer in advance, before removal).