Adding 'Revamp GetTor' project
Damian Johnson

Damian Johnson commited on 2014-03-02 06:15:25
Zeige 1 geänderte Dateien mit 59 Einfügungen und 0 Löschungen.


GSoC project idea from Sukhbir.


... ...
@@ -785,6 +785,11 @@ meetings around the world.</li>
785 785
     relatively unchanged for quite a while.
786 786
     </p>
787 787
 
788
+    <p>
789
+    <b>Project Ideas:</b><br />
790
+    <i><a href="#revamp_gettor">Revamp GetTor</a></i>
791
+    </p>
792
+
788 793
     <a id="project-torcheck"></a>
789 794
     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/TorCheck">TorCheck</a> (<a
790 795
     href="https://gitweb.torproject.org/check.git">code</a>, <a
... ...
@@ -1719,6 +1724,60 @@ their userbase as well.
1719 1724
     </p>
1720 1725
     </li>
1721 1726
 
1727
+    <a id="revamp_gettor"></a>
1728
+    <li>
1729
+    <b>Revamp GetTor</b>
1730
+    <br>
1731
+    Effort Level: <i>High</i>
1732
+    <br>
1733
+    Skill Level: <i>Medium</i>
1734
+    <br>
1735
+    Likely Mentors: <i>Sukhbir Singh (sukhe), Nima Fatemi (mrphs)</i>
1736
+    <p>
1737
+GetTor is a program that serves Tor bundles and related components over SMTP.
1738
+Users request the Tor Browser Bundle by sending an email to GetTor, which sends
1739
+back the bundle as email attachments. For users in countries where the Tor
1740
+Project website is blocked, GetTor is a convenient way for users to get access
1741
+to the bundles.
1742
+    </p>
1743
+
1744
+    <p>
1745
+GetTor has been unmaintained for a while and needs a revamp. The main issue is
1746
+that because the Tor Browser Bundle size exceeds 25 MB, sending it through
1747
+GetTor no longer works as most email providers don't support attachments
1748
+exceeding 25 MB. To alleviate this issue, bundles are now uploaded on
1749
+cloud-based services such as Google Drive and Dropbox and links are sent
1750
+out in the email body instead of attachments. This current setup is far from
1751
+complete -- GetTor needs a lot of work to get it to a point where it can do
1752
+smart things again and do them in the right way.
1753
+    </p>
1754
+
1755
+    <p>
1756
+As part of this project, you should:
1757
+    </p>
1758
+
1759
+    <ul>
1760
+      <li>Have some understanding of what GetTor does in general and the current state of its operation.</li>
1761
+      <li>Come up with ideas on how to make it better.</li>
1762
+      <li>Convince us if you would like to fix the existing code or want to rewrite GetTor from scratch.</li>
1763
+    </ul>
1764
+
1765
+    <p>
1766
+In addition to the above points, applications should be familiar with Python.
1767
+As part of the application process, study the <a
1768
+href="https://gitweb.torproject.org/gettor.git">GetTor code</a> and submit a
1769
+patch for returning the SHA1 checksum of the package instead of the text in
1770
+sendSorrySize() in response.py. (since you cannot test the patch, as long as it
1771
+is clear that you had some idea of what you were doing, it should be fine)
1772
+    </p>
1773
+
1774
+    <p>
1775
+Note: Please do not submit an application without talking to the mentors:
1776
+#sukhe and #mrphs on IRC. IRC is preferred but if for any reason you don't
1777
+want/can't use it, please email the mentors.
1778
+    </p>
1779
+    </li>
1780
+
1722 1781
 <!--
1723 1782
     <a id=""></a>
1724 1783
     <li>
1725 1784