CIP 0 Goverance proposal: historic versioning

Purpose: Charter Improvement Proposals - CIP-0
Status: Public Notification & Drafting
Voting: July 22 - 4 August
Author(s): @lee0007 @mheuer
Reviewers: under review


Update the current AN DAO Charter v1.0.0 to AN DAO Charter v1.1.0, which includes the changes of AN DAO Charter v1.0.1

November 2021 edits were not ratified, due to competing priorities and limited resources. It is important to state these changes do not alter the legal interpretation of AN DAO Charter v1.0.0.

Changes applied in v1.0.1

Changes applied in v1.1.0

  • Charter restructuring and formatting. Discussed with @fartunov @Alex and members of the Compliance Committee.…v1.1.0).
    – Restructures the charter chapters into eight individual .pdf files.
    – Simplifies the paragraph numbering.
    – Separate files are then collated into a single .pdf file uploaded via IPFS and referenced in the AN Main DAO
    – Individual parts callow merge/rework in future CIPs.

To ensure no material alterations the final version v1.1.0 is subject to Compliance Committee review.


Public Notification & Feedback: This proposal requires 30 days of public notice. Followed by a 14-day voting window. We welcome all feedback and aim to review all comments within 48 hours.

Voting: The proposed date for voting to begin is Friday 22 July 2022 to overlap with voting for CIP 1 CIP 2. We ask ANT holders to vote either Yes or No. The suggested text for the vote is:

  • Y /N Approve Aragon Network DAO Charter v1.1.0

Open Questions

Can Compliance Committee members please confirm for the record that v1.1.0 does not alter the legal interpretation of current AN DAO Charter v1.0.0. Interpretation may be the wrong word here. Please advise @eaglelex @Tayy @ronald_k

Because of the restructuring/reformatting introduced from v1.0.1 to v1.1.0, almost every line was shifted / indented, so that the GitHub comparison tool is confused and cannot track it.
Accordingly, comparing these two versions is a tedious job.
For the next versions, this will not be a problem and changes will be clearly highlighted, as in the v1.0.0 to v1.0.1 example.

To make life easier for reviewers, we could ask contributors (and offer a bounty?) to read the two charters with the goal to find changes going beyond restructuring / reformatting and highlighting them. Just an idea.

1 Like

I think that if we don’t speak about substantive changes, it’ not an issue.