Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-28 Thread Tim Wilson-Brown - teor
> On 28 Jan 2016, at 01:05, Nick Mathewson wrote: > > On Tue, Jan 26, 2016 at 9:01 PM, Tim Wilson-Brown - teor > > wrote: >> >> On 26 Jan 2016, at 23:19, David Goulet wrote: >> >> On 26 Jan (07:00:31),

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-27 Thread Nick Mathewson
On Tue, Jan 26, 2016 at 9:01 PM, Tim Wilson-Brown - teor wrote: > > On 26 Jan 2016, at 23:19, David Goulet wrote: > > On 26 Jan (07:00:31), Nick Mathewson wrote: > > On Mon, Jan 25, 2016 at 5:14 AM, David Goulet wrote: > > On 18 Jan

[tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-27 Thread Spencer
Hi, > > Nick Mathewson: > We should make a chart of what > times we have in common. :) > http://www.when2meet.com Wordlife, Spencer ___ tor-dev mailing list tor-dev@lists.torproject.org

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-26 Thread David Goulet
On 26 Jan (07:00:31), Nick Mathewson wrote: > On Mon, Jan 25, 2016 at 5:14 AM, David Goulet wrote: > > On 18 Jan (07:13:36), Tim Wilson-Brown - teor wrote: > >> > >> > On 15 Jan 2016, at 03:31, David Goulet wrote: > >> > > >> >> Friday January 29: 8:30 am

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-26 Thread Nick Mathewson
On Mon, Jan 25, 2016 at 5:14 AM, David Goulet wrote: > On 18 Jan (07:13:36), Tim Wilson-Brown - teor wrote: >> >> > On 15 Jan 2016, at 03:31, David Goulet wrote: >> > >> >> Friday January 29: 8:30 am eastern (1330 UTC) >> >> >> >> Prop#252: Single Onion

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-26 Thread Tim Wilson-Brown - teor
> On 26 Jan 2016, at 23:19, David Goulet wrote: > > On 26 Jan (07:00:31), Nick Mathewson wrote: >> On Mon, Jan 25, 2016 at 5:14 AM, David Goulet wrote: >>> On 18 Jan (07:13:36), Tim Wilson-Brown - teor wrote: > On 15 Jan 2016, at 03:31, David

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-25 Thread David Goulet
On 18 Jan (07:13:36), Tim Wilson-Brown - teor wrote: > > > On 15 Jan 2016, at 03:31, David Goulet wrote: > > > >> Friday January 29: 8:30 am eastern (1330 UTC) > >> > >> Prop#252: Single Onion Services [DRAFT] > >> Prop#260: Rendezvous Single Onion Services [DRAFT]

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-24 Thread George Kadianakis
Nick Mathewson writes: > So, one of the longstanding problems with Tor's (change) proposal > system has been that proposals sit around for a long time without > sufficient discussion or approval. When they're about to be > implemented, we do an informal "hey did anybody

[tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-20 Thread Spencer
Hi, Lunar: Proposals are all kept in the “torspec” Git repository [and] in Nick Thanks for taking the time to share this!! Wordlife, Spencer ___ tor-dev mailing list tor-dev@lists.torproject.org

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-19 Thread Nick Mathewson
On Sun, Jan 17, 2016 at 8:39 PM, isis wrote: > Nick Mathewson transcribed 2.8K bytes: >> Here's the schedule I have in mind for the first meeting, based on >> proposals already nominated at the IRC dev meeting. > > This idea and the schedule sound great to me. (Minus that

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-18 Thread Lunar
Spencer: > >Nick Mathewson: > >proposals sit around for a long time > > > > Is there a summarized visualization of these, or is it sifting through > emails and tickets? Proposals are all kept in the “torspec” Git repository: https://gitweb.torproject.org/torspec.git/tree/proposals Once in a

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-17 Thread Tim Wilson-Brown - teor
> On 15 Jan 2016, at 03:31, David Goulet wrote: > >> Friday January 29: 8:30 am eastern (1330 UTC) >> >> Prop#252: Single Onion Services [DRAFT] >> Prop#260: Rendezvous Single Onion Services [DRAFT] >> Prop#246: Merging Hidden Service Directories and

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-17 Thread isis
Nick Mathewson transcribed 2.8K bytes: > Here's the schedule I have in mind for the first meeting, based on > proposals already nominated at the IRC dev meeting. This idea and the schedule sound great to me. (Minus that the HS devs should be at the HS one.) Thanks, Nick! Side note: I've never

[tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-14 Thread Nick Mathewson
So, one of the longstanding problems with Tor's (change) proposal system has been that proposals sit around for a long time without sufficient discussion or approval. When they're about to be implemented, we do an informal "hey did anybody look at that?" check, but that's not really good enough.

[tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-14 Thread Spencer
Hi, Nick Mathewson: proposals sit around for a long time Is there a summarized visualization of these, or is it sifting through emails and tickets? contribute usefully to discussions, I will prioritize your nominations [for proposals] more Sounds fair and balanced. Wordlife,

Re: [tor-dev] Proposals should have reviews. Let's make sure that happens. Here's a schedule.

2016-01-14 Thread David Goulet
On 14 Jan (11:18:26), Nick Mathewson wrote: > So, one of the longstanding problems with Tor's (change) proposal > system has been that proposals sit around for a long time without > sufficient discussion or approval. When they're about to be > implemented, we do an informal "hey did anybody look