search

proftomwbell / Ulex

For version control of Ulex, the open source legal system
Other
79 stars 16 forks source link

Markdown formatting #7

Closed revmischa closed 6 years ago

revmischa commented 6 years ago

Move 1.0 rules into versions by directory Format readme as proper markdown

Ulex rules itself should probably be markdown formatted as well with links to the referenced items.

Where is version 1.1?

proftomwbell commented 6 years ago

Version 1.1 can be found in the Proof-of-Existence version at: https://goo.gl/YByFti.

proftomwbell commented 6 years ago

Rockin'. Thanks, @dmurawsky !

revmischa commented 6 years ago

Idea: the definitive Ulex versions could be kept in github, with the PoE or published "version" number corresponding to the repository commit hash, identified as something like "proftomwbell/Ulex @ 26a31d9c3e07172cb3faac45ea87f9834d4fb08d". The commit hash is a cryptographic hash derived from the git history and represents a particular set of changes at a particular revision, and cannot be altered. Anyone with a clone of the repo can "check out" that commit and see the state of all files in the repo at that point in time.

Adding the blockchain PoE is just kind of duplicating the process. Git already does this. If the history or file contents are changed the hash will differ, and anyone who cares can grab their own clone of the repo and verify the history themselves, easily. More easily than verifying on some blockchain silliness.

proftomwbell commented 6 years ago

@revmischa : Understood that the PoE is (now) redundant. I used that before setting up a Github account.

Still struggling to get the rest of your suggestions implemented, but removing references to PoE should not be hard.