Feature #11750

Track the distribution of the shares of the revocation certificate

Added by sajolida 2016-08-30 03:27:21 . Updated 2017-03-10 07:16:08 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_2.12
Start date:
2016-08-30
Due date:
% Done:

80%

Feature Branch:
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

Related issues

Blocked by Tails - Bug #10202: Have a mailing list for the revocation certificate mechanism Resolved 2015-09-16
Blocked by Tails - Feature #11751: Publish the public part of our distribution mechanism Resolved 2016-08-30

History

#1 Updated by sajolida 2016-08-30 03:28:03

  • blocked by #11748 added

#2 Updated by sajolida 2016-08-30 03:28:23

  • blocked by Bug #10202: Have a mailing list for the revocation certificate mechanism added

#3 Updated by intrigeri 2016-08-30 06:04:38

  • Status changed from New to Confirmed

#4 Updated by intrigeri 2016-09-12 13:25:08

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • Group A: done
  • Group B: last blocker removed, so I can do it as soon as the mailing list is up.
  • Group C: on sajolida’s plate IIRC
  • Group D: I’m in touch with the last 2 blockers, and tracking that on my side.

#5 Updated by intrigeri 2016-10-01 01:59:07

Another blocker to send shares is that the draft email refers to https://tails.boum.org/$something. It seems that some part of Bug #11380 has not been completed. So I’ll hold on before sending their share to groups B and D.

#6 Updated by sajolida 2016-10-02 17:53:49

  • blocked by Feature #11751: Publish the public part of our distribution mechanism added

#7 Updated by sajolida 2016-10-02 17:54:26

Oops! So I’m marking this as blocked by Feature #11751 which is needed to fix this placeholder.

#8 Updated by sajolida 2016-11-08 18:18:10

  • Assignee changed from sajolida to intrigeri

Now that the draft email has been reviewed, I sent a first batch of emails to my contacts. You can go ahead and do the same with yours. I added some checkbox thingie in the internal repo (1846b69) feel free to use that or otherwise tell me.

You can reassign this ticket to me for futher tracking once you think you’re done with your stuff.

#9 Updated by intrigeri 2016-11-08 19:03:59

  • Target version set to Tails_2.9.1

#10 Updated by intrigeri 2016-12-06 20:05:41

  • Target version changed from Tails_2.9.1 to Tails 2.10
  • % Done changed from 10 to 20

Emailed everyone I could.

#11 Updated by intrigeri 2017-01-06 10:26:30

  • Group A: done
  • Group B: done
  • Group C: WIP [sajolida]
  • Group D: WIP, waiting for replies since a month, pinged today [intrigeri]

#12 Updated by intrigeri 2017-01-06 10:26:58

  • % Done changed from 20 to 50

#13 Updated by intrigeri 2017-01-06 10:27:45

  • Target version changed from Tails 2.10 to Tails_2.11

I’ll come back to it during next cycle, and I expect sajolida tracks his part elsewhere.

#14 Updated by sajolida 2017-01-06 20:05:42

I pinged the remaining candidates for group C once. I won’t ping them twice as this mechanism relies on people being reliable on email.

#15 Updated by intrigeri 2017-02-06 12:09:51

  • % Done changed from 50 to 60

Pinged the 3 WIP bits of group D one last time.

#16 Updated by sajolida 2017-02-22 14:26:21

Giving up on the leftovers from group C. Sent a last ping to my contact for group D.

#17 Updated by intrigeri 2017-03-03 09:13:37

  • Assignee changed from intrigeri to sajolida
  • Target version changed from Tails_2.11 to Tails_2.12
  • % Done changed from 60 to 80

Only 2 people left, one is on sajolida’s plate and one on bertagaz’ plate.

#18 Updated by bertagaz 2017-03-03 12:00:55

intrigeri wrote:
> one on bertagaz’ plate.

I’m good now, went to complete the process.

#19 Updated by intrigeri 2017-03-03 12:40:53

> I’m good now, went to complete the process.

\o/

#20 Updated by sajolida 2017-03-10 07:16:08

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)

With bertagaz’s addition we are now settled on the full list that we had originally. Four people got dropped by lack of answer but we know have 23 people on the list and we can close this ticket \o/

I also checked the list in Git against the subscribers to the list and added a couple of people who hasn’t been subscribed yet.