Bug #11795

Document Git repo of ISO archive

Added by sajolida 2016-09-14 09:34:57 . Updated 2018-08-11 10:24:55 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2016-09-14
Due date:
% Done:

10%

Feature Branch:
doc/11795-iso-archive
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

We have a private repo with the archive of ISO images.
It was made private to avoid having to deal with the impact on our
server resources (e.g. bandwidth) and associated costs.

But we can, and do, create accounts for contributors who need access
to that archive: ask tails-sysadmins@boum.org.

Subtasks

Related issues

Related to Tails - Feature #12626: Report back to the reproducible builds community about how we did it Resolved 2017-05-31

History

#1 Updated by sajolida 2016-09-14 09:42:21

  • Assignee changed from sajolida to intrigeri
  • QA Check set to Ready for QA
  • Feature Branch set to doc/11795-iso-archive

intrigeri: Do you mind having a look?

#2 Updated by intrigeri 2016-09-15 01:49:58

> intrigeri: Do you mind having a look?

Will do.

#3 Updated by intrigeri 2016-09-23 02:57:26

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to sajolida
  • % Done changed from 0 to 10
  • QA Check changed from Ready for QA to Dev Needed

I’m a bit confused: git-annex operation on this repo is already documented (ISO_history.mdwn in internal.git) for those who need it. We do not give access to this archive over Git to other contributors, as said in the git-annex section of the sysadmins role page: the kind of access we give is over HTTPS. The rest of my comments assume that you had this in mind, and have a good reason to add this info to contribute/git anyway. If not, then you might want to adjust the title/goal of this ticket and document it differently.

  • IMO this does not belong to the “Puppet modules” section, even though it requires the same SSH config as people with commit access to our Puppet modules need.
  • Merely documenting the git clone operation won’t give the contributor something very useful in the end, since that’s a git-annex repo. See ISO_history.mdwn in internal.git for details. I’ll let you judge what’s worth moving to this new piece of doc (if anything).

#4 Updated by Anonymous 2017-06-30 11:36:34

Are the sigs also saved in the archive?

#5 Updated by Anonymous 2017-06-30 11:37:13

  • related to Feature #12626: Report back to the reproducible builds community about how we did it added

#6 Updated by intrigeri 2017-06-30 11:41:48

> Are the sigs also saved in the archive?

They are.

#7 Updated by sajolida 2018-06-04 12:52:57

  • Target version set to Tails_3.8

#8 Updated by sajolida 2018-06-25 16:18:00

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

#9 Updated by sajolida 2018-08-11 10:24:55

  • Status changed from In Progress to Rejected
  • Assignee deleted (sajolida)
  • Target version deleted (Tails_3.9)
  • QA Check deleted (Dev Needed)

I’ll let other reopen this ticket is they are interested in documenting this.