Feature #10024
Document issues behind having Tails derivatives
70%
Description
People from related projects often ask us about creating Tails derivatives for their custom needs. We should have a documentation explaining the issues behind that and the proper way of doing so.
Subtasks
History
#1 Updated by sajolida 2015-08-14 10:14:37
- Parent task set to
Feature #10026
#2 Updated by sajolida 2015-09-21 03:05:20
- Priority changed from Normal to Elevated
- Target version changed from Tails_1.6 to Tails_1.7
Postponing and so raising priority.
#3 Updated by intrigeri 2015-09-21 09:36:43
Note that Freepto are considering becoming a Tails derivative, so we may soon have a first practical example, and with nice and cooperative people, which should help :)
#4 Updated by sajolida 2015-09-22 07:35:10
- Status changed from Confirmed to In Progress
- Blueprint set to https://tails.boum.org/blueprint/derivatives/
#5 Updated by sajolida 2015-10-03 14:19:23
- QA Check set to Dev Needed
We reviewed the draft by sajolida during the October meeting. Other examples were mentioned such as supporting other cryptcurrencies or different pluggable transports.
#6 Updated by intrigeri 2015-10-03 14:38:35
[Freepto] A hack weekend: what about forking tails? might provide some inspiration on this topic.
#7 Updated by sajolida 2015-10-14 10:40:12
- Assignee deleted (
sajolida) - QA Check changed from Dev Needed to Ready for QA
- Feature Branch set to doc/10024-derivatives
Done! I don’t know who wants to take care of that, so I put no assignee. BitingBird could do that probably but she’s not very active on Redmine lately :)
#8 Updated by sajolida 2015-11-04 12:44:49
- Target version changed from Tails_1.7 to Tails_1.8
We missed this one during the last meeting…
#9 Updated by sajolida 2015-12-03 09:55:20
- Parent task deleted (
Feature #10026
#10 Updated by intrigeri 2015-12-06 16:40:24
- Assignee set to sajolida
- % Done changed from 0 to 70
- QA Check changed from Ready for QA to Dev Needed
I had a look and here are a few comments and suggestions:
- s/free software/Free Software/
- s/possible be encouraged/possible but encouraged/
- s/look and work on our code/look at our code and work on it/
- s/an ISO image smaller in size/a smaller ISO image/
- in “or otherwise break the automatic upgrades mechanism”, s/break/disable/ ?
- wrt. each “or otherwise”: initially I thought we were suggesting an alternate way to do it; but then for at least one of those is rather about warning of adverse consequences; I think the grammar/phrasing of “would need to […] or otherwise” and “should be careful to […] or otherwise” caused this misunderstanding.
- s/looks the same/look the same/
- “In Tails we have very high quality standards”: I don’t believe this is correct, and personally I feel uncomfortable that my work is being described this way (snipping rant about rarely taking time to polish one’s work and instead jumping to the next big thing, that sadly doesn’t apply to me only)
- s/relying our/relying on our/
- s/APT sources/additional APT sources/
#11 Updated by sajolida 2015-12-20 03:46:15
- Target version changed from Tails_1.8 to Tails_2.0
#12 Updated by sajolida 2015-12-25 16:07:33
Thanks for the review! I think I fixed all your concerns with
5740697..303d5a6 in a quite straightforward way, so I’ll proceed with
merging in time for 32C3 so I can point people to it :)
#13 Updated by sajolida 2015-12-25 16:27:09
- Status changed from In Progress to Resolved
- Assignee deleted (
sajolida) - QA Check deleted (
Dev Needed)
#14 Updated by intrigeri 2016-01-01 11:10:36
> Thanks for the review! I think I fixed all your concerns with
> 5740697..303d5a6 in a quite straightforward way, so I’ll proceed with
> merging in time for 32C3 so I can point people to it :)
Good thinking! FTR I had a look at the diff and it looks good :)