Tails

#1 Updated by Anonymous 2016-09-03 04:43:25

• Assignee set to intrigeri
• QA Check set to Info Needed

Intrigeri, you said that you already started to gather these docs, could you please point me to them? Then reassign this ticket to me please. Thanks.

#2 Updated by intrigeri 2016-09-23 02:25:15

• Assignee deleted (intrigeri)

> Intrigeri, you said that you already started to gather these docs, could you please point me to them?

Sure! Now, these documents are in the accounting Git repo (that’s basically the content of the processes directory there), so I don’t know how we shall proceed. I could of course send you a copy, but then we’ll end up with two versions evolving separately. Or you could get access to that repo (which you might need for other reasons soonish anyway). Or we could move them to a new, dedicated repo, that all contractors would have (at least read-) access to, and you would have write access to so you could improve these docs and add whatever else is needed. What do you prefer?

#3 Updated by Anonymous 2017-01-11 13:45:57

• Assignee set to intrigeri

intrigeri wrote:
> > Intrigeri, you said that you already started to gather these docs, could you please point me to them?
>
> Sure! Now, these documents are in the accounting Git repo (that’s basically the content of the processes directory there), so I don’t know how we shall proceed. I could of course send you a copy, but then we’ll end up with two versions evolving separately. Or you could get access to that repo (which you might need for other reasons soonish anyway). Or we could move them to a new, dedicated repo, that all contractors would have (at least read-) access to, and you would have write access to so you could improve these docs and add whatever else is needed. What do you prefer?

I very much like the idea of giving contractors read access to these docs and me write access.
Could you ask for this repo (encrypted i guess)? Last time i tried to set up this encrypted repo it did not work for some reason, so i wonder if you could either do it or send me some documentation?

#4 Updated by intrigeri 2017-01-20 16:58:44

• Status changed from Confirmed to In Progress
• Assignee deleted (intrigeri)
• Target version set to Tails_2.11
• % Done changed from 0 to 10
• QA Check deleted (Info Needed)

Sure. Here’s what I did after having a Git repo created (usually one would ask the sysadmins team):

git clone gcrypt::tails@git-tails.immerda.ch:workers-handbook.git
cd workers-handbook
git config gcrypt.publish-participants true
git config gcrypt.participants "LIST OF OPENPGP FINGERPRINTS"
cp ../fundraising/README .
editor README # adjust the line about gcrypt.participants
git add README
git commit -m 'Add setup documentation.'
git push -u origin master

Next step: I should migrate some content from other repositories to this new one. I won’t do that right now, so keeping on my plate and adding a target version.

#5 Updated by intrigeri 2017-01-20 16:59:10

• Assignee set to intrigeri

#8 Updated by intrigeri 2017-01-27 13:50:12

• Assignee deleted (intrigeri)
• % Done changed from 10 to 20

u wrote:
> Great, so please reassign to me once you’ve added some initial content there.

Done!

#13 Updated by anonym 2017-03-09 14:00:30

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

#15 Updated by intrigeri 2017-04-20 07:05:47

• Target version changed from Tails_2.12 to Tails_3.0

#17 Updated by Anonymous 2017-04-26 09:28:37

• Assignee set to sajolida

Reassigning to sajolida in case he still needs to export this git repository.
From now on I can take over the handling of new contractors using the information stored in the repo.

#18 Updated by sajolida 2017-05-22 17:17:52

• Assignee deleted (sajolida)
• QA Check set to Info Needed

I’ve got that repo now. Shall we close this ticket then?

#19 Updated by intrigeri 2017-05-23 06:17:18

• QA Check changed from Info Needed to Dev Needed

> I’ve got that repo now. Shall we close this ticket then?

Having a repo that 3 people know about does not fully address what this ticket is about; see the ticket description for details :)

Now, I don’t understand what u meant with “Reassigning to sajolida in case he still needs to export this git repository”.

#20 Updated by Anonymous 2017-05-31 09:20:29

• Target version deleted (Tails_3.0)
• QA Check deleted (Dev Needed)

intrigeri wrote:
> > I’ve got that repo now. Shall we close this ticket then?
>
> Having a repo that 3 people know about does not fully address what this ticket is about; see the ticket description for details :)

Ack.

> Now, I don’t understand what u meant with “Reassigning to sajolida in case he still needs to export this git repository”.

I simply wanted to know if we all have access, because there were problems previously.

I will keep this ticket open without a target version. I’m currently not aware of new contractors who have not yet received this information.

#22 Updated by Anonymous 2017-05-31 09:58:39

• Assignee set to intrigeri

intrigeri wrote:
> > I’m currently not aware of new contractors who have not yet received this information.
>
> Three data points that might affect your prioritization of this task:

> * In theory, all existing contractors have received this info at least once, but that was spread over multiple messages and over many years; in practice, pretty often (if not “most of the time”), they are unable to find this info when they need it, and then they ask the accounting team that is forced to act as document store’n’retrieve service, which is kinda dull. Making this repo available to all contractors (without waiting for new ones) would fix this.

ack.

> * Very likely, we’ll soon have a new contractor on the sysadmin team.

ack. you might want to send me an email with the address of this contractor, so that I can send him or her relevant information.

> * Now that the repo is ready, I expect that giving access to it to all contractors (I could do that) and sending them an email to let them know about it should be pretty quick. And then we have one less open issue on our plate :) Unless I missed something and we already pointed workers to this repo?

This sounds like a good idea. Reassigning to you then.

Please reassign to me when done and I’ll send an email to all people that are concerned by this. And then we can close the ticket.

#23 Updated by intrigeri 2017-05-31 15:17:35

• Target version set to Tails_3.0

My radar :)

#24 Updated by intrigeri 2017-06-02 15:34:26

• Assignee deleted (intrigeri)
• % Done changed from 20 to 30

#29 Updated by intrigeri 2017-06-12 16:09:26

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

(I’m closing the 3.0 target version.)

#34 Updated by Anonymous 2017-09-04 16:39:02

• Status changed from In Progress to Resolved