Bug #12118

Gather security policy compliance for 2019

Added by mercedes508 2017-01-07 15:04:29 . Updated 2020-01-25 09:59:19 .

Status:
Rejected
Priority:
Normal
Assignee:
muri
Category:
Target version:
Tails_4.3
Start date:
2017-01-07
Due date:
% Done:

50%

Feature Branch:
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

Related issues

Related to Tails - Bug #10740: Gather security policy compliance for 2016 Resolved 2015-08-14
Blocked by Tails - Bug #12117: Find someone to gather security policy compliance for 2017 Resolved 2017-01-07

History

#1 Updated by intrigeri 2017-01-07 15:20:31

  • related to Bug #10740: Gather security policy compliance for 2016 added

#2 Updated by intrigeri 2017-01-07 15:20:55

#3 Updated by intrigeri 2017-01-07 15:21:12

  • blocked by Bug #12117: Find someone to gather security policy compliance for 2017 added

#4 Updated by mercedes508 2017-02-14 14:27:12

  • Assignee set to mercedes508

#5 Updated by BitingBird 2017-08-28 18:57:11

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 50

#6 Updated by Anonymous 2018-01-15 14:06:28

Ping? Did this work out correctly? If yes, please close this ticket and create a new one for 2018.

#7 Updated by mercedes508 2018-01-20 19:53:49

  • Assignee deleted (mercedes508)

u wrote:
> Ping? Did this work out correctly? If yes, please close this ticket and create a new one for 2018.

Hum no I didn’t hustle people enough (or at least, can’t find any evidence) before 2017 summit so we did nothing about it…

So it’s at the same time outdated and not done. Should we directly switch to the 2018 edition?

Whatever the answer is I’m giving up on this task.

#8 Updated by Anonymous 2018-01-22 16:56:11

  • Subject changed from Gather security policy compliance for 2017 to Gather security policy compliance for 2018
  • Target version changed from 2017 to 2018

It’s 2018. I will repurpose this ticket. And leave it assigned to myself for the time being. Feel free to steal it from me.

#9 Updated by Anonymous 2019-01-21 00:13:08

  • Target version changed from 2018 to 2019

#10 Updated by Anonymous 2019-02-03 16:16:30

  • Subject changed from Gather security policy compliance for 2018 to Gather security policy compliance for 2019

#11 Updated by Anonymous 2019-03-18 15:41:06

  • Assignee deleted ()

This somehow arrived on my plate, but let’s face it: I have no capacity whatsoever to handle this.

#12 Updated by intrigeri 2019-03-18 15:49:43

  • blocked by #16257 added

#13 Updated by sajolida 2019-03-18 15:57:57

It’s good that you are cleaning your plates from things you won’t be able to do but dropping assignee like this on Redmine will most likely lead to this ticket not being solved by anybody this year. But maybe it’s fine…

#14 Updated by Anonymous 2019-03-18 16:08:31

@sajolida: this was supposed to be done in 2017 by mercedes. I repurposed it for 2018 and put it on my plate - while ticket triaging. Now it’s 2019 and nothing was done. I have absolutely no capacities to do this work, I’m already overwhelmed by doing the budget forecast. Feel free to pcik it up, let me know who it could be assigned to or let’s discuss it at our next accounting meeting.

#15 Updated by sajolida 2019-04-29 14:38:43

  • Status changed from In Progress to Confirmed
  • Assignee set to muri
  • Target version changed from 2019 to Tails_3.16

You said “Jul-Aug” and 3.16 is scheduled for early September.

#16 Updated by CyrilBrulebois 2019-09-05 00:05:30

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

#17 Updated by intrigeri 2019-09-12 14:25:13

  • Target version changed from Tails_3.17 to Tails_4.0

#18 Updated by intrigeri 2019-10-21 11:46:09

  • Target version changed from Tails_4.0 to Tails_4.1

#19 Updated by CyrilBrulebois 2019-12-04 11:31:15

  • Target version changed from Tails_4.1 to Tails_4.2

#21 Updated by CyrilBrulebois 2020-01-07 18:00:38

  • Target version changed from Tails_4.2 to Tails_4.3

#22 Updated by intrigeri 2020-01-25 09:59:19

  • Status changed from Confirmed to Rejected

This ticket was initially about 2017, then 2018, then 2019, and we’re now in 2020, without a clear plan for the next steps, and with doubts wrt. whether the process we’re supposed to follow in theory makes much sense ⇒ muri and I agree that at the summit, we take a big step back and reconsider the whole security policy thing — and in particular, how we check compliance.