Settle on a voting solution

Empieza revisando los requisitos del issue #33 y comparando los sistemas existentes de referencia enumerados: Caritat, CIVC, Elekto, Google Forms y el sistema de votación de Codeberg. El trabajo estará terminado cuando el TSC llegue a una decisión sobre una solución de votación y la documente, abordando la autenticidad, el secreto, la inmutabilidad y la UX de la tabulación de votos.

Currently, there's no documented consensus on how a vote among the LoopBack TSC members should occur (i.e. how to cast a vote). In the past, we have used GitHub Teams Discussions and GitHub Issues Reactions. However, non of these meet the following requirements:

• Authenticity: The authorisation to vote is only restricted by GitHub authentication. Requiring a PGP-signed Git Commit may be more resilient against account takeovers.
• Secrecy during voting process: The votes are visible to other TSC members, which may sway their own votes.
• Immutability: The votes can be modified after the voting itself has concluded. This is in part because the TSC members are delegated the GitHub Organisation Admin role, which means that locking a GitHub Issue does not prevent votes changes.
• Vote tabulation UX: For GitHub Issue-based voting, there's nothing preventing non-TSC members from "casting a vote". This mean that tabulation would require filtering through the noise (e.g. through the use of the GitHub API).

This issue is to aid in discussing and deciding on a more robust solution.

Prior art

• Caritat
  • Used by the Node.js TSC for recent votes (e.g. https://github.com/nodejs/TSC/pull/1206) Ongoing discussion: https://github.com/nodejs/TSC/issues/1165
  • Git-based workflow
  • Does not require new infrastructure
• CIVC (alt. website)
  • Web-based workflow
  • Third-party hosted websites available (see links above); Self-hosted also an option.
  • Used for Cloud Foundry TOC elections
  • Prev. used for Kubernetes elections (prior 2021).
• Elekto
  • Web-based workflow
  • Requires self-hosting
  • Intended to be a replacement for CIVC
  • Currently being tabled by Cloud Foundry for their upcoming TOC election: https://github.com/cloudfoundry/community/pull/282
  • Used in Kubernetes 2021 elections: https://github.com/kubernetes/community/blob/9cc5dc80174d04a7d05f4c4fb387f9efea167c5b/events/elections/2021/README.md
    K8's problem statement: https://github.com/kubernetes/community/issues/5096
• Google Forms (or equivalent)
  • Web-based workflow
  • Used in OpenJS Foundation Board Seat Election (e.g. https://github.com/openjs-foundation/cross-project-council/issues/859)
• Codeberg voting system
  • Sends voting PIN via email
  • Used by Codeberg e.V.: https://codeberg.org/Codeberg/Contributing/issues/58

All of the listed solutions utilise the Condorcet election method.

Except Caritat, all of the solutions do not provide any method to validate the authenticity of the results.