The proposal can ratify both the amendment (diff) and the full amended version. Noting this since there was no voting to ratify the initial constitution. Doing both in one go is nice.

I think that's a good idea, xaur. It looks to me like the only two areas in need of amending are project governance and funding. LMK if you agree.

Need to check the discussion, but I remember there were some incorrect bits that need to be removed. Pinging @RichardRed0x since he suggested the idea to ratify constitution on Politeia.

Since the proposal will be to amend the constitution document, it will be nice if complete information about the change is recorded in the resilient Politeia file system.

Complete information includes:

1. text of the proposal
2. old constitution doc
3. new constitution doc

This way both old and new constitution are ratified and stored forever in Politeia. In Markdown format, they are very light (a few kilobytes each). The two docs can be diffed to view only the change.

Need to clarify if Politeia allows to attach a second Markdown file.

Whoever picks the writing, I recommend to put pre-proposal (and possible accompanying old and new constitution files) in a gist, and share the link everywhere.

P.S. man I wish nation state laws were handled like this, written in Markdown, stored and versioned in Git! Let's set a decent example.

Good suggestions @xaur .
Markdown attachments are not allowed, only png and txt. Having the old and new versions and diff on Pi is a nice idea though.
The document is such that having markdown in a txt file would probably not be too bad (just some * and ##, no links that really screw with reading markdown as txt).

I agree that that's where the changes are @Dustorf

If there is consensus that what we want for now is an amendment which removes old inaccurate information and adds statements about missing things (like Politeia), I would be up for taking on the role of shepherding this along.

+1 on Richard taking a first crack on this and then we can review and discuss

As txt it would work fine, like any "lightweight markup" markdown is human readable in raw form. The key is that the files will be anchored and stored in a super simple format that can be read on any device. I would suggest some extra restrictions for such files: ASCII-only charset, no BOM, LF line endings.

Thoughts on this as I'm drafting it:

• I did make minor edits to Introduction, Principles and Blockchain Governance.
• Blockchain Governance section could say more about the consensus rules voting procedure, I added one sentence but it could go into much more detail in my opinion, or link to the relevant page.
• The best way to share the new draft is probably opening a WIP PR to dcrdocs, because that will generate a diff that people can see in browsers to follow the changes - it is also a good way to collect feedback.

Edits to the Introduction and Blockchain Governance sections look good! I personally think that we could have less detail in the Blockchain Governance section and link to relevant pages of the docs instead. We also need to think more carefully about the Project Governance and Funding section. What information is necessary to include in each point? How can we present these points in a logical order? All in all, this is a great starting point. Thank you for taking the initiative @RichardRed0x

Updated issue description to include discussions. You can see past versions by clicking "edited..." down arrow.

After this comment I haven't seen much action around the constitution discussion: https://www.reddit.com/r/decred/comments/asnl21/should_we_scrap_the_decred_constitution/egwfo3a

Shall we just open a PR for the latest version and put it up for vote on Politeia?

@noahpierau there is a PR open in dcrdocs and some discussion.

I'm not up to date on all discussions that took place, but in any case I support the idea to update the constitution while trying to minimize the diff. The immediate benefit is a constitution up to date with current state of things and less confusion. Ditching it entirely is a more radical move that should be voted separately.

+1 to post on Politeia, it would push the issue forward. Also, based on feedback new iterations of the draft can be made.

I suggest that first revision of the proposal attaches existing constitution and first draft of its amended version as text files. Any revisions of the proposal should attach updated draft of the amended version. This way all drafts are recorded on Politeia properly and can be diffed.

@lukebp does Politeia handle updates of attached files in proposal revisions? By handle I mean allow to overwrite existing attachment and store both old and new version of the attachment in Git.

does Politeia handle updates of attached files in proposal revisions? By handle I mean allow to overwrite existing attachment and store both old and new version of the attachment in Git.

Yes.

Noticed you didn't use attachments in the proposal @RichardRed0x, were there any problems with them?