[tor-consensus-health] Consensus issues

Damian Johnson atagar at torproject.org
Thu Aug 28 08:54:45 UTC 2014


Oh dear! You're completely and utterly right. My bad.


On Thu, Aug 28, 2014 at 1:20 AM, Sebastian Hahn
<sebastian at torproject.org> wrote:
>
> On 28 Aug 2014, at 10:13, Damian Johnson <atagar at torproject.org> wrote:
>> On a side note I greatly dislike that proposals can be closed without
>> updating the relevant spec. I keep an eye out for changes to the
>> dir-spec and control-spec, not updates to proposals. Is there any
>> compelling reason for not making that a requirement for closing a
>> proposal?
>
> I completely agree that this should be a requirement, but afaict this
> has happened. Check out commit fc8a6f0da0c79783fe48076243970fa6700c4f7c.
>
> It has this diff:
>
>          A space-separated list of supported methods for generating
> -        consensuses from votes.  See section 3.8.1 for details.  If this
> -        line is present, method "1" MUST be included.  Absence of the
> -        line means that only method "1" is supported.
> +        consensuses from votes.  See section 3.8.1 for details.  Absence of
> +        the line means that only method "1" is supported.
>
> Cheers
> Sebastian


More information about the tor-consensus-health mailing list