Bug #9003

Cleanup outdated blueprints

Added by BitingBird 2015-03-03 16:26:12 . Updated 2017-03-08 14:12:10 .

Status:
In Progress
Priority:
Normal
Assignee:
spriver
Category:
Target version:
Start date:
2015-03-03
Due date:
% Done:

0%

Feature Branch:
Type of work:
Website
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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

Blueprints that can be deleted:

Unclear (e.g. no ticket etc.)

Subtasks

History

#1 Updated by sajolida 2015-03-05 15:04:27

Oh, and https://tails.boum.org/blueprint/TailsGreeter/ is bothering me everytime I tried to browse that page and has been implemented as well.

#2 Updated by BitingBird 2015-03-05 15:10:51

At least some of the children of https://tails.boum.org/blueprint/TailsGreeter/ (for exemple https://tails.boum.org/blueprint/TailsGreeter/blog 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 2015-03-18 12:59:26

  • Status changed from New to Confirmed

#4 Updated by spriver 2016-12-10 18:02:05

  • Description updated
  • 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 2016-12-11 07:59:47

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

> * https://tails.boum.org/blueprint/desktop_notifications/ (Bug #7989 is resolved)
> * https://tails.boum.org/blueprint/GNotification/
> * https://tails.boum.org/blueprint/HTTP_mirror_pool/ (Bug #7161 is resolved)
> * https://tails.boum.org/blueprint/HTTP_mirror_pool/archive/
> * https://tails.boum.org/blueprint/UEFI/ (Feature #5739 is resolved)
> * https://tails.boum.org/blueprint/UEFI/32-bit/ (Feature #8471 is resolved)
> * https://tails.boum.org/blueprint/UEFI/GRUB/ (is nearly empty and parent blueprint is resolved)
> * https://tails.boum.org/blueprint/UEFI/syslinux/ (probably needed?)
> * https://tails.boum.org/blueprint/UEFI_boot_on_Mac_without_rEFInd/ (Feature #6242 is resolved)
> * https://tails.boum.org/blueprint/audit_AppArmor_profiles/ (Feature #8007 is resolved)
> * https://tails.boum.org/blueprint/delete_obsolete_Git_branches/ (Feature #8616 is resolved)
> * https://tails.boum.org/blueprint/freezable_APT_repository/ (Feature #5926 is resolved)
> * https://tails.boum.org/blueprint/hardware_for_automated_tests/
> * https://tails.boum.org/blueprint/hardware_for_automated_tests_take2/ (Feature #11009 is resolved)
> * https://tails.boum.org/blueprint/incremental_upgrades/
> * https://tails.boum.org/blueprint/monitor_servers/ (Feature #5734 is resolved)
> * https://tails.boum.org/blueprint/rewrite_Git_history/ (Feature #6277 is resolved)
> * https://tails.boum.org/blueprint/sandbox_the_web_browser/ (Feature #5525 is resolved)
> * https://tails.boum.org/blueprint/touchpad/
> * https://tails.boum.org/blueprint/usb_install_and_upgrade/ and subpages
> * https://tails.boum.org/blueprint/automated_builds_and_tests/ and subpages
> * https://tails.boum.org/blueprint/crowdfunding_research/
> * https://tails.boum.org/blueprint/encode_APT_suite_in_Git/ (Feature #8654 is resolved)
> * https://tails.boum.org/blueprint/evaluate_Docker/ (Feature #7530 was rejected)
> * https://tails.boum.org/blueprint/follow_parts_of_Redmine/
> * https://tails.boum.org/blueprint/improve_askbot_to_our_requirements/
> * https://tails.boum.org/blueprint/more_efficient_memory_wipe/
> * https://tails.boum.org/blueprint/protect_against_external_bus_memory_forensics/

#6 Updated by sajolida 2016-12-12 19:12:59

  • QA Check set to Info Needed

#7 Updated by spriver 2017-01-10 10:57:33

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 2017-01-10 18:15:07

  • 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 2017-03-03 19:52:05

I guess we can add https://tails.boum.org/blueprint/server_edition/ to this list (on the other hand, maybe some day we want to create a server version of Tails?)

#10 Updated by segfault 2017-03-08 14:12:10

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