Changes between Version 1 and Version 2 of org/meetings/2014SummerDevMeeting/Roadmaps


Ignore:
Timestamp:
Jul 13, 2014, 2:51:09 PM (6 years ago)
Author:
karsten
Comment:

Transcribe goals and stickies from Tuesday afternoon session.

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/2014SummerDevMeeting/Roadmaps

    v1 v2  
     1= Meeting goals =
     2
     3 - Remove administrative roadblocks to acquiring and administrating new infrastructure (build machines, etc.)
     4 - Fix contracting workflow
     5 - What is the decision-making process for Tor?
     6 - Who do I ask for direction on projects that need to be done?
     7 - Dog food plan for all TPO/TPI/TPC folks (or forks?)
     8 - Moritz would like to resume the discussion of Tor Europe.
     9 - Settle the differences between the company and the community
     10 - Central location for funding info: don't be a bottleneck!
     11 - Figure out the steps for obfs4 deployment.
     12 - Future of pluggable transports (upcoming pluggable transports, BridgeDB (?), tor improvements, etc.)
     13 - Make plans for hidden service performance and measurement project.
     14 - Future little-t-tor development features (single guard, hidden services, etc.)
     15 - Land patch in Instantbird
     16 - Define development roadmap and threat model for BridgeDB.
     17 - Determine how BridgeDB and new bridge distribution mechanisms are going to be funded.
     18 - Establish year 1 Sponsor Q milestones.
     19 - Bridging Tor and OONI.
     20 - Decide concrete directions for pluggable transport specification refactoring.
     21 - Better planning process for little-t-tor
     22 - Better understanding of Tor measurement needs; concrete technical ways to achieve the above
     23 - Moritz wants help automating deployment and monitoring of Tor relays.
     24 - OONI Q3/Q4 development roadmap
     25 - Complete OONI trajectory of how/where to go forward with deployment
     26 - Map out improvements to TBB bootstrapping usability
     27 - Hoping to get funding for Tahoe-LAFS native Tor integration.
     28 - We want to make clearer how people can contribute to Sponsor O.
     29 - Guides: which ones need update, translation, etc.
     30 - Get David Goulet committed to hidden-service development, and Yawning committed to pluggable transport development.
     31 - Decide if we hire harmony and what job they would do.
     32 - Mitigate global passive adversary threats
     33 - Fix user interface and web page and wikipedia.org
     34 - Make integration/testing plan for kernel/socket scheduling
     35 - Repair and strengthen friendship with focus on (unreadable) shared positive vision
     36 - To learn about the culture of this community. The people, the personalities. To understand.
     37 - Ensure Tor Browser Team members are all on the same page with respect to current and future funder deliverables and internal priorities.
     38 - Developers and trainers should have an open discussion about what Tor training covers.
     39 - Make sure nobody gets arrested.
     40
     41= Tuesday afternoon session led by Gunner =
     42
     43(*) means something was deemed important by attendees
     44
     45Morale/safe workplace
     46 - Having more interaction and feedback from Tor people
     47 - I don't even know who are my co-workers
     48 - Building respect amongst team (**)
     49 - Accept apologies and then move on; stop harboring bad feelings
     50 - We need to be civil to other orgs, because you never know who they talk to!
     51 - People don't acknowledge problems (*)
     52 - Tor feels hostile for conversations and lacks secure (unreadable) for everything
     53 - People surprisingly fired (**)
     54
     55Personnel
     56 - Four months without a contract (**)
     57 - I don't know who is supposed to be working on what! (***)
     58 - Total lack of acknowledgement for situations currently impacting workers
     59 - Make all timesheets public, just like reports (*)
     60 - As a volunteer, I pick my coworker. As a contractor, not so much. How's that handled?
     61 - Where should I go when I believe someone is doing a bad job?
     62
     63Sustainability/culture
     64 - We need to establish work-life balance guidelines
     65 - Demonstrate professional respect
     66 - No one mediates disputes (*)
     67 - Treat each other with kindness
     68 - Tor speaks English without common definitions, e.g.: "political"
     69
     70Empowerment
     71 - Lots of responsibility without power to succeed in tasks (***)
     72 - People think they can do my job (*)
     73 - I need authority to get things done (I have the responsibility) (*)
     74 - There is no escalation procedure when people retain information
     75 - Getting help in prioritizing tasks
     76
     77Vision
     78 - Political analysis is totally missing
     79 - No common vision shared (**)
     80 - Is Tor a pure provider of technology or also a political animal? (***)
     81 - Sharing and discussing common vision for Tor related projects
     82 - Tor is impacted by our funders but we deny it.
     83 - Tor is fighting a proxy war for the U.S. government and is internally dishonest (?) about this truth (?) (*)
     84
     85Project
     86 - We don't even use our own projects company-wide (*)
     87 - We meet too rarely and only talk about contracts but not the project
     88 - Tor lacks forensics for incident response but also emotional support for incident response.
     89
     90Decision making/collaboration
     91 - Establish goal setting and achievement for entire team
     92 - Establish united leadership team -- goals of organization.
     93 - How can a meeting be organized without involving people who are on the ground? (*)
     94 - Create clear communication
     95 - Fix bottleneck of communication when conversation fails (**)
     96 - Create structure for process -- human resources, hiring, etc.
     97 - A process for common cooperation is missing for (unreadable) all tasks (***)
     98
     99 - We need a hand-off process for important decisions or relationships.
     100 - Implement liquid democracy for deciding on issues.
     101 - Provide a safe space to deal with our security situation; e.g.: pwnage; e.g.: emotional issues.
     102 - Open a physical space for humans to gather to co-work.
     103 - We accept confines (?) that are constructs. We should define them and empowered (?).
     104 - All documents should be on an (.onion) intranet (***)
     105 - Provide fixed weekly time(s) for discussion/addressing issues and resolving decisions
     106 - Place human resource specialist on staff/board (**)
     107 - Agree on psychosocial care professional selection criteria. (*)
     108 - Discuss everyone's deliverables internally so we can trade/organize better.
     109 - Solution for contractor hiring; deployment should be a separate function
     110 - Focus on intentional expectation setting with all staff/volunteers roles/compensation (*)
     111 - Prioritize early and proactive notifications of issues/status change for team members
     112 - Have a veto procedure for new people
     113 - Have an open legal advisory channel for all TPI folks.
     114 - Provide mediation on demand for conflict resolution (****)
     115 - Have someone say yes when we get offers of help.
     116 - Announce new contracts and their deliverables to spread knowledge on who is working on what and what to expect. (***)
     117 - Set goals for both contractors and employees that they can achieve and are measurable so they can know they have accomplished something (****)
     118 - Inform people beforehand that their contract is going to expire and renewed or not renewed. (*)
     119 - Delegate budget authority and associated decision making (***)
     120 - Collective and improved hiring/on-boarding contractor/employees process could be improved by adding more inputs (**)
     121 - Resolve Tor's long-term vision and priorities to inform decision making (******)
     122
    1123= Roadmaps =
    2124