Commit 0f657cfb authored by Nah's avatar Nah 🖖
Browse files

updating user research sections

parent 4868c056
......@@ -8,7 +8,6 @@ title: User Research Guidelines
---
subtitle: We collect only necessary data to improve our services.
---
>>>>>>> parent of 1e624ba... update content status
key: 3
---
html: two-columns-page.html
......@@ -64,8 +63,14 @@ Before ending the training, coordinate the feedback with the trainer. The two of
It is very important for us to hear back from you. We want to know how the training and the research was for you, how we can improve our support and also, if you want to keep running Tor User Research. We will ask you to fill a form at the end of the research, so we can get your address to send to you a researcher kit (t-shirt and stickers).
We hope to hear back from you very soon!
We will send you our document on **how to report** to the UX team, so please [get in touch](https://lists.torproject.org/cgi-bin/mailman/listinfo/ux) with us to get it.
If you think you won't have time to gather and report in this format, we would love to have another way to get the material you collected. You can take pictures or send your ´raw´ notes for us.
Before your session, read and print this material on [User Research Reporting](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/community/user_research_reporting.md). If you don't think you'll have time to report in this format, we will happily accept your findings another way – for example, you can take pictures or send your 'raw' notes to us.
### How to submit your findings
1. Write your [report](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/community/user_research_reporting.md) (keep it simple).
2. Upload it to our [Gitlab repository](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/README.md).
3. Create issues in the [Research repository](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/README.md).
4. UX team will discuss each issue and forward it to developers when necessary.
## Additional links
......
_model: page
---
title: How to Volunteer
---
body:
## Where to start
If this is your first time running a User Research session for the Tor Project, we recommend starting with one of these studies. Both can be conducted on a rolling basis and ran remotely.
- [Usability Testing Tor Browser Desktop](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2019/4._Tor_Browser_Desktop_-_download__launch__browse.pdf)
- [Discovery Bridges](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2020/discovery-bridges.md)
After choosing which study to run, open an issue in our [GitLab page](https://gitlab.torproject.org/tpo/ux/research). Add the title of your research, then select the Usability Testing template option and fill it in. Please remember to update the issue as your research evolves.
Not all of the data collected in our research is disclosed to the public, but our general findings are. To protect our participants' privacy we take care to anonymize their responses and avoid recording our sessions.
If you're already familiar with the Tor Project and user testing, have a look at our [current needs for user research](https://community.torproject.org/user-research/open/) and see which study better suits you. Remember to drop us an email telling us about your plans so we can follow and support your research.
As a volunteer we also ask that you read and follow our [Code of Conduct](https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.txt), as well our [Guidelines for Research](https://community.torproject.org/user-research/guidelines/).
**Why do we run Demographics?** We don't collect personal data in our [Demographics](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2020/user_demographics-en.md), and all questions are optional. We believe it's important to collect basic demographics to help us understand if we are meeting our mission regarding diversity and inclusion. In addition, collecting these demographics is required for specific studies to support human rights.
**We don't trick participants.** We don't use trick questions in our research. We expect participants to be honest with us, and we must be honest about our questions in return. As a transparent research space our surveys, studies, and reports are all public, and participants are free to view past studies prior to taking part – however they are not advised to do so.
**We don't track participants.** We care about your privacy and security. If we invite you to participate in a study, we won't track you and any recordings will be erased after the report is complete. We advise volunteers not to record their sessions at all.
**Open source for privacy.** We use free and open source software to analyze our data, and we recommend our volunteers do the same. We also ask anyone running research not use software hosted by third parties like cloud providers.
**Decision-making process.** We don't have a single model for decision making. After conducting your research, it's normal to be excited to see your feedback implemented as soon as possible. However all feedback must be discussed internally across the different teams at the Tor Project first. This means that it's often necessary to run the same research more than once to validate your findings, and meet the expectations of the engineers, developers, designers, researchers and others at Tor. Please read our [Guidelines](https://community.torproject.org/user-research/guidelines/) to get to know this process more.
## Checklist
- Read the guidelines on [how to do user research with Tor](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/README.md).
- Read and follow our [Code of Conduct](https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.txt).
- If you don't have one yet, [request a Gitlab account](https://support.torproject.org/misc/bug-or-feedback/).
- Open an issue in the [UX Research Repository](https://gitlab.torproject.org/tpo/ux/research/-/issues).
- Subscribe to the [UX mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo).
- Learn more about our users by reading [Tor's user personas](https://community.torproject.org/user-research/persona).
---
color: primary
---
html: two-columns-page.html
---
image: eye
---
key: 5
---
section: user research
---
section_id: user research
---
subtitle: We care about privacy and security.
......@@ -31,3 +31,6 @@ We are committed to open design, so you can see the user research we have conduc
| TB Circuit Display | Usability testing ([.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2018/3.User_testing_circuit_display_Test.pdf)) | Kampala(UG), Nairobi(KE), Mombasa(KE) | Q118, Q218 | [.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/reports/2018/ur_kenya_2018_Feature_report__Onions_and_Circuit_Display.pdf) |
| Tor Browser for Desktop | User needs discovery ([.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2018/4.00_user_needs_discovery.pdf)) | Bogotá(CL), Cali(CL), Valle del Cauca(CL), Kampala(UG), Hoima(UG), Nairobi(KE) | 2018 | [.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/reports/2018/ur_colombia_2018_report_tbb-tba.pdf) |
| Tor Browser for Android | User needs discovery ([.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2018/4.00_user_needs_discovery.pdf)) | Bogotá(CL), Cali(CL), Valle del Cauca(CL), Kampala(UG), Hoima(UG), Nairobi(KE) | 2018 | [.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/reports/2018/ur_colombia_2018_report_tbb-tba.pdf) |
### Community Research
* [Censored Continent - Understanding the use of tools during Internet censorship in Africa](https://research.torproject.org/techreports/icfp-censored-continent-2020-07-31.pdf): Cameroon, Nigeria, Uganda and Zimbabwe as case studies.
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