Feature #5889
have a maintainer for I2P or remove it
Start date:
2013-07-19
Due date:
% Done:
100%
Description
Tails developers are not very knowledgeable about I2P, we are not using it, and we are lagging behind in terms of maintenance.
We propose to contact I2P upstream to tell them about that situation and propose them to maintain it themselves in Tails. Otherwise we will remove it from 1.0.
Related issues
Blocks Tails - |
Resolved | 2013-09-26 | 2015-07-15 |
Blocks Tails - |
Resolved | ||
Blocks Tails - Feature #5544: Persistence preset: I2P | Confirmed | ||
Blocks Tails - |
Resolved | ||
Blocks Tails - Feature #6039: Research consequences of Torbrowser patches when using I2P | Confirmed | ||
Blocks Tails - Feature #5788: Restart I2P when time changes | Confirmed | ||
Blocks Tails - |
Resolved |
History
#1 Updated by sajolida 2013-07-19 09:48:22
- Starter set to Yes
#2 Updated by sajolida 2013-07-19 09:48:37
- Starter changed from Yes to No
#3 Updated by intrigeri 2013-07-19 09:52:18
- Type of work changed from Upstream to Communicate
#4 Updated by intrigeri 2013-10-03 12:39:10
- Category set to 180
#5 Updated by kytv 2013-10-30 15:01:29
I will (probably) be able to fill this role.
#6 Updated by kytv 2013-11-01 18:27:20
Having looked at the git repo, yes, I will definitely be able to do this.
#7 Updated by intrigeri 2013-11-02 01:36:17
- Status changed from Confirmed to In Progress
#8 Updated by intrigeri 2013-11-02 01:38:16
We’ll mark this ticket as resolved once I2P is updated in an actual Tails release, which should be a sufficient proof of it being maintained :)
#9 Updated by intrigeri 2013-11-30 03:50:42
- Status changed from In Progress to Resolved
Kill Your TV demonstrated that they were able to produce a high-quality topic branch, suitable for merging into devel, that upgrades I2P. Calling this done, then :)