Team issueshttps://gitlab.torproject.org/tpo/applications/team/-/issues2023-01-09T00:12:11Zhttps://gitlab.torproject.org/tpo/applications/team/-/issues/19Is not saving history hurting Tor Browser retention rates?2023-01-09T00:12:11ZArthur EdelsteinIs not saving history hurting Tor Browser retention rates?The main unique value that Tor Browser provides is network privacy. But we also enable private browsing mode by default, which means history and passwords are not saved.
That's actually pretty inconvenient for a modern web browser. Ever...The main unique value that Tor Browser provides is network privacy. But we also enable private browsing mode by default, which means history and passwords are not saved.
That's actually pretty inconvenient for a modern web browser. Every time the user starts Tor Browser, they don't get the convenience of Restore Session, auto-login, recent pages, history-based completion, importing user data from other browsers, and Sync. This issue was raised in [Gallagher et al 2018](https://lists.torproject.org/pipermail/ux/attachments/20180921/c901ae9f/attachment-0001.pdf)
So, we could consider allowing users to open a "normal browsing" window, that retains history and passwords and even uses "Firefox Sync". They would still get the benefit of network privacy. Saved state could be locked behind a master password, or we could remind users to use whole-disk encryption.
My hypothesis is that this approach could help retain users and enable more users to use Tor Browser as their "main browser". But it would require an analysis of the pros and cons and a careful redesign. We also would need to fix all unpatched network privacy in normal browsing.
So in this ticket I'm proposing we analyze this idea: figure out the best possible design, and determine if the benefits outweigh the costs.https://gitlab.torproject.org/tpo/applications/team/-/issues/14Make list of software and associated licenses published by Application's team2024-03-25T09:00:48ZrichardMake list of software and associated licenses published by Application's teamFrom meeting: https://pad.riseup.net/p/licenses-tor-Bo4uj-keep (archived in https://nc.torproject.net/f/436603).
We should build a list of software we build/support and figure out what licenses we are using.From meeting: https://pad.riseup.net/p/licenses-tor-Bo4uj-keep (archived in https://nc.torproject.net/f/436603).
We should build a list of software we build/support and figure out what licenses we are using.richardrichardhttps://gitlab.torproject.org/tpo/applications/team/-/issues/11Update QA and Testing content on our HACKING document2022-06-23T22:20:56ZGeorg KoppenUpdate QA and Testing content on our HACKING documentOur QA and Testing content on our HACKING page needs some update.Our QA and Testing content on our HACKING page needs some update.https://gitlab.torproject.org/tpo/applications/team/-/issues/10Add mozregression support for Tor Browser2022-06-23T18:42:59ZrichardAdd mozregression support for Tor BrowserSo an old trac user suggested bisecting an issue with the `mozregression` tool in tor-browser#24934
This tool automates the bisection process when attempting to identify when an issue become an issue in Firefox (and other Mozilla produ...So an old trac user suggested bisecting an issue with the `mozregression` tool in tor-browser#24934
This tool automates the bisection process when attempting to identify when an issue become an issue in Firefox (and other Mozilla products). It would be nice to have Tor Browser support, or to implement something similar.
- https://mozilla.github.io/mozregression/quickstart.htmlhttps://gitlab.torproject.org/tpo/applications/team/-/issues/7Migrate and update the documentation from old wikis2023-08-26T06:06:23ZPier Angelo VendrameMigrate and update the documentation from old wikisA few months ago, we decided to move all the documentation that is spread everywhere to the wiki of tpo/applications/team.A few months ago, we decided to move all the documentation that is spread everywhere to the wiki of tpo/applications/team.richardrichardhttps://gitlab.torproject.org/tpo/applications/team/-/issues/6Consider next steps to improve applications QA2023-07-14T15:17:44ZdonutsConsider next steps to improve applications QAWe completed a survey of the tor-qa mailing list in https://gitlab.torproject.org/tpo/ux/research/-/issues/67, which didn't receive much engagement unfortunately. Either way, it's a sign that we should move on. Here's a list of the next ...We completed a survey of the tor-qa mailing list in https://gitlab.torproject.org/tpo/ux/research/-/issues/67, which didn't receive much engagement unfortunately. Either way, it's a sign that we should move on. Here's a list of the next steps as I see them:
**Tests**
- [ ] Produce a new manual test script based on the old [Quality Assurance wiki page](https://gitlab.torproject.org/tpo/applications/tor-browser/-/wikis/Quality-Assurance)
- [ ] Put in place some process to review the list of manual tests before each major release
- [ ] Test and fix all current automated tests (that we want to continue using): see [applications/tor-browser-bundle-testsuite](https://gitlab.torproject.org/tpo/applications/tor-browser-bundle-testsuite/-/issues)
- [ ] Review and update the [testsuite wiki/documentation](https://gitlab.torproject.org/tpo/applications/tor-browser-bundle-testsuite/-/tree/master/doc) if necessary
- [ ] Put in place some process to regularly run and maintain the testsuite
**Recruitment campaign**
- [x] Discuss the timing of running a mini-campaign on social media, the forum and email to recruit to Alpha testers
- [x] Create graphics and messaging to support the campaign: https://gitlab.torproject.org/tpo/operations/communications/-/issues/64
- [x] Review and improve the [tor-qa landing page](https://community.torproject.org/user-research/become-tester/): https://gitlab.torproject.org/tpo/web/community/-/issues/269
- [x] Write a template for "what to test" section to go in Alpha release posts
- [x] Write a blog post for the campaign: https://gitlab.torproject.org/tpo/operations/communications/-/issues/65
- [x] Prepare tweets and other social media messaging
- [x] Create forum badges for Alpha testers: https://gitlab.torproject.org/tpo/community/support/-/issues/40076 & https://gitlab.torproject.org/tpo/community/support/-/issues/40075
- [x] Update the sticky post in the [Alpha feedback category](https://forum.torproject.net/c/feedback/tor-browser-feedback/7)
- [x] Figure out what to do with release posts (e.g. cross-post them into the Alpha feedback category): https://gitlab.torproject.org/tpo/community/support/-/issues/40077
- [x] Select some (or all) of the above for translation into RU
- [x] Launch the campaign and onboard new Alpha testers
**QA party**
- [ ] Schedule an internal QA party during an all-hands approx 1-1.5 months before stable release
- [ ] Work with User Support to create a format for this session
- [ ] Host the QA party and translate the results into tickets
**Other**
- [x] Include a test-banner on `about:tor` on Nightly and Alpha releases: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40886
- [ ] Begin collecting metrics on the platforms we're receiving feedback on to identify gaps in our QA
- [ ] Review our [Nightly](https://nightlies.tbb.torproject.org/nightly-builds/tor-browser-builds/) and [Alpha](https://www.torproject.org/download/alpha/) /download pages, and potentially combine these