Karsten Loesing: > Hello everyone, > > we, the Tor Metrics Team, have finished writing our roadmap for the 12 > months between October 2017 and September 2018: > > https://trac.torproject.org/projects/tor/raw-attachment/wiki/org/teams/MetricsTeam/metrics-team-roadmap-2017-11-17.pdf > > https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam#RoadmapfromOctober2017toSeptember2018 > > In the process of writing this roadmap we incorporated feedback from > various people in the Tor community, including suggestions made on this > list. > > And if something didn't make it on this year's roadmap, we made a note > to reconsider in about a year from now. Hm. There are teams like the Tor Browser people who are doing roadmaps only from dev meeting to dev meeting, meaning for 6 months. Actually, that 6 months or dev-meeting to dev-meeting roadmapping is exactly what Isabela said we (should) do in https://lists.torproject.org/pipermail/tor-project/2017-November/001564.html: """ - Next Tor Meeting is arriving, we do the balance of what we have finished, what we will carry on and start selecting tasks for the next roadmap we will be building at the next Tor Meeting. """ So I wonder how this fits into your model. I am especially concerned about stuff that comes up at the next dev meeting that would be a concern for the metrics team as it seems to me, reading what you wrote above, that it would not be considered for the roadmap for the current year but rather would have to wait for the year thereafter. Georg
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev