petar / gov4git Goto Github PK

• milestone 1: verifiable prioritization polling based on QV (~2 months)

  • build out working prototype (1 month)
    • identity management
      • generating new identities with ed25519 signature keys
    • community user and group management
      • balance operation for balance management (badges, voting credits, etc.)
    • prioritization polling operations
      • poll operation (create a poll)
      • vote operation (vote on an open poll)
      • tally operation (collect votes and report aggregates)
      • seal operation (finalize a poll and merge into main branch with a verifiable record)
      • list operation (list open polls)
    • deployment to a small group of users (expected in October 2022)
  • polish (1 month)
    • evaluation of user experience
      • installation flow
      • error messages and corrective suggestions
      • issue tracking setup and bug reporting automation
    • versioning and interoperability
      • add governance protocol version info in git artifacts
    • documentation
      • blog article describing end-to-end user workflow and effect of operations on git repos
      • terminal screencast video demonstrating user workflow
    • test
      • testing framework
      • test coverage (all operations)

• milestone 2: verifiable PR approval (1 month)

  • TBD

• milestone 3: retro-active community history verification (1 month)

  • TBD

As an admin, I want to

• add admins to the project
• issue voice credits to a contributor
• issue specific badge(s) to a contributor
• issue voice credits to any contributor with specific badge(s)
• set policies for merging commits
  • reward contributors with voice credits who upvoted the merged commit
  • reward the commit author (s) with voice credits and specific badge(s); perhaps setting different reward badges on different branches (e.g., different languages of the book) of the project.
  • Note that one might need to address a weird edge case in accounting for the voice credits and badge(s) of merged-commit authors who don't have gov4git project accounts. Or, in the MVP, one might consider effectively implementing merge policies only for PRs of commits authored by gov4git project account holders.
• see a list of all voice credit and badge holders, including voice credit balance and badge specifications
• revoke a contributor's badge(s)
• revoke a contributor's voice credits

As a contributor, I want to

• quadratically up- and downvote an open PR of the project
• see my badge(s)
• see my voice credit balance

As anybody, I want to

• create my gov4git project account
• get a verifiable ranked list of the project's open PRs according to the unique cluster match quadratic voting resultsi