wiki:Outreachy

ABOUT

Outreachy is an intern program for members of groups traditionally underrepresented in technology. Check out their main page for more information about eligibility.

FOR PARTICIPANTS

About Tor

The ability to access the Internet anonymously and free from repressive observation is critical for the protection of basic freedoms, especially for vulnerable and marginalized populations including journalists, activists, political dissidents, and human rights workers.

The Tor Project is a US 501(c)(3) non-profit organization advancing human rights and freedoms by creating and deploying free and open source anonymity and privacy technologies, supporting their unrestricted availability and use, and further their scientific and popular understanding.

The Tor network and Tor Browser are currently used by over four million people every day to protect their privacy, safety, and freedom of expression on the Internet.

2020 Application

The Tor Project is applying to participate in the Outreachy round that runs May to August 2020.

Contact Information

The coordinator for this Outreachy period is Pili Guerra (pili AT torproject DOT org, pili on IRC). Drop her an email or ping her on IRC with any questions you have during the application period.

Projects

Project 1: Help Tor Project support our users

Mentor: gus at torproject.org / IRC: ggus

The Community Team at Tor Project is looking for an intern to help us support our users receive and find the most up to date information on using our products. As part of this internship we’re looking for someone to:

Help us to answer support queries that come in through our frontdesk@ email address, #tor irc channel and other informal support channels such as:

  • Reddit,
  • Stackoverflow,
  • blog comments
  • Google Play Store for Tor Browser for Android reviews and feedback

Keep our documentation updated: When new versions of Tor Browser are released, we need to update the Tor Browser User Manual with any usage details and explanations of new features as well as with updated screenshots.

Fix small layout issues with our Tor Browser Manual and Support websites.

Compile a list of common user issues: Write a monthly report collating any common user issues found throughout all of our support channels.

During March 5 - April 7, you must:

  1. Read our documentation:
  1. Check and answer common questions from our users (probably some of them you will need to do some research) - we will email this to applicants, get in touch with us.
  1. Read our open issues and submit a pull request to tickets open in our repositories; you will need a Gitlab account, get in touch with us.
  1. Install an IRC client and learn how to use IRC; join our channels: #tor, #tor-project, #tor-south, #tor-project, #tor-www. Some IRC client suggestions: Hexchat, irssi, weechat...
  1. Subscribe to Tor mailing lists: tor-community-team, global-south and tor-project
  1. Join us on the Community Team meeting - every Monday, 1600 UTC, #tor-meeting channel on IRC

Project 2: IPv6

In 2020, we are working on improving Tor Relay IPv6 support.

The Internet Protocol, version 6 (IPv6) is a low-level protocol that is used for internet communication. The older Internet Protocol, version 4 (IPv4) is slowly being replaced by IPv6.

More Tor clients are running on IPv6-only or dual-stack (IPv4 and IPv6) networks. But only 20% of Tor’s available relay bandwidth supports IPv6. We want to improve Tor relay support for IPv6, so that it is easier for relay operators to run IPv6 relays. We want to automate relay IPv6 address discovery, and relay reachability self-checks

Getting started with tor development
  1. Clone tor using git: https://github.com/torproject/tor
  2. Build tor from source
  3. Run the tor unit tests using "make check". Let us know if they fail, and we'll help fix them
  4. Clone chutney using git. Chutney is a tor integration test tool: https://github.com/torproject/chutney
  5. Go to the tor directory, and run the tor integration tests using "make test-network". Let us know if they fail, and we'll help fix them
  6. Make sure you have a GitHub account, so you can submit pull requests to the tor or chutney GitHub repository
Initial Tasks
Main Tasks
Stretch Goals
All outreachy-ipv6 Tickets

Available tickets are usually "new" or "reopened", and have no owner.

Component: Core Tor/Chutney (9 matches)

Ticket Summary Status Owner Reviewer Milestone
#17011 chutney doesn't verify using IPv6 addresses assigned
#20067 Chutney should verify IPv6 SOCKSPorts assigned MrSquanchee
#20068 Chutney tests for IPv6-only bridge clients assigned
#20142 chutney IPv6 HiddenServicePort tests assigned MrSquanchee
#30182 IPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support IPv6 assigned
#33598 chutney does not fail on some SOCKS errors assigned c
#33609 Check that onion services have successfully posted descriptors before verifying needs_review c asn
#33825 Make Environ handle "in" and "get()" like a dict needs_revision
#33677 Stop waiting a set time for onion service descriptors new

Component: Core Tor/Tor (13 matches)

Ticket Summary Status Owner Reviewer Milestone
#26646 add support for multiple OutboundBindAddressExit IP(ranges) assigned Tor: unspecified
#31543 Add unit tests or chutney tests for IPv6Traffic assigned Tor: unspecified
#33812 Add unit tests for bandwidth statistics functions needs_review MrSquanchee ahf Tor: unspecified
#7193 Tor's sybil protection doesn't consider IPv6 needs_revision nickm Tor: 0.4.4.x-final
#33617 Add a BandwidthStatistics option and consensus parameter needs_revision MrSquanchee asn Tor: 0.4.4.x-final
#33618 Add IPv6 Support to is_local_addr() needs_revision kimimaro teor Tor: 0.4.4.x-final
#33788 Check the return value of tor_inet_ntop() and tor_inet_ntoa() needs_revision nickm Tor: 0.4.4.x-final
#33919 Write unit tests for channel_matches_target_addr_for_extend() needs_revision nickm Tor: 0.4.4.x-final
#33408 Make tor versions sortable, by adding the commit number to EXTRA_INFO new Tor: 0.4.4.x-final
#33582 Make bridges wait until they have bootstrapped, before publishing their descriptor new Tor: 0.4.4.x-final
#33632 List ed25519 fingerprints on the command line new Tor: unspecified
#33768 Make tor_inet_pton() handle bad addresses consistently on Windows new Tor: 0.4.4.x-final
#33816 Fill in missing IPv6 addresses in extend cells new Tor: 0.4.4.x-final


2019 Application

The Tor Project is participating in the Outreachy round that runs December to March 2020.

Contact Information

The coordinator for this Outreachy period is Pili Guerra (pili AT torproject DOT org, pili on IRC). Drop her an email or ping her on IRC with any questions you have during the application period.

We have an excellent set of mentors for this period - Stephanie (steph AT torproject DOT org, stephw on IRC), Gus (gus at torproject.org, ggus on IRC).

Projects

Deadline is Nov. 5, 2019 at 4pm UTC to record your contributions and create a final application.

We have two projects in mind. We will decide whether to mentor one or both based on the interests and expertise of the applicants.

Project 1: Help Tor Project support our users

The Community Team at Tor Project is looking for an intern to help us support our users receive and find the most up to date information on using our products. As part of this internship we’re looking for someone to:

Help us to answer support queries that come in through our frontdesk@ email address, #tor irc channel and other informal support channels such as:

  • Reddit,
  • Stackoverflow,
  • blog comments
  • Google Play Store for Tor Browser for Android reviews and feedback

Keep our documentation updated: When new versions of Tor Browser are released, we need to update the Tor Browser User Manual with any usage details and explanations of new features as well as with updated screenshots.

Fix small layout issues with our Tor Browser Manual and Support websites.

Compile a list of common user issues: Write a monthly report collating any common user issues found throughout all of our support channels.

During October 1 - November 5, you must:

  1. Read our documentation:
  1. Check and answer common questions from our users (probably some of them you will need to do some research) - we will email this to applicants, get in touch with us.
  1. Read our open issues and submit a pull request to tickets open in our repositories; you will need a Gitlab account, get in touch with us.
  1. Install an IRC client and learn how to use IRC; join our channels: #tor, #tor-project, #tor-south, #tor-project, #tor-www. Some IRC client suggestions: Hexchat, irssi, weechat...
  1. Subscribe to Tor mailing lists: tor-community-team, global-south and tor-project
  1. Join us on the Community Team meeting - every Monday, 1600 UTC, #tor-meeting channel on IRC

Workflow expected during the internship

  1. Everyday connect to IRC and hang out on #tor-www, #tor, #tor-project, #tor-south and other channels
  2. Connect to Frontdesk service and answer users.
  3. Check blog posts and social media for users comments reporting issues.
  4. Based on users feedback [1, 2 and 3]: open tickets to report bugs to Tor Browser devs, make Pull requests with corrections and new content to our documentation
  5. If you find outdated or incorrect information on Tor Project websites, we expect you to submit a ticket and/or a pull request.
  6. Community Team meeting happens every Monday, 1600 UTC on #tor-meeting. You will need to update our meeting pad with your work.

Newcomer guide

If you're lost, here's a beginner guide to help you.

Step 1

Goal: first steps with Tor Browser and join our communication channels.

  • Install and try Tor Browser. Yep, it's very simple and important to use Tor so you can learn and help others.
  • Subscribe to tor-community-team, global-south and tor-project mailing lists: You can find all the mailing lists here: https://lists.torproject.org
  • Create an IRC account, so you can chat with Tor folks and see what's happening. IRC is a little bit tricky to start, so I suggest you to use an IRC client (for example, Hexchat) and follow the instructions:

https://support.torproject.org/get-in-touch/irc-help/

  • Create an account in GitLab(dip.torproject.org): ping Pili or Gus to create an account for you. We will be available on #tor-www channel.

Step 2

Goal: understand the documentation workflow.

Note: The Tor Project is currently working to migrate issues from trac.torproject.org to dip.torproject.org. Some teams are already using dip.torproject.org (Community team, for example).

Step 3

Goal: review and improve our documentation based on user feedback.

  • Read and answer users questions in public forums (Reddit, stackoverflow, blog.tpo).
  • If there's something outdated, incorrect or missing from our documentation resources, open a ticket in dip (support, manual, etc)
  • If you know the answer, submit PRs, like phase 2.

Step 4

We will submit to you some questions from Frontdesk, so you can practice :)

Project 2: Improve Tor's image in the media and our communications resources

Contact Stephanie (steph AT torproject DOT org, stephw on IRC).

https://www.outreachy.org/december-2019-to-march-2020-internship-round/communities/tor-project/#improve-tors-image-in-the-media-and-our-communicat

2018 Application

Contact Information

The coordinator for this Outreachy period is Tommy Collison (tommyc AT torproject DOT org, t0mmy on IRC). Drop him an email or ping him on IRC with any questions you have during the application period.

We have an excellent mentor for this period — Colin Childs (colin ATtorproject DOT org).

The Projects

We have two projects in mind. We will decide on which one based on the interests and expertise of the applicants.

  • User Advocate

Tor is looking for a user advocate who would work with members of Tor’s development and community teams to help us understand where users struggle to use Tor. A secure web browser only works if it’s usable.

This intern will monitor our bug-reporting channels, IRC rooms, and social channels to get a sense of what new bugs appear in our software, and where users have problems connecting to and using Tor. Each month, we’d like the intern to report on the most common bugs, problems, questions, and other issues that users have.

To get started, we suggest you look around Tor’s bug tracker to see the sorts of problems users are currently reporting. What are some recurring themes or trends? When do bug reports spike? Feel free to respond to one or more of these questions and email your answer to Tor’s Outreachy coordinator, so we can get a sense your work!

  • Documentation Reviewer

For this task, the intern would help the community team update, review, and format sections of the Tor documentation on how to add Tor’s privacy and anonymity protections to other apps. Much of this documentation is written by volunteers and is not regularly maintained. Tor is about to transition to a new support portal, and the intern would help make this content ready to be displayed on the new website.

To get started on this task, check out Tor’s documentation pages. We’d like the intern to focus on updating these pages in particular.

Familiarizing Yourself with Tor

  • Hang out on #tor-project and #tor-dev to get a sense of the community. Introduce yourself as someone interested in Tor usability. If you're not familiar with IRC, Fedora has a good beginner's guide, and ​​OFTC's website has info on connecting to our specific IRC server. If you're can't figure out how to connect, drop Tommy an email, and he'll be happy to help.
  • If you can, attend the IRC meetings of the Community Team (16:00 UTC every Monday), the Network Team (Mondays 17:00 UTC), the ApplicationsTeam (Mondays 18 UTC) and the Development Team (19:00 UTC on Mondays) and introduce yourself.
  • Check out the support wiki.
  • Check out some of the Community Team's and Network Team's current projects.
Last modified 3 months ago Last modified on Mar 17, 2020, 4:23:42 AM