Changes between Version 1 and Version 2 of torbirdy/RoadMap

Jun 24, 2013, 7:58:15 PM (6 years ago)

move this to the road map document from the original sponsor page


  • torbirdy/RoadMap

    v1 v2  
    1 This is where we will list our road map of tickets by milestone and by component. It should provide an overview of all work we'd like to be done for the TorBirdy component, linking to relevant sponsors and so on.
     1== Deliverables ==
     31. Documentation
     4    1. TorBirdy Design Document (see #8775).
     5        - Details TorBirdy's design and the Thunderbird preferences we
     6          change (the ''what'' and the ''why'').
     7    1. Create end-user documentation that details the steps required for
     8    users to use and configure TorBirdy. See #6446.
     9        - This should cover Windows (#8909), Linux (#8910), OS X (#8911), with screenshots of the
     10          installation process.
     11        - The idea is to make it easy for '''anyone''' to use TorBirdy, not
     12          just advanced users.
     13    1. Document the testing steps for motivated and regression testers by
     14    providing a detailed feature list, test cases and expected behavior.
     15    See #7060.
     16    1. Write a detailed FAQ that handles the most frequently asked
     17    questions, such as:
     18        - "Why don't you allow changing Thunderbird settings when TorBirdy is enabled?"
     19        - "Why is automatic checking of emails disabled and how do I enable it?"
     212. Thunderbird Patches
     22    1. Work on getting our patches accepted by Mozilla; given the current
     23    feedback, this probably involves rewriting them. This is very important
     24    as these patches will plug the two (currently) known leaks in TorBirdy.
     25        - See tickets #6314, #6315 and
     283. Security Audit
     29    1. The last time we audited TorBirdy was when we released v0.0.3 one
     30    year ago. We should do this again and preferably after every release to
     31    make sure that we are safe from any sketchy features Thunderbird
     32    introduces with every new release.
     33        - Review overall security, check existing and new preferences.
     34    1. Review some popular add-ons (such as Lightning, see #6319) to make
     35    sure they are safe to use.
     36        - As "some add-ons" is a broad term, starting with #6319 is a good
     37          idea...
     38        - After that, we should have a system where we are open to
     39          reviewing new add-ons if someone requests them.
     414. HTTP Proxy
     42    1. GPG has no SOCKS5 support, so we need a HTTP proxy for
     43    TorBirdy for the Enigmail traffic. See #6974.
     44        - There are two possible solutions:
     45            - ship a HTTP proxy with TorBirdy,
     46            - use a JavaScript HTTP proxy. See #6958.
     485. Integrating Tor
     50    1. Right now, we are assuming the user has Tor installed before running TorBirdy, and if not, we ask the user to install it separately. We should start shipping Tor with TorBirdy as a single package, for each platform that we support. See #8936.
     51        - [ tor-launcher] (the Vidalia replacement) is under active development and will be used to launch Tor for the TBB. We should use that for TorBirdy by either contributing to its development so that it supports Thunderbird out of the box, or just hack it to make it work for us.
     52        - For the Tor binaries, we should either just get them from TBB, or start compiling them ourselves. This is open for debate.
     546. Miscellaneous Tasks
     56    1. Finish packaging TorBirdy for Debian. See #8030.
     57    1. Design a simple webpage that points to the relevant documentation. See #6017.
     58    1. Finalize TorBirdy's logo. See #6016.
     60== Tickets ==