|
[[TOC]]
|
|
|
|
|
|
|
|
= End of Q2 goals =
|
|
|
|
== Roadmaps - keep us true and in sync ==
|
|
# End of Q2 goals
|
|
=== Summary: ===
|
|
## Roadmaps - keep us true and in sync
|
|
|
|
### Summary:
|
|
In Valencia we had the opportunity to spend two days together where we built roadmaps for all the different spheres of Tor. The value of this meeting is immense and we can't waste it. Those roadmaps are the first path we've drawn for where we want to be, it will change for sure, but is a structure that can be used to help organize everything else and keep us in sync. They were created in a moment where everyone was together and thinking together on the same issues, my goal is to use this to sync with sponsor stuff, organization building stuff, development stuff, user support and so on. We are all connected and these roadmaps reflects it. We should continue to using it as a reference and continue improving, rethinking it.
|
|
In Valencia we had the opportunity to spend two days together where we built roadmaps for all the different spheres of Tor. The value of this meeting is immense and we can't waste it. Those roadmaps are the first path we've drawn for where we want to be, it will change for sure, but is a structure that can be used to help organize everything else and keep us in sync. They were created in a moment where everyone was together and thinking together on the same issues, my goal is to use this to sync with sponsor stuff, organization building stuff, development stuff, user support and so on. We are all connected and these roadmaps reflects it. We should continue to using it as a reference and continue improving, rethinking it.
|
|
|
|
|
|
=== Problem to solve: ===
|
|
### Problem to solve:
|
|
Tor needs to adopt a common process for documenting and keeping track of everything. Currently that is no formal way, some ideas has been proposed and adopted, but nothing that is used by everyone. Not having this we make it difficult to know what is going on around the organization. And due to how Tor operates (90% of the time you are working remotely) is crucial to facilitate the access to this information.
|
|
Tor needs to adopt a common process for documenting and keeping track of everything. Currently that is no formal way, some ideas has been proposed and adopted, but nothing that is used by everyone. Not having this we make it difficult to know what is going on around the organization. And due to how Tor operates (90% of the time you are working remotely) is crucial to facilitate the access to this information.
|
|
|
|
|
|
=== End Result: ===
|
|
### End Result:
|
|
Roadmaps should:
|
|
Roadmaps should:
|
|
|
|
|
|
* reflect:
|
|
* reflect:
|
... | @@ -27,11 +27,11 @@ They will be fully done via Trac by using it's ticket system and it's roadmap fe |
... | @@ -27,11 +27,11 @@ They will be fully done via Trac by using it's ticket system and it's roadmap fe |
|
* Person X will to take paternity leave and wants to plan for his absence - he wants to share with his team the tasks he needs to hand over while away.
|
|
* Person X will to take paternity leave and wants to plan for his absence - he wants to share with his team the tasks he needs to hand over while away.
|
|
* At a dev meeting a team wants to reaview the past ideas to plan what to do next about a project
|
|
* At a dev meeting a team wants to reaview the past ideas to plan what to do next about a project
|
|
|
|
|
|
== Simplify - simplify process, build routine and organize information so is easier for everyone to obtain answers whenever they are looking for information. ==
|
|
## Simplify - simplify process, build routine and organize information so is easier for everyone to obtain answers whenever they are looking for information.
|
|
=== Summary: ===
|
|
### Summary:
|
|
To support the goal above and clean the path for us to move forward is important to simplify our processes by building routine exercises or support those that already exist (i.e. weekly dev teams meetings). These are the tools in witch the community will operate and coordinate between themselves. And the most important thing for this goal, is to organize the information and facilitate the access to it.
|
|
To support the goal above and clean the path for us to move forward is important to simplify our processes by building routine exercises or support those that already exist (i.e. weekly dev teams meetings). These are the tools in witch the community will operate and coordinate between themselves. And the most important thing for this goal, is to organize the information and facilitate the access to it.
|
|
|
|
|
|
=== Problems to solve: ===
|
|
### Problems to solve:
|
|
Pain points identified so far that I should address:
|
|
Pain points identified so far that I should address:
|
|
|
|
|
|
* A lot of things hanging around with unknow status that I check and take what the action should be (update the status, close the project, revive the project.. etc):
|
|
* A lot of things hanging around with unknow status that I check and take what the action should be (update the status, close the project, revive the project.. etc):
|
... | @@ -68,7 +68,7 @@ Pain points identified so far that I should address: |
... | @@ -68,7 +68,7 @@ Pain points identified so far that I should address: |
|
* There is a need for reports to keep the flow of information going but the currently solution is not working for different reasons:
|
|
* There is a need for reports to keep the flow of information going but the currently solution is not working for different reasons:
|
|
* some documented here: !https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorMonthlyReports
|
|
* some documented here: !https://trac.torproject.org/projects/tor/wiki/org/meetings/2014WinterDevMeeting/notes/TorMonthlyReports
|
|
|
|
|
|
=== End Results: ===
|
|
### End Results:
|
|
Solve the unknown status list. Have the plan to simplify support and documentation efforts in motion and with a concrete goal of how we want this to look at the end. For instance if we will do email 101 support, how we can have template + training going on to increase the volunteer base for that and therefor support more users in more languages.
|
|
Solve the unknown status list. Have the plan to simplify support and documentation efforts in motion and with a concrete goal of how we want this to look at the end. For instance if we will do email 101 support, how we can have template + training going on to increase the volunteer base for that and therefor support more users in more languages.
|
|
|
|
|
|
Same for documentation, we already have the plan to simplify our FAQ and we will do it, once we are done we should decide on the frequency that we want to review and update it again. Will be building with these initiatives with the community to ourselves in shape for growing.
|
|
Same for documentation, we already have the plan to simplify our FAQ and we will do it, once we are done we should decide on the frequency that we want to review and update it again. Will be building with these initiatives with the community to ourselves in shape for growing.
|
... | | ... | |