On Wed, Jun 15, 2011 at 02:05:44AM -0400, grarpamp wrote:
On workload and stuff...
the idea we had at the 2010 Potsdam meeting where we had primary
and secondary developers for each product.
There is Tor core (ported to various platforms). This is code and
docs. This is what matters. It is not config or packaging.
Above and beyond that, if there is a demand for it, why not introduce
a secondary level of suitably trusted enthusiasts to develop and
manage all the various modes of operation. Officially disclaim it
appropriately as an unofficial vaporware framework, wikify it, put
a couple public developer packaging boxes online and see what
happens.
Also, you could easily publish just a set of torrc's tailored to
various purposes. Or even create an online config generator with
various feature checkboxes.
I don't think most of the target audience knows (or wants to know) what
a torrc is. They want one-click download, install, and run. And that's
what we should give them.
I've no objection to flag days that result in good long term gains.
Well, Flag Day was yesterday, so you've got a whole year to figure out
the plan for next time. ;-)
- Ian
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev