Commit a1002a9d authored by Tails developers's avatar Tails developers
Browse files

Rely less on todo/* and bugs/*.

parent e88921d7
......@@ -73,9 +73,9 @@ Sorry about that.
<p>This wiki is used as a basic bug tracking system:</p>
<ul>
<li>[[/bugs]]</li>
<li>[[/TODO]]</li>
<li>[[/wishlist]]</li>
<li>[[!tails_bug "" desc="bugs"]]</li>
<li>[[!tails_todo "" desc="TODO"]]</li>
<li>[[!tails_website wishlist]]</li>
</ul>
</div> <!-- #tools -->
......
......@@ -876,7 +876,7 @@ configured for completeness.
It is planned to anonymize the network interfaces MAC address in a
later Tails version. See the related [[design
document|design/MAC_address]] and [[todo item|todo/macchanger]].
document|design/MAC_address]] and [[!tails_todo macchanger desc="todo item"]].
### 3.6.8 Host system swap
......@@ -983,7 +983,7 @@ extension that:
- allows using I2P instead of Tor to visit eepsites (I2P's own hidden
services look-alike); see [[the design document dedicated to Tails
use of I2P|I2P]] for details;
- could help [[fixing Iceweasel's FTP support|todo/FTP_in_Iceweasel]].
- could help [[!tails_todo FTP_in_Iceweasel desc="fixing Iceweasel's FTP support"]].
Thanks to Torbutton, Iceweasel is configured so that Tails browser
fingerprint appears uniformly among Torbutton users. Tails enables
......@@ -1044,7 +1044,7 @@ configured to use the keys.indymedia.org hidden-service keyserver (`hkp://2eghzl
Tor hidden service;
- it is well-synchronized with the HKP keyservers pool.
[[todo/Monkeysphere]]'s `hkpms://` support will be used as soon as
[[!tails_todo Monkeysphere]]'s `hkpms://` support will be used as soon as
possible in place of the hierarchical X.509 certification model.
GnuPG is configured to prefer non-outdated digest algorithms such as
......@@ -1089,7 +1089,7 @@ user|design/virtualization_support]] if it is.
### 3.7.3 Running Tails inside a Windows session
[[Ongoing work|todo/virtualization_support]] will make it easier to
[[!tails_todo virtualization_support desc="Ongoing work"]] will make it easier to
run the CD/USB in a virtual machine inside a Windows session whenever
native boot is impossible or not desirable. This probably will be
implemented by shipping a [QEMU](http://www.qemu.org/) or
......@@ -1116,8 +1116,8 @@ regressions in Tails, especially anonymity and security related
ones. It would also make it easier to work on Tails for developers
who do not own modern powerful hardware.
Research and practical work to setup such an environment [[has slowly
started|todo/automated_builds_and_tests]]. In the meantime, a [[manual
Research and practical work to setup such an environment [[!tails_todo
automated_builds_and_tests desc="has slowly started"]]. In the meantime, a [[manual
test suite|contribute/release_process/test]] is "run" against Tails
release candidates images before they are officially published.
......@@ -1160,12 +1160,12 @@ using sysctl ([[!tails_gitweb chroot_local-includes/etc/sysctl.d/ipv6.conf]]).
Support of arbitrary DNS queries is currently [[missing but
planned|todo/support_arbitrary_dns_queries]].
Bridge support is [[missing but planned|todo/bridge_support]].
Bridge support is [[!tails_todo bridge_support desc="missing but planned"]].
Some tools currently available to command-line users lack the
integration into Tails and/or graphical user interface that would be
needed to make them useful to anyone. See the [[macchanger TODO
page|todo/macchanger]] as an example.
needed to make them useful to anyone. See the [[!tails_todo
macchanger desc="macchanger TODO page"]] as an example.
Providing an easy-to-use tool to inspect and cleanup meta-data in
files (e.g. before they are published on the Web) would help any PELD
......
......@@ -41,7 +41,7 @@ Hence, running I2P should be opt-in, i.e. it should not start per
default. The user must start I2P manually, either by some easily
accessible icon on the desktop/in the applications menu, or by
specifying so during boot (once we make that possible, see the
[[todo/boot_menu]] TODO page).
[[!tails_todo boot_menu]] TODO page).
In addition to providing the I2P client, iceweasel should be able to
handle eepsites (.i2p tld) seamlessly without interfering with any
......@@ -90,7 +90,7 @@ this is a good reason to enable hidden mode, that is to disable
participating in I2P traffic:
[[!tails_gitweb config/chroot_local-includes/usr/share/i2p/router.config]].
[[FoxyProxy|todo/iceweasel_addon_-_FoxyProxy]] has been installed
[[!tails_todo iceweasel_addon_-_FoxyProxy desc="FoxyProxy"]] has been installed
system-wide, and the default iceweasel profile provides with a
configuration handling the I2P integration. FoxyProxy's whitelist
filter is used to make sure that the corresponding urls will be
......@@ -141,7 +141,7 @@ Things to meditate upon
SOCKS5. This effectively breaks FTP completely, so there's room for
adding a pattern above number 4 which matches ftp connections
(i.e. `^ftp://.*`) and proxies them through some ftp proxy using Tor
as its parent proxy. See [[todo/FTP_in_Iceweasel]]. As an addition,
as its parent proxy. See [[!tails_todo FTP_in_Iceweasel]]. As an addition,
at the moment (versions <=0.8) ftp does not work in I2P for
technical reasons, so no pattern for that is needed.
......@@ -168,4 +168,4 @@ Things to meditate upon
* Are the patterns used above correct for their intended purposes?
Does the FoxyProxy setup in any way open up for attacks? See
[[todo/iceweasel_addon_-_FoxyProxy]].
[[!tails_todo iceweasel_addon_-_FoxyProxy]].
......@@ -6,7 +6,7 @@
**This is a not implemented yet.**
See the related [[todo item|todo/macchanger]].
See the related [[!tails_todo macchanger desc="todo item"]].
---------------------------------------------------------------------
......
......@@ -11,7 +11,7 @@ whole bunch of fingerprinting attacks an attacker could mount if it
could pose as the time server and mess with the user's time. We
therefore want to be able to *authenticate* the servers that provide
us with supposedly accurate time information. Home-made research
[[demonstrated|todo/authenticate_time_servers]] that NTPv4's server
[[!tails_todo authenticate_time_servers desc="demonstrated"]] that NTPv4's server
authentication features do not fit our usecase yet, so we have to look
for solutions elsewhere.
......
......@@ -221,8 +221,8 @@ Setting up a Tails persistent volume means:
of us who wrote it is the most efficient at.
* Partition / filesystem / LUKS management is done using `udisks`; the
[[udisks bug wrt.
partition attributes|todo/usb_install_and_upgrade/todo]]
[[!tails_todo usb_install_and_upgrade/todo desc="udisks bug wrt.
partition attributes"]]
is workaround'ed.
### Configure which bits are persistent
......@@ -263,7 +263,8 @@ Persistence settings changes are taken into account at next boot.
### Enable persistence at boot time
Choosing between various persistence modes is one of the reasons why
we've written a graphical [[todo/boot_menu]]: [[todo/TailsGreeter]].
we've written a graphical [[!tails_todo boot_menu]]:
[[!tails_todo TailsGreeter]].
#### Design
......
......@@ -40,7 +40,7 @@ Two alternatives booting methods have been investigated:
We have settled on the *copy ISO's content* way, mostly because it is overall
simpler, more robust, and allows
implementing [[todo/incremental_upgrades]] relatively easily.
implementing [[!tails_todo incremental_upgrades]] relatively easily.
Partitioning
============
......@@ -60,7 +60,7 @@ The system partition (holding Tails) has a size of 1.5 GB, with the
following estimates:
* Tails ISO: 1GB
* 3 [[incremental upgrade kits|todo/incremental_upgrades]], 60 MB each: 180MB
* 3 [[!tails_todo incremental_upgrades desc="incremental upgrade kits"]], 60 MB each: 180MB
The Tails system partition uses a FAT32 filesystem, mainly because it is the
one supported by SYSLINUX we may easily create, in a programmatic manner, from
......@@ -124,11 +124,11 @@ We have `.desktop` files for the following usecases:
Why a fork of liveusb-creator?
==============================
After an initial [[roundup of existing tools|todo/usb_install_and_upgrade/archive]],
After an initial [[!tails_todo usb_install_and_upgrade/archive desc="roundup of existing tools"]],
we decided to use Fedora's `liveusb-creator` as a basis, for reasons that are now
obsolete due to more recent design choices. While we did most of our initial
adaptation work on liveusb-creator with future upstreaming of our changes in
mind, it proved to be hard, and future extension seems now out of question.
Our [[future plans|todo/usb_install_and_upgrade]] include moving to another
Our [[!tails_todo usb_install_and_upgrade desc="future plans"]] include moving to another
piece of software as a basis, and hopefully working more closely with this
future upstream of ours.
......@@ -18,4 +18,4 @@ later used by a desktop notification system.
- [[!tails_gitweb config/chroot_local-includes/etc/skel/.config/autostart/virt-notify.desktop]]
- [[!tails_gitweb config/chroot_local-includes/usr/local/bin/tails-virt-notify-user]]
A bit more work is [[left to do|todo/virtualization_support]].
A bit more work is [[!tails_todo virtualization_support desc="left to do"]].
......@@ -42,8 +42,8 @@ To end with, it might be that we simply have not thought of software
XYZ yet. Reading our [[design document|contribute/design]] may help
you understand which use cases Tails covers and hence which types of
software we may consider. If you feel that XYZ would fill up an empty
space, please [[suggest it to us|todo]] and give valid points for its
inclusion.
space, please [[!tails_todo "" desc="suggest it to us"]] and give valid
points for its inclusion.
Why isn't Tails based on system XYZ?
====================================
......@@ -126,7 +126,7 @@ fit for a stable Debian release, rather than on software that came as
a snapshot of Debian testing/unstable at a given point of time.
*Ubuntu ships the AppArmor Mandatory Access Control system.*
**Answer**: right. We [[would like|todo/Mandatory_Access_Control]] to
**Answer**: right. We [[!tails_todo Mandatory_Access_Control desc="would like"]] to
get something similar into Tails: that's why we have done a great part
of the work that was needed to add basic AppArmor support in Debian
Wheezy. But don't misread the press releases: AppArmor is enabled for
......
......@@ -66,7 +66,8 @@ and it *only* has the `todo/code` tag, you can probably safely skip to
the next section.
So you want to contribute code to Tails but do not know where to
start? Our [[TODO list|/todo]] is huge and frightening, but...
start? Our [[!tails_todo "" desc="TODO list"]] is huge and
frightening, but...
*Do not panic!*
......@@ -77,14 +78,14 @@ Let's see how we can help you picking up a task. A few tips:
much.
* Choose something where your singular skills and knowledge are put to
work.
* Have a look to the [[easy tasks|todo/easy]] list: there is
* Have a look to the [[!tails_todo easy desc="easy tasks"]] list: there is
something, in each of these tasks, that one can do right away since
it does not require deep knowledge of the Tails internals.
On the one hand, you may want to **start doing practical stuff
immediately**. In this case, see the tasks that are *only* tagged
`todo/code` on the [[TODO|todo#code]] list. You probably want to start looking
at the few ones that are also in the [[easy tasks|todo/easy]] list
`todo/code` on the [[!tails_todo "" desc="TODO"]] list. You probably want to start looking
at the few ones that are also in the [[!tails_todo easy desc="easy tasks"]] list
first so that you can gain confidence and we can smoothly learn to
work together.
......@@ -104,10 +105,11 @@ unless you are sure it is really easy you should:
1. **Gather results of previous research and discussions.** Search
this wiki and the [developers mailing-list
archive](https://boum.org/mailman/pipermail/tails-dev) for previous
discussions on the topic you are interested in;
[[some|todo/macchanger]] [[tasks|todo/usb_install_and_upgrade]] are
much harder to get right than one could initially expect, and you'd
better see how difficult it is to implement what you want.
discussions on the topic you are interested in; [[!tails_todo
usb_install_and_upgrade desc="some"]] [[!tails_todo tasks
macchanger desc="tasks"]] are much harder to get right than one
could initially expect, and you'd better see how difficult it is to
implement what you want.
2. **[[Tell us|contribute/talk]] about your plans.** This helps making sure
your idea fits nicely into the [[big picture|contribute/design]]
and nobody is currently working on the same task.
......
......@@ -16,7 +16,8 @@ do let us know — ideally, by submitting a patch with your fix.
# Writing
The easiest documentation tasks may be found by looking at documentation section on the [[TODO|todo#documentation]] list (items tagged `todo/documentation`). Small fixes and
The easiest documentation tasks may be found by looking at
documentation section on the [[!tails_todo "" desc="TODO"]] list (items tagged `todo/documentation`). Small fixes and
enhancements are greatly welcome, and can be done by [[sending
us|contribute/talk]] Git patches, or by publishing a [[Git]] branch.
......
......@@ -11,7 +11,7 @@ feature.
Tasks that are currently stalled by the need for input are listed in
the *Research*, *Discuss*, *QA* and *Test* sections of the [[/TODO]] list.
You probably want to start looking at the ones that are also in the
[[easy tasks list|todo/easy]] first so that you can gain confidence...
[[!tails_todo easy desc="easy tasks list"]] first so that you can gain confidence...
and we can smoothly learn to work together.
# Talk to us
......
......@@ -5,5 +5,5 @@ See:
* the *Promote* section of the [[TODO]] list.
* [[Press and media information|press]]
- [[todo/document_common_Tails_misconceptions]]
- [[!tails_todo document_common_Tails_misconceptions]]
......@@ -192,10 +192,10 @@ translators|translate#tails-l10n]].
Important changes to the documentation are notified on the [[mailing list for
translators|contribute/how/translate#tails-l10n]]. You can consult its
[archive](https://mailman.boum.org/pipermail/tails-l10n/) to search for
recent translation requests. See also the [[translate section of our todo
list|todo/#translate]].
recent translation requests. See also the translate section of [[!tails_todo ""
desc="our todo list"]].
The [[documentation section of our todo list|todo/#documentation]]
The documentation section of [[!tails_todo "" desc="our todo list"]]
lists a number of pages that need improvement. They should be rewritten
at some point, and are of low priority as far as translation work is
concerned.
......
......@@ -63,7 +63,7 @@ Our custom tags include:
- [[!debusertag disk-space]]
- [[!debusertag freeness]]
- [[!debusertag hardening]]: general kernel and toolchain hardening issues
- [[!debusertag mandatory-access-control]]: [[todo/Mandatory_Access_Control]]
- [[!debusertag mandatory-access-control]]: [[!tails_todo Mandatory_Access_Control]]
- [[!debusertag memory-erasure]]
- [[!debusertag privacy-violation]]
- [[!debusertag iceweasel]]
......
......@@ -196,7 +196,7 @@ It must then be copied to `config/binary_rootfs/squashfs.sort`. This file is
automatically used by `lb_binary_rootfs` to tell `mksquashfs` to use the
provided *sort list*.
(See [[todo/improve_boot_time_on_cd]] for details.)
(See [[!tails_todo improve_boot_time_on_cd]] for details.)
Build the final image
---------------------
......@@ -221,7 +221,7 @@ Example:
Prepare update-description files
--------------------------------
1. Prepare update-description files (see [[todo/incremental_upgrades]]
1. Prepare update-description files (see [[!tails_todo incremental_upgrades]]
for details):
* update (create if needed) an update-description file for every
*previous* supported releases (e.g. N-1, N-1~rc2), that describes
......@@ -234,7 +234,7 @@ Prepare update-description files
Testing
=======
Until [[todo/automated_builds_and_tests]] are setup, some manual testing
Until [[!tails_todo automated_builds_and_tests]] are setup, some manual testing
has to be done by the persons preparing the release, in addition to the
real-world tests done by fellow beta-testers.
......@@ -336,7 +336,7 @@ shortly, perhaps even soon enough to integrate them before pushing the
release out officially.
Import the update description files and their detached OpenPGP
signature into the `updates/` tree. See [[todo/incremental_upgrades]]
signature into the `updates/` tree. See [[!tails_todo incremental_upgrades]]
for the file naming conventions.
Then, record the last commit before putting the release out for real:
......
......@@ -53,13 +53,13 @@ Check the image size has not changed much since the last release.
* Browsing (by IP) a HTTP or HTTPS server on the LAN should be possible.
* Browsing (by IP) a FTP server on the LAN should be possible.
* Browsing (by hostname) a FTP server on the Internet should be possible, and
downloading a file should be possible (once [[todo/fix Internet FTP support]]
downloading a file should be possible (once [[!tails_todo fix Internet FTP support]]
is fixed)
* Entering `about:plugins` in the location bar should say no plugin is
installed.
* Does playing HTML5 videos work? In particular, (due to its popularity)
do [youtube](http://www.youtube.com) videos work (once
[[todo/easier YouTube]] is fixed -- currently object unblocking in
[[!tails_todo easier YouTube]] is fixed -- currently object unblocking in
NoScript is required)?
* Compare the fingerprint of Tails and the latest TBB using at least
<https://panopticlick.eff.org/> and <http://ip-check.info/>, and
......@@ -481,6 +481,6 @@ language.
* MAT should be able to clean a PDF file.
* Browsing (by hostname) a FTP server on the Internet should be
possible using GNOME's *Connect to server* feature
(once [[todo/fix Internet FTP support]] is fixed)
(once [[!tails_todo fix Internet FTP support]] is fixed)
* The Tails signing key in `/usr/share/keyrings/tails-keyring.gpg`
should be up-to-date.
......@@ -42,7 +42,7 @@ unexpected issues.
Reverting the faulty feature branch is an option too.
Having our own [[todo/APT repository]] will remove quite some of the
Having our own [[!tails_todo APT repository]] will remove quite some of the
potential for last minute breakage.
Remaining issues
......
......@@ -52,8 +52,8 @@ actions=no archive=yes show=0 feeds=no]]
<h1>Wheezy</h1>
<ul>
<li>[[todo/live-build_3.x]]</li>
<li>[[todo/update_pidgin_otr_translation]]</li>
<li>[[!tails_todo live-build_3.x]]</li>
<li>[[!tails_todo update_pidgin_otr_translation]]</li>
</ul>
</div>
......@@ -9,7 +9,7 @@ ticket so that they reflect the actual status of the task and especially the
next thing to do for it to be solved.
The tickets are currently stored in this wiki in [[todo]]. We are in the process
of setting up a [[todo/better task manager]] (with ticket progress, assignments,
of setting up a [[!tails_todo better task manager]] (with ticket progress, assignments,
...).
# Report progress or failure
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment