Amendment Doc 002 - Administration of governance and community documents - V3.0

Public: Only invited members may reply

  • Viewed Bedrock Solutions Bedrock Solutions Blockchain Innovation Foundation Blockchain Innovation Foundation Blockrock Mining Blockrock Mining Canonical Ledgers Canonical Ledgers Consensus Networks Consensus Networks Cube3 Cube3 DBGrow DBGrow De Facto De Facto Factable Solutions Factable Solutions Factom Inc Factom Inc Factomatic Factomatic Factomize Factomize Factoshi Factoshi Federate This Federate This Go Immutable HashQuark HashnStore HashnStore Kompendium Kompendium LayerTech LayerTech Luciap Luciap Matters Matters Nic R Niels Klomp Nolan Bauer PrestigeIT PrestigeIT RewardChain RewardChain Stamp-IT Stamp-IT The Factoid Authority The Factoid Authority VBIF VBIF WB
  • Not Viewed Brian Deery CryptoLogic CryptoLogic

Should the document be ratified or amended as specified by the thread type?


All votes are in

  • Total voters
    26
  • Poll closed .

Timed Discussion

Discussion ended:

Status
Not open for further replies.
Hello,

The Governance Working Group is releasing suggested updates to Doc 002 - Administration of governance and community documents (v3.0)

Why?

This document update introduces Batched Amendments. We have at least 11 other docs remaining that need amending to carry out the Guide removal vote, and we want to push them through all at once. They're ready to go. Doc 002 has now been amended to support this kind of vote process, adding agility to governance work now and in the future.

A lot of docs remain outdated because the process is too cumbersome. If the outcome of a vote means multiple documents need amending, there's little incentive to go do this. The process needs to be easier. A single discussion thread should be able to vote yes or no on multiple documents.

Another practical benefit is that batching amendments together will have a positive effect on engagement. It's much easier for a Standing Party to make an informed decision if all the information and discussion is taking place within the same topic, rather than spread out over 10 different vote threads.

What we don't want are stealth edits. Sneaky little details that creep up and go unnoticed. The doc therefore mentions some additional criteria for Batched Amendments. Information provision with an accurate overview of all key changes is one of them. For that same reason, the scope to Batched Amendments is limited to doc amendments and retirements. New documents cannot be part of this.

The first batch we want to release will not contain any significant contentious changes other than quality-of-life-fixes, as that would impede the chances of ratification. So please refrain from saying: "I won't vote for this until so-and-so gets fixed." We need this Guide removal out of the way.

What?

Specifically, this amendment contains the following changes:

1. Added 4.2. - the option for Batched Amendments.
2. Added 2.3.3.2. - naming the discussion thread for multiple Docs. Happy to hear other suggestions.
3. Changed wording to reflect majority voting by possible future Standing Parties. While it's true future Standing Parties may not have document voting rights, we can just have this be superseded in the respective doc for a Standing Party that shouldn't have said voting rights. In the meantime, we will be future-proofing current docs like this.
4. Added 2.3.6. to Section 3.
5. Updated the version numbering. I think this was previously done incorrectly. See Section 3.2.
 

Chappie

Factomize Bot
This thread is a Document Ratification/Amendment Timed Discussion and I am designed to help facilitate efficient communication.

Guides and ANOs may take part in this discussion and vote. Unless this discussion is ended early or extended, it will end in 8 days after which a vote will take place. After 18 hours from the start of the thread or any point up until 24 hours are left in the discussion, you can make a motion to end the discussion immediately or extend the discussion beyond it's initial time frame by selecting the pertinent button at the top of this thread. If someone "seconds" your motion, a poll will take place which requires a majority of Standing Parties to vote one way or the other.

At the end of the discussion period, Guides will vote first and 4 must vote yes otherwise the process ends. If 4 do vote yes, ANOs then vote and if 60% vote yes, the document is successfully ratified or amended.
 

Chappie

Factomize Bot
We are now 18 hours into the discussion. You may now make a motion to extend this Document Ratification/Amendment Discussion by an additional 72 hours or end this conversation by selecting the pertinent button at the top of this thread. This option will end when there are 24 hours left in the discussion.
 

Chappie

Factomize Bot
Nolan Bauer has made a motion to end the discussion early. If someone seconds this motion by selecting the button below, a vote on the motion will start.

A majority voting yay will pass the motion and the discussion will end immediately. This motion will remain open until the normal discussion period ends or a motion to end the discussion is passed by a majority.
 

Chappie

Factomize Bot
Colin Campbell has seconded the motion to end the discussion early.

A motion is now active at the top of this thread to vote if you want to end the discussion early and move on the next phase. A majority voting yes will pass the motion and the discussion will be closed immediately. This vote will remain open until the normal discussion period ends or another motion is passed.
 

Chappie

Factomize Bot
The motion to end the discussion has passed.

The final poll is available for Guides to vote on now for 3 days. If Guides pass the vote with 4 "Yes" votes then ANOs will be able to vote. If Guides fail to pass, there will be no further action.
 
Status
Not open for further replies.
Top