[tor-dev] Proposal 301: Don't include package fingerprints in consensus documents

teor teor at riseup.net
Wed Mar 13 22:58:20 UTC 2019

> On 14 Mar 2019, at 03:50, Iain Learmonth <irl at torproject.org> wrote:
> Signed PGP part
> Hi,
>>> On 25/02/2019 23:30, teor wrote:
>>>> Looks good to me, let's merge it as an "accepted" proposal?
> This is now proposal 301.
> What is the process by which this becomes "accepted"? Is this just a
> matter of someone making that commit?

Here's what "Accepted" means:

   Accepted: The proposal is complete, and we intend to implement it.
      After this point, substantive changes to the proposal should be
      avoided, and regarded as a sign of the process having failed


I can't imagine us making any substantive changes to the proposal.

The reasons and actions are clear, and there are clearly-defined sub-tickets
for each of the tasks. We have successfully implemented similar tasks before.

Unless anyone objects in the next week, let's make this change:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20190314/22a171a4/attachment.sig>

More information about the tor-dev mailing list