Tails

#1 Updated by sajolida 2017-05-29 16:55:32

• related to Feature #6349: Have a live Debian sid desktop ISO image available for download added

#2 Updated by sajolida 2017-05-29 17:00:07

• Assignee set to elouann

We’re in a very grey zone concerning who should feel responsible to document. I’m assigning it to the current help desk because:

• I’m already clear overtime on technical writing for this quarter so I want to limit myself to reviews.
• This documentation seems to be more in the field of help desk than general purpose documentation.
• Help desk also have some paid time to do documentation tasks that will make the frontdesk job’s easier in the future and, according to they clocking data, they usually have more margin than I do.
• I will anyway have to work on this to review and correct the language.

So please, dear help desk, share your plans with me before writing anything: propose roughly where this should be mentionned on our website, linked from, etc.

Then I’ll be happy to comment on your plans before you write a draft.

#3 Updated by Anonymous 2017-06-27 12:46:11

• related to Bug #12474: Document troubleshooting tips for more failure scenarios throughout installation assistant added

#5 Updated by mercedes508 2018-01-12 15:46:33

• Assignee changed from elouann to sajolida

Help Desk is not responsible for doc writing anymore, so re-assigning it to sajolida.

Moreover it’s already documented in our git, to point users to these images.

#6 Updated by sajolida 2018-02-16 20:25:49

• Assignee changed from sajolida to intrigeri
• QA Check set to Ready for QA
• Feature Branch set to doc/12613-debian-live-images

intrigieri: What do you meant by “the one we want to point users to in most cases”? In which cases would we want to point to a different image?

Assuming that it’s not worth documenting different images, here is a draft. Please check whether what I’m saying makes sense.

I put it in a dedicated section at the bottom of /doc/first_steps/bug_reporting because:

• It’s more “bug reporting” than “troubleshooting”.
• It’s not realistic to put this forward as a prerequisite for people to report a bug. It’s a 2.5 GB download! Before 6a4621ac43 we were also asking them to go through a list of >1000 Redmine tickets :)

So maybe it’s more like a useful link for Help desk.

But I’m not really convinced either…

#7 Updated by sajolida 2018-02-16 20:26:21

• blocks Feature #14758: Core work 2017Q4 → 2018Q1: Technical writing added

#8 Updated by intrigeri 2018-02-17 07:43:52

• Status changed from Confirmed to In Progress
• Assignee changed from intrigeri to sajolida
• QA Check changed from Ready for QA to Dev Needed
• Type of work changed from Contributors documentation to End-user documentation

sajolida wrote:
> intrigieri: What do you meant by “the one we want to point users to in most cases”?

I mean the ISO image I’m linking to after the text you’re quoting followed by “:” i.e. http://get.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-gnome+nonfree.iso.

> In which cases would we want to point to a different image?

E.g. to try to find out if a problem is GNOME-specific, one might want to point to a non-GNOME image. Or to try to find out if a problem is caused by a buggy proprietary firmware, one might want to point to the free software image.

> Assuming that it’s not worth documenting different images, here is a draft. Please check whether what I’m saying makes sense.

It looks good! I’ve merged it already because it’s clearly better than not having it at all. But I have one concern about how this Debian testing Live image is introduced. There are two major ways to help troubleshoot a Tails bug on Debian:

1. test on current Debian stable, to know if the problem is specific to Tails
2. test on current Debian testing, to know if the problem has been fixed in Debian testing already (ideally we would ask to test a nightly build of feature/buster, so we know if it’s fixed in a Debian testing-based Tails, but it’s broken too often)

Our Help Desk (and myself) asks users to do either one, depending on the case. The way I understand it, your introduction text (“to know if your bug only affects Tails”) suggests the new section is about the first case, while it’s really about the second case. When I’ve opened this ticket, I was assuming we were already documenting the first case so I was suggesting we document the second case too, but I was mistaken: we don’t document the first case anywhere I could find. I think the section added by this branch should/could document both but I don’t know how the text should be structured, you’re the boss!

#9 Updated by sajolida 2018-03-02 20:01:03

• Assignee changed from sajolida to intrigeri
• QA Check changed from Dev Needed to Info Needed

To download images of the current Debian I found that:

https://cdimage.debian.org/cdimage/release/current-live/amd64/iso-hybrid/

But no static link that would keep on working across Debian version. Do you know any?

NB: I’m still not convinced that this is something useful to document in our documentation, I mean outside of people already interacting with Help desk or the Foundation team. So every bit of added complexity or every special cases brings me closer to thinking that if it cannot be simple, it shouldn’t be documented at all…

#11 Updated by intrigeri 2018-03-05 08:15:41

• Assignee changed from intrigeri to sajolida
• QA Check changed from Info Needed to Dev Needed

> To download images of the current Debian I found that:
> https://cdimage.debian.org/cdimage/release/current-live/amd64/iso-hybrid/

FYI that’s the 100% free software one. I believe that in most cases that one will be more useful: https://get.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current-live/amd64/iso-hybrid/

> But no static link that would keep on working across Debian version. Do you know any?

I could not find any stable link to the latest ISO, sorry :/

> NB: I’m still not convinced that this is something useful to document in our documentation, I mean outside of people already interacting with Help desk or the Foundation team. So every bit of added complexity or every special cases brings me closer to thinking that if it cannot be simple, it shouldn’t be documented at all…

Your call.

#13 Updated by sajolida 2018-03-22 18:19:30

• Assignee changed from sajolida to intrigeri
• QA Check changed from Dev Needed to Ready for QA

Sorry for the mess in Git. I tried a bit harder and came up with two more commits that should solve your concerns (and mine).

#14 Updated by intrigeri 2018-03-26 07:29:59

• Status changed from In Progress to Resolved
• Target version set to Tails_3.7

> I tried a bit harder and came up with two more commits that should solve your concerns (and mine).

Great! I’ve fixed a few typos in commit:9b81ca4e302f01157fc89707830049116a8596a7 and merged.

#15 Updated by intrigeri 2018-03-26 07:30:27

• Assignee deleted (intrigeri)
• % Done changed from 0 to 100
• QA Check changed from Ready for QA to Pass