Bug #9003

Cleanup outdated blueprints

Added by BitingBird about 5 years ago. Updated about 3 years ago.

In Progress
Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:
Affected tool:


Some blueprints have been implemented, never started, etc and can be deleted:

Blueprints that can be deleted:

Unclear (e.g. no ticket etc.)


#1 Updated by sajolida about 5 years ago

Oh, and is bothering me everytime I tried to browse that page and has been implemented as well.

#2 Updated by BitingBird about 5 years ago

At least some of the children of (for exemple and some reports in it) are spammed. Either dig deep to find the correct versions and archive them, or remove all.

#3 Updated by sajolida about 5 years ago

  • Status changed from New to Confirmed

#4 Updated by spriver over 3 years ago

  • Description updated (diff)
  • Status changed from Confirmed to In Progress
  • Assignee set to sajolida

I went through the blueprints and this is my result of pages that are suitable for deletion. I don't know if we keep some sort of archive.
Some blueprints were a bit unclear to me, if they can be deleted or should be kept. I listed them seperated.

#5 Updated by intrigeri over 3 years ago

Please don't delete those; they have info that can be useful in the future:

#6 Updated by sajolida over 3 years ago

  • QA Check set to Info Needed

#7 Updated by spriver about 3 years ago

I talked to several persons from the project at CCC, and we came across the idea instead of deleting blueprints to move unneeded ones to an (probably read-only) archive where they can easily be accessed for any usage/reading in the future. Of course it's possible to track deleted blueprints via git, but at least I think that this is rather complicated and browsing through (archived) blueprints is a bit easier. So I'm proposing to create something like blueprint/archive/ where blueprints are going to be moved in once they're not needed anymore.

#8 Updated by sajolida about 3 years ago

  • Assignee changed from sajolida to spriver
  • QA Check deleted (Info Needed)

I think that's cool. It won't change the size of the Git repo, will make it easier to search through stuff if needed, and we help us relax on what to archive or not since it will be easier to revert or deal with oversights in archiving.

#9 Updated by segfault about 3 years ago

I guess we can add to this list (on the other hand, maybe some day we want to create a server version of Tails?)

#10 Updated by segfault about 3 years ago

We talked about this during the contributors meeting. We agreed to move the old blueprints to an archive page.

Also available in: Atom PDF