Hello Tor Browser team,
as we approach Montreal's meeting and teams will be creating their roadmap for the months between meetings (till winter 2018 meeting). I would like to present you a new way of relationship we are building between teams work and our funding.
Tor is trying to get out of the 'deliverable' funding model, which is mostly used with the current gov grants we have. We are working to shift to funding opportunities that follows a different model, more focus on the execution of the vision of our mission than on specific deliverables.
It will take some time till we have a significant part of our fund to come from this type. But we have already started to seek for these opportunities and some teams will start to shift to this model.
Another thing related to this model are reports. We will still keep our work organized and have tickets associated with every item on the roadmap so we can easily tell what happened with each task. Since it is a model focus more on the execution of the vision of our mission, our accomplishments from our roadmap is what we are reporting as they are driving us towards our mission.
With this said, the Tor Browser 'desktop' team is one that is starting on this model. So for the roadmap exercise in Montreal you will have some freedom when creating it. I am saying 'some' because there are tasks you can't really ignore like keeping up with ESR releases from Mozilla.
I am listing here some areas of work that the team can consider tasks for the roadmap, please add more if you have any. This is just a way to start our brainstorming process for Montreal:
* keep up with ESR releases * acquisition ux work - download process and get connected to the network (tor launcher) * user onboarding ux work - about:tor page * fingerprinting * selfrando * sandboxing * release infra
We can use this pad to document ideas for the roadmap:
https://storm.torproject.org/shared/FJWrnBf1SXemGKhOK_Wxwl57BVlj0Ynjn8lXcjFO...
Cheers, Isabela
Hello everyone!
I wanted to have a little follow up on this. First thanks for checking the pad and adding stuff there.
https://storm.torproject.org/shared/FJWrnBf1SXemGKhOK_Wxwl57BVlj0Ynjn8lXcjFO...
I was wondering if we could take some time on Monday's meeting to talk about this part:
* "New identity for this site" / new identity for every search * Support more locales * UX improvements ** simplifying security UI (Security Slider, NoScript, Click-to-play) ** Hiding or simplifying parts of about:preferences and other footguns ** Fixing performance problems such as connecting to websites ** Improve circuit display (guards, explanations, etc.) ** Improving fonts (whitelisted and bundled) ** acquisition ux work - download process and get connected to the network (tor launcher) ** user onboarding ux work - about:tor page ** adblocker (such as uBlock Origin)
The reason why is that I am working on getting a designer to work with Linda. For that we need to present the tasks this person will be working on with the UX team. I want these tasks to be what you have on your roadmap where ux folks will be working with you.
Right now at the pad we have some 'brain dump' that I need to flash out so I can better communicate what tasks they will be working with TB team.
So, these are the things I would like us to do on Monday (if possible).
1. Organize these user problems by areas an user goes through from learning about the product till using it (and hopefully with frequency ;)
This will help communicate what is the goal of fixing that problem, some folks must have seen the typical user funnel graphs[1] with the stages the user goes till they are active users of a product. For Tor, I think of those like this:
a) awareness
For me this is from when the user does a search online for our site, is able to see our site, is able to learn how to download Tor Browser.
note: that are many user problems in this path - some we can control some we can't like censorship to our site (but we can still provide some help in these cases)
b) acquistion
Here starts from the user ability of installing Tor Browser, starting the application, and then being able to connect to the Tor network and use it to browse a site.
note: I guess you know 20K problems that exist here heheh
c) retention
Our goal here is to create the habit of using Tor Browser. How you do it? One way is by enabling the user to customized their experience according to their needs (security slider, noscript configurations). Another thing that influences these decisions to be able to customize your experience is to understand what is going on. So user education (specially 'in app, at moment, learning moments') is very important.
We get this by investing on user onboarding, on identifying opportunities to create a 'learning moment' which can be a pop-out teaching something new to the user, it also can be better experience on how to configure settings to enable this customization.
The more the user can tailor their experience to their needs, specially while having awareness of what those decisions means regarding security/privacy while using Tor Browser. The higher will be our chances to have them building the habit of using TB.
After these areas, normally the industry has something like 'resurrection', how to get back the people you loose. We don't have that because we don't track people. Our only way to convince someone we lost to give another try is by continuously telling the world about the improvements we are doing :) and maybe they will hear and give us another shot hehehe anw, you get the point.
I would like us to think of ux work in these fronts, and try to organize those tasks under these areas.
Then if possible attach some tickets to the tasks/work we are listing. This will help me have an idea of the problem we are trying to fix.
My personal deadline for the design thing is oct 4th. That is why I would like to do this on Monday's meeting. This exercise will help me a lot!
Cheers, Isabela
[1] https://www.google.com/search?q=user+funnel&source=lnms&tbm=isch&...
On 9/22/17 11:05 AM, isabela wrote:
Hello everyone!
I wanted to have a little follow up on this. First thanks for checking the pad and adding stuff there.
https://storm.torproject.org/shared/FJWrnBf1SXemGKhOK_Wxwl57BVlj0Ynjn8lXcjFO...
I was wondering if we could take some time on Monday's meeting to talk about this part:
- "New identity for this site" / new identity for every search
- Support more locales
- UX improvements ** simplifying security UI (Security Slider, NoScript, Click-to-play) ** Hiding or simplifying parts of about:preferences and other footguns ** Fixing performance problems such as connecting to websites ** Improve circuit display (guards, explanations, etc.) ** Improving fonts (whitelisted and bundled) ** acquisition ux work - download process and get connected to the
network (tor launcher) ** user onboarding ux work - about:tor page ** adblocker (such as uBlock Origin) ...
I skimmed the tbb-usability tickets and added some tickets to the pad. But I am not sure how to set priorities. I suspect everyone will have a different opinion, but I would say that we should focus our efforts on acquisition plus the things that make Tor Browser more difficult to use on a daily basis (e.g., security UI, circuit display, website compatibility problems).
-Mark
On 9/25/17 16:16, Mark Smith wrote:
I skimmed the tbb-usability tickets and added some tickets to the pad. But I am not sure how to set priorities. I suspect everyone will have a different opinion, but I would say that we should focus our efforts on acquisition plus the things that make Tor Browser more difficult to use on a daily basis (e.g., security UI, circuit display, website compatibility problems).
-Mark
Thank you!
Yes, we will have to prioritize things. Also, what doesn't get to be done now can be done later (this roadmap is just from between Montreal meeting and the next one).
We will definitely save this brainstorm so we don't miss what is not taken.
Talking about 'taking' things, I will go over it tomorrow (now my brain is too mushy) and pick some stuff I might consider priority and that the designer can be working with the team. This designer contract will be part time and for 6 months. We will hope to move (after those 6 months) into a full time position.
So what I will be picking will be stuff related to that work. That might be other work on that list that we can do or should still be added to the team roadmap.
Also I will share with y'all whatever I pick so you can 'approve' my suggestions hehe
Like I said, I am just trying to get this designer tasks figure out. So I hope folks does prioritize the rest in Montreal.
cheers, isabela
Hello TBB team! o/
I wanted to share with you a couple of things before you are off to montreal.
1st: design proposal
This is the work we sent to OTF: https://docs.google.com/document/d/18tbCiex9ZAWoUGyWB9jTX94E7o3vcBSyacT_bpgi...
Important note 1: we are only promising the design work not the dev work Important note 2: this contract will be for 6 months. (maybe this is helpful for you as you plan when to do the ux work)
2nd: mobile browser work
Not that you will be the one doing it :P but this is some information related to the work on that proposal. https://storm.torproject.org/shared/X1L3MPAb2AqbXyxdXnawPolhAF95FrkDM4SjcN2S...
Again, maybe this will be helpful for you as you plan your work.
Let me know if you have any questions, Isabela
-
isabela -
Mark Smith