News for hackers. Stuff that matters.
Re:US Constitution – A Git repo with history of edits by cobbzilla on Thursday October 24, 2019 @09:24AM (#21344435)
US Federal law works just like this but with an awful manual process that is screaming for a VCS:

- Laws are passed by Congress and signed by the President.

- The actual formal text of the law is printed in the “US Statues at Large”. Think of this like a commit log— it’s written as a series of add/modify/remove operations to the United States Code (USC), which represents the “master” branch of the repo; our current laws.

- Sometimes the add/edit/remove operations have implications in many parts of the code. There is a manually-intensive process that actually determines which parts of the USC must be modified and how. This is like code review on a PR.

- Periodically, after many laws are passed and many mods to the USC, it is “republished” (tag/release).

Why we couldn’t do this with our laws is beyond me. Institutional inertia I suppose.

Re:US Constitution – A Git repo with history of edits by C1sc0cat on Thursday October 24, 2019 @12:48PM (#21346391)
Exactly parliamentary procedure was using content control well before computers where invented read Citrine or Roberts Rules.

But Executive's do get up to "naughty shit!" as a Uk Party Whip said to me once in a bar.