Bug #16635

Give commit access to FT members who satisfy the relevant security policy

Added by intrigeri 2019-04-05 14:41:46 . Updated 2019-08-22 12:24:36 .

Status:
Resolved
Priority:
Normal
Assignee:
intrigeri
Category:
Infrastructure
Target version:
Tails_3.16
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

It’s painful that some FT members can review branches but are not allowed to merge them. Likely most FT members who currently have no commit rights satisfy the relevant security policy and could be trusted with such rights. Let’s request them!

Subtasks

Related issues

Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by intrigeri 2019-04-05 14:42:12

#2 Updated by intrigeri 2019-04-05 14:43:50

  • Assignee set to intrigeri
  • Target version set to Tails_3.14
  • Private changed from Yes to No

During this cycle I’ll ask the affected developers to check if they comply with the relevant security policy.

#3 Updated by intrigeri 2019-04-16 13:00:30

  • Status changed from Confirmed to In Progress

Requested preliminary agreement from tails@, ignoring security policy matters for now.

> I’ll ask the affected developers to check if they comply with the relevant security policy.

I’ll do that once 1. tails@ agrees in principle; 2. we clarify/fix said security policy.

#4 Updated by intrigeri 2019-05-14 15:07:21

intrigeri wrote:
> Requested preliminary agreement from tails, ignoring security policy matters for now. > > > I'll ask the affected developers to check if they comply with the relevant security policy. > > I'll do that once 1. tails agrees in principle;

Almost a month has passed since my request so I consider tails@ has agreed in principle.

> 2. we clarify/fix said security policy.

I’ll dive into this now.

#5 Updated by intrigeri 2019-05-14 17:40:32

  • Target version changed from Tails_3.14 to Tails_3.15

Sent a proposal to tails@.

#6 Updated by intrigeri 2019-06-02 16:08:41

intrigeri wrote:
> Sent a proposal to tails@.

… and set a deadline on June 14.

#7 Updated by intrigeri 2019-06-08 16:45:18

Updated proposal, new deadline is June 22.

#8 Updated by intrigeri 2019-07-01 07:31:05

Security policy was clarified. Next step: check if/how the 2 fine people we want to give commit access to comply with said policy.

#9 Updated by intrigeri 2019-07-01 07:49:57

intrigeri wrote:
> Next step: check if/how the 2 fine people we want to give commit access to comply with said policy.

Send them the policy & proposed we go through it together on XMPP, to avoid lengthy round-trips over email (we had bad past experience about such matters).

#10 Updated by intrigeri 2019-07-01 07:50:40

  • Target version changed from Tails_3.15 to Tails_3.16

(I doubt this will be completed by July 9.)

#11 Updated by intrigeri 2019-08-06 12:46:38

  • Target version changed from Tails_3.16 to Tails_3.17

One of the two fine people declined (would need to reinstall laptop top satisfy the security policy) and the other is mostly away from Tails in August ⇒ I’ll come back to it in September.

#12 Updated by intrigeri 2019-08-22 12:21:44

  • Status changed from In Progress to Resolved

Done, we have one more committer! :)

#13 Updated by intrigeri 2019-08-22 12:24:36

  • Target version changed from Tails_3.17 to Tails_3.16