Changes between Version 1 and Version 2 of org/meetings/2019Stockholm/Notes/TorAppEcosystem

Jul 19, 2019, 1:52:48 PM (6 months ago)



  • org/meetings/2019Stockholm/Notes/TorAppEcosystem

    v1 v2  
     1= Tor Application Ecosystem Branding =
     3''How can we provide consistent branding for applications in the Tor ecosystem?''
     5**Facilitator(s):** Nathan
     7**Audience:** Steph, Antonela, Isa?, Roger?, Pili?
     9**Duration:** 1 hour
     11== Prep ==
     13Back in May Nathan and Fabiola from Guardian Project,  Carrie and Tiffany from OkThanks and Steph and Pili from Tor Project had a call to discuss Tor brand usage in applications that use Tor in some way. 
     15The purpose of the call was to align all of our efforts towards providing consistent branding family for applications that use tor and are somehow “endorsed" by the Tor Project. For example, there are currently a number of apps in the Apple Store that include Tor in the name and it can be hard for users to make an informed choice as to which apps are trustworthy and somehow “endorsed” by the Tor Project.
     17For example, we discussed the need for defining a set of requirements and criteria that applications would have to meet in order to be included in this “Tor applications ecosystem” as well as a common language for talking about privacy features within applications. Some ideas for criteria and requirements that came up for me from this discussion are:
     19* If it’s using tor, this should be compiled using source code
     20* Should be open source?
     21* Should be developed by a Tor community member, e.g.
     22  * Someone we know
     23  * actively engaged in the community
     25Furthermore, when talking about a “Tor applications ecosystem” we should clearly define what it means for an app to be included in this ecosystem and also what it does not necessarily mean, e.g we’re not committing or saying that the application code has been audited by us.
     27We also spoke about a potential rating system, e.g level 1 - 5 to allow users to make some sort of value judgement on these apps. Another option could be some sort of feature/properties table, similar to the way matrix currently does this:, the idea being that we could list these somewhere on a Tor portal, e.g the new developer portal.
     29Another idea that was shared was the possibility of designing some sort of “Powered by Tor” or “Tor Community" badge (possibly with some sort of rating attached) for these apps that could be added to their website or GitHub repo and link out to a page explaining what this means exactly. Since we had this discussion I also had a thought about what should happen if we need to revoke the "badge”? How do we announce something like this?
     31Other thoughts around branding Guidelines for “Tor Ecosystem Applications”:
     33* dos and don’ts, e.g can't put "powered by tor" unless…
     34* can't use same colour scheme
     35* differentiate core branding
     36* Tor Browser icon
     37* Should we have a common logo family for community apps ?
     39We briefly discussed Onion Browser and Orbot, and in particular where does Orbot fit in to all this and where should it live going forward e.g Tor Project Android account or Guardian Project Android account.
     41== Notes from Dev Meeting ==
    143Tor App Ecosystem