sbp commented on issue #321:
URL: 
https://github.com/apache/tooling-trusted-releases/issues/321#issuecomment-3538891695

   There are two reasons for this.
   
   **We don't get private vote threads.** [As @dave2wave 
said](https://github.com/apache/tooling-trusted-releases/issues/318#issuecomment-3534323387)
 in #318:
   
   > During the beta and in production we should require that the address be a 
public mailing list of the project. Part of the ATR attestations we want to 
provide is a link to the public vote thread.
   
   But note that manual tabulation of the vote can still proceed at present, 
and resolution (marking the vote as success or failure) still works. I don't 
know whether we'll be removing the `private@` option entirely, but I assume 
that's @dave2wave's intention from the above.
   
   **Tabulation is computationally expensive and requires a POST.** You need to 
press the `[ Resolve vote ]` button to tabulate the votes from the vote thread. 
Please note that this only works on public vote threads, due to the above, so 
it won't work in the `private@` case. It's also heuristic, and absolutely does 
not work correctly in all cases! We found that people say all sorts of very 
complex things involving the tokens `+1` and `-1` during a vote thread, and it 
is not possible to account for all of these cases in a few dozen lines of 
Python. We do the best we can to cover all cases.
   
   I'm going to close this issue because these are our intended behaviours, but 
I want to note that discussion is still open and if you have any suggestions, 
queries, or comments about any of the above then I'd very much like to hear it 
and this issue is still the appropriate venue. We can reopen this issue if we 
decide to take any further action as a result of continued discussion.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to