Tails

#1 Updated by intrigeri 2014-06-03 08:04:09

• related to Feature #5542: Help MAT upstream to write documentation added

#3 Updated by BitingBird 2014-06-04 06:43:56

• Status changed from New to Confirmed

I confirm it, since sajolida’s command doesn’t work

#4 Updated by sajolida 2014-06-05 01:33:40

• Status changed from Confirmed to New

#5 Updated by sajolida 2014-06-05 01:34:15

• Status changed from New to Confirmed

#6 Updated by BitingBird 2014-12-03 17:32:42

• Status changed from Confirmed to In Progress
• QA Check set to Ready for QA

#7 Updated by BitingBird 2014-12-03 18:13:26

• Assignee set to sajolida
• Target version set to Tails_1.2.2
• Feature Branch set to bitingbird:doc/7368-warning_metadata

#8 Updated by sajolida 2014-12-11 14:15:21

• related to deleted (Feature #5542: Help MAT upstream to write documentation )

#9 Updated by sajolida 2014-12-11 14:15:29

• Assignee changed from sajolida to BitingBird
• Parent task set to Feature #5542
• QA Check changed from Ready for QA to Info Needed

Thanks for the patch. This made me realize that many other things can be fixed regarding MAT in our documentation, so I made this a subtask of Feature #8416.

Do you think that should merge this as such or rather work a bit of the other subtasks of Feature #8416 before?

#10 Updated by sajolida 2014-12-11 14:17:05

• Parent task deleted (Feature #5542)

#11 Updated by sajolida 2014-12-11 14:17:12

• Parent task set to Feature #8416

#13 Updated by sajolida 2014-12-11 16:50:22

• Feature Branch changed from bitingbird:doc/7368-warning_metadata to doc/7368-warning_metadata

#14 Updated by anonym 2014-12-12 16:41:59

• Target version changed from Tails_1.2.2 to Tails_1.2.3

#15 Updated by BitingBird 2015-01-08 05:35:36

• Target version changed from Tails_1.2.3 to Tails_1.3

#16 Updated by BitingBird 2015-01-15 04:32:34

• Assignee changed from BitingBird to sajolida
• QA Check changed from Info Needed to Ready for QA
• Feature Branch changed from doc/7368-warning_metadata to bitingbird:doc/7368-warning_metadata

I think this can be merged already, I don’t really know where to start to document MAT and the warning is useful as-is, although more complete documentation would be better :)

#17 Updated by intrigeri 2015-01-16 17:14:16

• Feature Branch changed from bitingbird:doc/7368-warning_metadata to doc/7368-warning_metadata

Rebased on master.

#19 Updated by intrigeri 2015-02-07 14:01:28

• % Done changed from 0 to 50

Cherry-picked your commit, added two more on top, pushed.

#20 Updated by BitingBird 2015-02-08 14:12:00

• Priority changed from Normal to Elevated

The review has already half been done, I think it’s quick.

#21 Updated by sajolida 2015-02-09 15:29:20

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

Ok, to include this inline right now, and not wait for the MAT documentation. Still, I have a few concerns with your doc:

• Did you build the wiki? Because all the links are broken for me :)
• The Wikipedia page is quite rough. I try to be cautious about the relevance of our external links and the intro of this page is quite obscure don’t you think? The MAT website has a short introduction which is quite better actually. Or maybe we can find something somewhere else? Probably Tactical Tech has some explanation about metadata somewhere… Could check this out?
• Can you try to avoid hyphen or dashes to structure sentences? I’m sure this one could have a simpler structure either broken in two or restructured to merge its two parts.
• Did you have a good reason to not add a .mdwn extension to your file?
• I usually use a naming scheme in three parts for file dedicated to inlined sections, to make them easier to identify when I browse through the file system. See for example ./first_steps/persistence.caution.mdwn. Shall we do that here as well?

#22 Updated by BitingBird 2015-02-10 14:20:46

• Target version changed from Tails_1.3 to Tails_1.3.2

#23 Updated by BitingBird 2015-03-03 13:11:12

• Assignee changed from BitingBird to sajolida
• QA Check changed from Dev Needed to Info Needed
• Feature Branch changed from doc/7368-warning_metadata to bitingbird:doc/7368-warning_metadata

sajolida wrote:
> Ok, to include this inline right now, and not wait for the MAT documentation. Still, I have a few concerns with your doc:
>
> * Did you build the wiki? Because all the links are broken for me :)

I didn’t, sorry. Done now :)

> * The Wikipedia page is quite rough. I try to be cautious about the relevance of our external links and the intro of this page is quite obscure don’t you think? The MAT website has a short introduction which is quite better actually. Or maybe we can find something somewhere else? Probably Tactical Tech has some explanation about metadata somewhere… Could check this out?

We already link to MAT in the next line, and tactical tech has a page about metadata cleaning, but it doesn’t mention MAT although it mentions many other tools (I sent them a message to suggest it), so I’m afraid it would be confusing for the users to be sent to a page explaining other tools. Should I remove the link altogether and consider that users will get the metadata explanation from the MAT link? Leave the wikipedia link? Something else?

> * Can you try to avoid hyphen or dashes to structure sentences? I’m sure this one could have a simpler structure either broken in two or restructured to merge its two parts.

I put a :

> * Did you have a good reason to not add a .mdwn extension to your file?

I was confused because the inline doesn’t include the extension, but it’s fixed.

> * I usually use a naming scheme in three parts for file dedicated to inlined sections, to make them easier to identify when I browse through the file system. See for example ./first_steps/persistence.caution.mdwn. Shall we do that here as well?

The persistence.mdwn that is included in the same page is not named in three, but I don’t mind renaming. Would documents.metadata.mdwn be ok?

#24 Updated by sajolida 2015-03-05 14:38:36

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

What about trying to write a very short sentence that explain metadata
in a very simplistic form? I feel weird about using that jargon in the
doc without explaining, even very minimalistically, what this is about.
Then, yes the link to MAT should be enough.

> The persistence.mdwn that is included in the same page is not named
> in three, but I don’t mind renaming.

Hmm, that’s right! Then I guess you can leave metadata.mdwn like this :)

#25 Updated by BitingBird 2015-03-14 16:10:07

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

Added a commit to explain metadata, explanations are stolen from MAT. Please review :)

#26 Updated by sajolida 2015-03-17 10:53:59

• Status changed from In Progress to Resolved
• % Done changed from 50 to 100

Applied in changeset commit:ed01e8ab9e5699772c30a6dbe610691860a346a1.

#27 Updated by sajolida 2015-03-17 10:54:28

• Assignee deleted (sajolida)
• QA Check changed from Ready for QA to Pass
• Feature Branch changed from bitingbird:doc/7368-warning_metadata to doc/7368-warning_metadata

#29 Updated by BitingBird 2015-03-22 12:12:27

• Target version changed from Tails_1.3.2 to Tails_1.3.1