[tor-commits] [community/slideshow] Better strings for localization

[emmapeel at torproject.org]

commit 174e6c0ebdce0972b92ea4dbe62680498130b5ec
Author: gus <gus at torproject.org>
Date:   Tue Apr 13 15:36:50 2021 -0300

    Better strings for localization
---
 content/user-research/guidelines/contents.lr       | 21 +++++++++----
 content/user-research/how-to-volunteer/contents.lr | 34 ++++++++++++++++------
 2 files changed, 40 insertions(+), 15 deletions(-)

diff --git a/content/user-research/guidelines/contents.lr b/content/user-research/guidelines/contents.lr
index ff0586b..c78ca5e 100644
--- a/content/user-research/guidelines/contents.lr
+++ b/content/user-research/guidelines/contents.lr
@@ -35,18 +35,21 @@ You'd love to read about your experiences during the training, product testing,
 
 * Scenario: describe the process of the test you ran.
 * Demographics: While we are not interested in specific characteristics of our audience, or binary attributes, we must know the total reach of your Tor training. You should take [this material]() with you on the day of your research, distribute it among participants, and answer their questions about how to fill it in if they have any.
-* Interview Process: Thank the participant for their willingness to participate in this process and explain that we are testing the product, not them. The interview should not last longer than 20 minutes, you can record if you wish, but you can also take notes on the printed material you will carry with you (or on your computer). Thank the participant again and end the interview.
+* Interview Process: Thank the participant for their willingness to participate in this process and explain that we are testing the product, not them.
+The interview should not last longer than 20 minutes, you can record if you wish, but you can also take notes on the printed material you will carry with you (or on your computer).
+Thank the participant again and end the interview.
 Send us the result - you don't have to write a report, we can do this data analysis with the material you collected.
 
-
 ## Coordinate with the trainer and the Tor UX team
 You're not doing all this work alone - we will support you with meetings, guides, and mentorship if you want. You can join us at any time on our IRC channel #tor-ux and our [mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/ux).
 
-You must be aligned about the agenda and time to run interviews (if that is the case) during the end of the training. **We strongly recommend that you go through the program of the exercise with the trainer**. Also, we want you two to coordinate feedback together — both for you and for your audience.
+You must be aligned about the agenda and time to run interviews (if that is the case) during the end of the training. **We strongly recommend that you go through the program of the exercise with the trainer**.
+Also, we want you two to coordinate feedback together - both for you and for your audience.
 
 At the beginning of the training, be sure to let everyone know what is your role there and why you're taking notes on the practice.
 
 ## Get prepared!
+
 Print and bring with you the material that you will need to run the research - that will probably be something like:
 
 * Demographics
@@ -58,12 +61,18 @@ It is easier to have this material printed and in hand, but if you prefer, you c
 Keep in mind that you might not have Internet access at the venue, so if you're going to install a Tor feature with someone during the interview, you may need to have it downloaded before the training.
 
 ## Report to Tor UX team
-Before ending the training, coordinate the feedback with the trainer. The two of you should work together to hand out post-its for the audience, you can give each participant post-it of a different color per question and ask them to fill it with what they think about: 1. the service they just learned; 2. Tor project; and 3. Tor in general. It can also be questions - keep in mind that any feedback is a good feedback.
 
-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).
+Before ending the training, coordinate the feedback with the trainer.
+The two of you should work together to hand out post-its for the audience, you can give each participant post-it of a different color per question and ask them to fill it with what they think about: 1. the service they just learned; 2. Tor project; and 3. Tor in general.
+It can also be questions - keep in mind that any feedback is a good feedback.
+
+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!
 
-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.
+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
 
diff --git a/content/user-research/how-to-volunteer/contents.lr b/content/user-research/how-to-volunteer/contents.lr
index a3f3f3f..b3a5c81 100644
--- a/content/user-research/how-to-volunteer/contents.lr
+++ b/content/user-research/how-to-volunteer/contents.lr
@@ -8,27 +8,43 @@ body:
 
 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.
+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.
+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.
+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.
+**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 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.
+**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.
+**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.
+**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