[tor-commits] r25502: {website} Dropping last year's tails projects Checked with intrigeri a (website/trunk/getinvolved/en)
Damian Johnson
atagar1 at gmail.com
Mon Mar 5 15:41:00 UTC 2012
Author: atagar
Date: 2012-03-05 15:41:00 +0000 (Mon, 05 Mar 2012)
New Revision: 25502
Modified:
website/trunk/getinvolved/en/volunteer.wml
Log:
Dropping last year's tails projects
Checked with intrigeri and the prior three tails projects are no longer
relevant. He sent replacements that I'll add in a sec.
Modified: website/trunk/getinvolved/en/volunteer.wml
===================================================================
--- website/trunk/getinvolved/en/volunteer.wml 2012-03-03 19:47:35 UTC (rev 25501)
+++ website/trunk/getinvolved/en/volunteer.wml 2012-03-05 15:41:00 UTC (rev 25502)
@@ -347,6 +347,7 @@
and still under very active development.
</p>
+ <!--
<p>
<b>Project Ideas:</b><br />
<i><a href="#tailsStartMenu">Custom GDM3 startup menu, aka.
@@ -356,6 +357,7 @@
<i><a href="#tailsDebianLive">Improve Debian Live support for
persistence</a></i>
</p>
+ -->
<a id="project-torsocks"></a>
<h3><a href="http://code.google.com/p/torsocks/">Torsocks</a> (<a
@@ -724,35 +726,6 @@
</ul>
</li>
- <a id="tailsStartMenu"></a>
- <li>
- <b>Custom GDM3 startup menu, aka. tails-greeter</b>
- <br>
- Priority: <i>High</i>
- <br>
- Effort Level: <i>Medium</i>
- <br>
- Skill Level: <i>Medium to High</i>
- <br>
- Likely Mentors: <i>intrigeri, anonym</i>
- <p>Several major upcoming Tails features need to gather user input at
- startup time: bridges support, persistence, MAC address anonymization,
- etc.</p>
- <p>Existing boot menus lack the graphical widgets and generally
- user-friendliness needed. Hence it was decided to implement Tails startup
- menu in GDM3: GDM3's default login/password prompt needs to be replaced
- with a custom GTK+ application hereby named tails-greeter that allows the
- user to provide any input necessary.</p>
- <p>Anyone undertaking this project should be familiar with GNU/Linux and
- application development; no other skill is required, apart of the ability
- to quickly find practical answers in APIs and documentation for many
- technologies she knows nothing about: this challenging coding project will
- indeed involve getting familiar with some modern GNU/Linux Desktop
- technologies such as D-Bus, GNOME and GConf. Python/GTK+ is probably the
- best suited language for the task.</p>
- <p>For more information see <a href="https://tails.boum.org/todo/boot_menu/">https://tails.boum.org/todo/boot_menu/</a></p>
- </li>
-
<a id="orbot-torbutton"></a>
<li>
<b>TorButton for Mobile Firefox 4 or Custom Browser on Android</b>
@@ -1185,68 +1158,6 @@
</p>
</li>
- <a id="tailsMetadataAnonymizing"></a>
- <li>
- <b>Meta-data anonymizing toolkit for file publication</b>
- <br>
- Priority: <i>Medium</i>
- <br>
- Effort Level: <i>Low to Medium</i>
- <br>
- Skill Level: <i>Low to Medium</i>
- <br>
- Likely Mentors: <i>intrigeri, anonym</i>
- <p>Tor helps greatly in publishing files anonymously. However, much personal
- information can be enclosed *inside* such published files' meta-data: GPS
- coordinates, author's name and so on. Anyone who wants to anonymously
- publish a file can thus far too easily de-anonymize herself.</p>
- <p>A set of tools allowing users to easily inspect and clean up meta-data in files
- would benefit Tor users, and would e.g. be shipped in Tails.</p>
- <p>A graphical user interface is a must, but library and command-line
- interfaces are most welcome so that future work can add support for
- cleaning published files to various publishing tools, such as desktop
- social networking clients and Web content management systems.</p>
- <p>This project mostly consists of writing glue between the many existing
- tools and libraries that provide read/write access to files' meta-data. An
- extensible program design would probably be the best bet, so that support
- for other kinds of files can easily be added later.</p>
- <p>The meta-data cleaning toolkit would run at least on GNU/Linux;
- additional Windows and/or Mac OS X support would be welcome. The tools used
- would be up to the students. The detailed specification is ready and will
- be published soon.</p>
- </li>
-
- <a id="tailsDebianLive"></a>
- <li>
- <b>Improve Debian Live support for persistence</b>
- <br>
- Priority: <i>Medium</i>
- <br>
- Effort Level: <i>Medium</i>
- <br>
- Skill Level: <i>Low to Medium</i>
- <br>
- Likely Mentors: <i>intrigeri, anonym</i>
- <p>Data persistence is a somewhat tricky topic in a Live system context,
- especially one such as Tails, which is explicitly designed to avoid
- leaving any trace of its use.</p>
- <p>Some real-life use cases, however, require some kind of data
- persistence. To start with, Tails should (carefully) support persistence of
- application-specific configurations (e.g. GnuPG keyring) and of a user
- arbitrary data store. Note that persistence in Tails will always be opt-in
- and require encrypted storage.</p>
- <p>The backend work consists of improving Debian Live's existing
- persistence features to make them suit the specific context of Tails. A trust
- relationship is already established with upstream who is happy to merge our
- changes. The codebase is not that small and much refactoring is needed, so
- this really is a programming project rather than a fire'n'forget shell
- script hack contest.</p>
- <p>Anyone undertaking this project must be familiar with GNU/Linux, and
- preferably with Debian. Being able to (quickly learn to) write clean and
- safe programs in shell is also needed.</p>
- <p>For more information, see <a href="https://tails.boum.org/todo/persistence/">https://tails.boum.org/todo/persistence/</a>.</p>
- </li>
-
<a id="torsocksForOSX"></a>
<li>
<b>Make torsocks/dsocks work on OS X</b>
More information about the tor-commits
mailing list