Bug #11942

Clean up some rotten bits from our doc

Added by sajolida 2016-11-17 10:47:38 . Updated 2017-05-02 10:03:03 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2016-11-17
Due date:
% Done:

50%

Feature Branch:
doc/11942-rotten-bits
Type of work:
Website
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

While going through the whole documentation for Feature #11916 I spotted and cleanup some rotten bits on our website. These are small unrelated bits so I’m sorry but the subject of this ticket is so generic (but the commits are atomic). I also didn’t want to wait until 3.0, so here is a branch.

Subtasks

Related issues

Blocks Tails - Feature #12432: Technical writing core work 2017Q2 Resolved 2017-04-07

History

#1 Updated by sajolida 2016-11-17 13:24:54

  • Assignee set to spriver
  • Feature Branch set to doc/11942-rotten-bits

spriver: do you mind having a first look and check the changes to the doc. Then please reassign to intrigeri as this removes some very old part of the website that he created initially so I’d like his opinion as well. Then reassign it to me as I need to synchronize with root@boum.org to update our ikiwiki config.

#2 Updated by spriver 2016-11-18 18:47:41

  • Assignee changed from spriver to intrigeri

I checked all changed files/pages and found no errors and nothing to change, so it seems okay for me.

#3 Updated by intrigeri 2016-11-19 07:31:26

  • Assignee changed from intrigeri to sajolida

#4 Updated by sajolida 2016-12-26 11:09:03

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

Sorry to bother you with this intrigeri, but I wanted your explicit opinion on this branch before merging (see Bug #11942#note-1). It seems like you silently reassigned it to me as if it was a mistake or something…

#5 Updated by intrigeri 2016-12-26 12:17:03

> Sorry to bother you with this intrigeri, but I wanted your explicit opinion on this branch before merging (see Bug #11942#note-1). It seems like you silently reassigned it to me as if it was a mistake or something…

OK, will do. I had not followed this ticket at all, so when it was silently assigned to me by spriver, without being Ready for QA, and without any specific input request, I thought it was a mistake (and didn’t read the history of your previous discussion).

#6 Updated by intrigeri 2016-12-27 08:36:47

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to sajolida
  • % Done changed from 0 to 50
  • QA Check deleted (Info Needed)
  • I’ve pushed a few commits that repair some mistakes on the branch.
  • Regarding commit:57a4d6c6c0e65d92f7a4eb99c862e4432cb288eb: FWIW I think there will still be a sandbox page on the website (generated from the ikiwiki basewiki). But indeed we don’t have to carry our own in Git. So, if I need something like this again (e.g. commit:31cdc2a50fc5e8e49b3e59073592cabc4a56536e from April, 2016) to try how stuff would work on our live website, where should I do it?
  • You’ll want to merge master into this branch and resolve conflicts.

#7 Updated by sajolida 2017-04-07 15:17:40

#8 Updated by sajolida 2017-05-02 10:03:03

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)

Cool, so I merge origin/master into this branch, resolved a bunch of conflicts, reverted 57a4d6c6c0 to keep sandbox.mdwn and pushed!