Bug #14501

Merge help desk internal shared expectations with mission page

Added by mercedes508 2017-08-30 09:30:38 . Updated 2019-08-30 17:22:37 .

Status:
Confirmed
Priority:
Normal
Assignee:
emmapeel
Category:
Target version:
Start date:
2017-08-30
Due date:
% Done:

0%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

We should merge as much as possible our internal shared expectations with the public role mission page. As decided during 2017 summit.


Subtasks


Related issues

Related to Tails - Bug #14458: Update Help Desk mission page Resolved 2017-08-30

History

#1 Updated by intrigeri 2017-10-01 08:37:29

Bug #14458 is ready for QA, which is a strong indicator that this one should not be a subtask of it.

#2 Updated by intrigeri 2017-10-01 08:37:40

  • related to Bug #14458: Update Help Desk mission page added

#3 Updated by Anonymous 2018-01-17 11:34:10

Would you like to set a target version for this ticket so we make sure it does not get forgotten?

#4 Updated by mercedes508 2018-01-19 12:25:37

  • Target version set to Tails_3.6

#5 Updated by bertagaz 2018-03-14 11:32:24

  • Target version changed from Tails_3.6 to Tails_3.7

#6 Updated by bertagaz 2018-05-10 11:09:23

  • Target version changed from Tails_3.7 to Tails_3.8

#7 Updated by intrigeri 2018-06-26 16:27:59

  • Target version changed from Tails_3.8 to Tails_3.9

#8 Updated by emmapeel 2018-06-28 15:20:11

  • Assignee changed from mercedes508 to emmapeel
  • QA Check set to Dev Needed

I take over this one

#9 Updated by intrigeri 2018-09-05 16:26:58

  • Target version changed from Tails_3.9 to Tails_3.10.1

#10 Updated by intrigeri 2018-10-24 17:03:40

  • Target version changed from Tails_3.10.1 to Tails_3.11

#11 Updated by CyrilBrulebois 2018-12-16 14:09:13

  • Target version changed from Tails_3.11 to Tails_3.12

#12 Updated by anonym 2019-01-30 11:59:19

  • Target version changed from Tails_3.12 to Tails_3.13

#13 Updated by CyrilBrulebois 2019-03-20 14:34:07

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

#14 Updated by CyrilBrulebois 2019-05-23 21:23:24

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

#15 Updated by CyrilBrulebois 2019-07-10 10:34:02

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

#16 Updated by intrigeri 2019-08-30 17:22:37

  • Target version deleted (Tails_3.16)

Hi!

We’ve set up an automated process to ask our fellow contributors to update some tickets of theirs, in order to:

  • better reflect your plans;
  • bring down your amount of work-in-progress to a sustainable level;
  • encourage team work and increase the chances that someone finishes the work;
  • avoid a human doing ticket triaging and asking you the same questions on each such ticket.

In particular, this process identifies:

  • Stalled work-in-progress
  • Reviews waiting for a long time

However, in the current state of things, this process is not able to notice those tickets when their Target version has been repeatedly postponed by our Release Managers. Therefore, the ticket triaging team decided on Feature #16545 to remove the Target version whenever in such cases, when it does not feel realistic. This is what I’m doing on this ticket.

You now have a few options, such as:

  • Deassign yourself. That’s fine. If it really matters, someone else, possibly you, may pick it up later. Then, if this ticket is relevant for a Tails team, bring it to their attention; else, forget it and take care of yourself :)
  • If you think you can realistically come back to it and finish the work in the next 6 months, say so on this ticket, for example by setting a suitable “Target version”. This will communicate your plans to the rest of the project and ensure the task pops up on your radar at a suitable time. Of course, you can still realize later that it is not going to work as planned, and revisit today’s choice.

Cheers!