r/programming • • Nov 25 '18

How I changed the law with a GitHub pull request

https://arstechnica.com/tech-policy/2018/11/how-i-changed-the-law-with-a-github-pull-request/
917 Upvotes

147 comments sorted by

246

u/[deleted] Nov 25 '18 edited Nov 26 '18

Having more information about the law accessible in easily-consumed formats seems to be clearly a net good. It strikes me as slightly odd that GitHub is being used largely as a static content store, but no quibble there.

(N.b. by static content store I mean that Git is being used primarily as a file host, with version history incidental, rather than as a collaboration and development tool).

Git seems like an even better fit for bringing transparency to the process of drafting legislation - modeling the process of creating, amending, and reconciling laws as commits and merges, for example, that constituents and researchers and explore either during or after the fact.

I think there's a strong desire for that type of transparency in lawmaking, but it doesn't seem to align with the interests of anyone involved in the actual process.

102

u/ZeeBeeblebrox Nov 26 '18

modeling the process of creating, amending, and reconciling laws as commits and merge

Since I doubt any government is likely to switch to such a process, I think it would be a cool idea for someone to encode the current procedures in this way. It would be really nice to be able to git blame sections of passed laws to see who made the edits. I think that already would be a huge boon to transparency as it would make it easier for people to track changes and perhaps correlate them to campaign contributions and lobbying efforts.

39

u/[deleted] Nov 26 '18

That'd be awesome. Not just seeing the name of the clerk or whoever writes the stuff down, but the actual legislator who introduced it and who voted for it, etc.

16

u/_unicorn_irl Nov 26 '18

That feeling when you forgot to git pull before voting and now you've passed a pork monstrosity and your constituents hate you.

23

u/vale_fallacia Nov 26 '18
git push failed: remote repository said:
"Conflicts with 1st amendment"

10

u/[deleted] Nov 26 '18

oh, you just need to add the --force and you're good.

0

u/jyper Nov 26 '18

Pork is good it drives compromise

1

u/eiffel31 Nov 26 '18

Someone did a prototype for part of French law (in French): https://github.com/steeve/france.code-civil

-1

u/hyphenomicon Nov 26 '18

I don't know that this would be an unmitigated good or even be very likely to be a net good. It seems like it would allow for more direct targeting of lobbying efforts, more influence of populists, and more graft for local constituents.

42

u/ZeeBeeblebrox Nov 26 '18

Hmm, I think one of the main problems we have these days is information asymmetry. A lobbying firm already has the funds to do this kind of thing, while the average journalist or constituent does not, so I personally don't see how it would make things worse.

4

u/ryuzaki49 Nov 26 '18

Imagine ammendents inside a pull request with comments and law reviews

3

u/GrandAdmiralDan Nov 26 '18

It's all fun and games until someone goes to jail because of a botched merge conflict resolution.

6

u/neelsg Nov 26 '18

Just because the process right now is not assisted by some VCS software does not mean we don't have these same issues hapenning already. It isn't transparent, so you most likely just don't know about it

1

u/GrandAdmiralDan Nov 26 '18

No argument there. Still an amusing thought.

1

u/jyper Nov 26 '18

It's called the judicial system

-1

u/shevegen Nov 26 '18

I think there's a strong desire for that type of transparency in lawmaking,

Transparency for public law through private entities?

You US folks are very strange people.

6

u/[deleted] Nov 26 '18

He's referring to Git (the version control system that's open source), not GitLab

2

u/[deleted] Nov 26 '18

It doesn't have to be private entity. But at the same time, why it couldn't be private entity?

0

u/[deleted] Nov 26 '18

[deleted]

3

u/shevegen Nov 26 '18

This is true. But I do not think this is the point that is being contended here.

-10

u/aurisor Nov 26 '18

In web dev "static content" usually refers to literal html, images or text, as opposed to content that's generated at runtime (e.g. API outputs).

12

u/BKrenz Nov 26 '18

I'm not sure how what you're saying is relevant?

2

u/aurisor Nov 26 '18

As others pointed out, people are misreading op and thinking he means “unchanging” when that term has a specific meaning in a certain context.

I’m not sure why people are downvoting me, it’s clearly what he means, and here’s an entire page using the term just as he does: https://www.maxcdn.com/one/visual-glossary/static-content/

1

u/BKrenz Nov 26 '18

We're not do much arguing that the content is or isn't static, just that it doesn't really have much to do with Web Dev specifically.

1

u/aurisor Nov 26 '18

What? I'm saying /u/harpagos called the laws "static content" because that's what web devs call piles of html in vcs *because he's a web dev not because it's never going to change*

Go look in his post history he's clearly a web dev

I don't understand why I'm getting downvoted for pointing out a difference in terminology that's really clearly the source of the confusion here.

1

u/[deleted] Nov 26 '18 edited Apr 24 '24

Comment redacted to prevent LLM training.

1

u/aurisor Nov 26 '18

I got u fam ❤️

5

u/alreadyburnt Nov 26 '18

Because u/isUsername misunderstood the context in which u/harpagos used the phrase 'static content store.'

13

u/BKrenz Nov 26 '18

What we are discussing has nothing to do with web development specifically. To quote u/harpagos:

It strikes me as slightly odd that GitHub is being used largely as a static content store

He's referring to the content checked into Git being static - that is, the documents related to the law, I would think. He (incorrectly, one would think) made the assumption those would be static in nature. u/isUsername pointed that out, noting that laws change overtime, and as such, the features of Git would make it easy to see what has changed, when it changed, and who changed it - much like we do with code.

I've certainly read of authors of books using Git(hub) for their work. The technology may certainly have been developed for programming, be used primarily by programmers, but it's also just a great concept that would have great applications in other fields. Wherever you're making changes to something over time, and would like to track those changes, the concept of version control is just great.

1

u/[deleted] Nov 26 '18 edited Apr 24 '24

Comment redacted to prevent LLM training.

1

u/_unicorn_irl Nov 26 '18

I agree with you - either usage of static is wrong. The law is not static because it changes. If they were using the term 'static' in the sense of static vs dynamic markup, that would not be an argument against using github. Tons of programmers use github to store static content, like javascript and html files, because those files change and we need a history and change management process for them. To say that you shouldn't use git/github for something unless it relies on a database doesn't make sense.

-5

u/nerdyhandle Nov 26 '18

We still store HTML pages in git. HTML isn't static.

Images, PDFs, word documents, etc. are what I as a developer would consider static. I usually avoid storing these in Git. Git in the past didn't handle these efficiently. However, Git now supports LFS. So storing these documents today in Git is fine. Although Git will not show the difference between the revisions.

9

u/primitiveType Nov 26 '18

Maybe I'm forgetting something obvious but how is html not static?

0

u/aurisor Nov 26 '18

This was my whole point. Static usually means “unchanging” but “static content” has a specific meaning. Check this page for an example https://www.maxcdn.com/one/visual-glossary/static-content/

148

u/[deleted] Nov 25 '18

It's an interesting idea but "changed the law" in this case was a PR to fix a typo in a citation.

79

u/[deleted] Nov 26 '18

Yeah it’s not exactly like they’re proposing new laws through PRs and accepting them based on the ratio of smily to confused faces, which is what I was hoping for

6

u/VeganBigMac Nov 26 '18

Spend any time in a slack channel for any political organizing group and using emoji's to vote gets old real fast.

13

u/[deleted] Nov 26 '18

We do that! Well, OK, not real laws, but a manifesto, which is at least similar! https://openpolitics.org.uk

6

u/EmersonEXE Nov 26 '18

This is awesome. Has any part of the manifesto been adopted to law yet?

2

u/mcgruntman Nov 26 '18

No, it's a fringe movement.

1

u/[deleted] Nov 26 '18

I prefer "startup" :D

1

u/mcgruntman Nov 26 '18

It wasn't meant insultingly. I've heard of the project before and love it, on paper. Fat chance of it having a major impact on policy any time soon though.

1

u/[deleted] Nov 26 '18

Oh I didn’t take it as an insult, don’t worry, I’m very impressed you’ve heard of it! I quite agree that major impact is a long way off, especially as I have about zero time to work on it at the moment :(

1

u/[deleted] Nov 26 '18

Hah, no, though some of the things in it are now law completely coincidentally. We have had a number of candidates run for office on it though, to try it out: see https://somethingnew.org.uk

1

u/MINIMAN10001 Nov 26 '18

Reminds me of chaos bot which initially had up and down thumbs for voting, they added a bunch more emotes as votes. Last I checked they are a meritocracy because of problems with cheating the system. So one of the top 10 contributors must approve on top of the Democratic vote.

20

u/improbablywronghere Nov 26 '18

I enjoyed the article for the broader story about government adopting awesome version control products (like github), and how useful that can be. The actual plot of the article was secondary.

4

u/VeganBigMac Nov 26 '18

I feel like that was an acceptable level of clickbait as it was true in a broader sense.

4

u/BillyBBone Nov 26 '18

Aren't they the same thing? If a law says that you have 9 days to do something because someone accidentally typed 9 instead of 90 in an authoritative document, doesn't that make the "9 days" version the enforceable one?

The author states:

This isn’t a copy of the DC law. It is an authoritative source.

I don't know what "an" authoritative source is versus "the" authoritative source, but when you change that document, aren't you effectively changing what judges and lawyers use to adjudicate?

2

u/seamsay Nov 26 '18

In this particular case, no I don't think so. As I understand it they essentially fixed a link that was pointing to the wrong place, I don't think they actually changed the text of the law itself.

1

u/improbablywronghere Nov 26 '18

Also, I’m almost positive if In the case of a typo based situation the judge will be able to interpret that law to the best of their ability. That is to say nobody going to jail or not off a typo.

199

u/banger_180 Nov 25 '18

I like git being used for this, but feel like github should not be the authorative source. They should have some more secure self hosted service.

123

u/Mischala Nov 26 '18

I don't see how a self-hosted publicly accessible solution will be more secure than using GitHub.
If anything, allowing GitHub to deal with the security aspect, something they do for countless repos, and thousands of private, corporate codebases is preferable to allowing the governments lowest bidding contractor to do it.

Then again, I have never worked in government, it's possible their cybersecurity contractors are much better than GitHub's inhouse team, with less on their plate.

103

u/musketeer925 Nov 26 '18

I feel like the concern is not the competency of Github's security team, but rather that the authoritative source of the law is controlled by a non-public third party.

63

u/meneldal2 Nov 26 '18

But they have their own local repo, so they can check if Github tries to rewrite history easily. As can anyone else who downloaded the repo before Github would have done anything to it.

You don't need to trust your provider for it to work.

13

u/MertsA Nov 26 '18

Yes but then GitHub isn't really the authoritative source then is it?

0

u/meneldal2 Nov 27 '18

For the layman it is, I'm just talking about trust but verify here.

1

u/MertsA Nov 27 '18

For a layman it's a source but if it's not the end all, be all source then it's not the authoritative source. If a GitHub employee decided that they wanted to change the law and manually approved their own pull request it's not like that would meaningfully change the law. Someone following the vandalised copy of it also would still be breaking the law regardless of what that git repo says. I'm not saying it's not a valid source, I'm just saying that it's not an authoritative source given that it doesn't have any real authority and shouldn't have any real authority.

0

u/meneldal2 Nov 27 '18

You can sign the commits though, so it's easy to know which is the last "valid" commit (signed by the government in question).

1

u/MertsA Nov 27 '18

I don't think you're getting this. If it's not authoritative without being signed by some other entity then it's not authoritative.

0

u/meneldal2 Nov 27 '18

You want some kind of signing, that's also why you use HTTPS. You can't trust anything without some certificate to prove that what you are seeing is the truth.

→ More replies (0)

-6

u/svick Nov 26 '18

That's assuming SHA-1 is secure, which it isn't.

38

u/meneldal2 Nov 26 '18

You can create collisions with SHA-1 indeed, but can you hide them well enough that it doesn't look suspicious? A random string added to your file is going to be quite obvious.

2

u/ThisIs_MyName Nov 26 '18

Do you really think a gov't agency will ensure that all files in the repo are plaintext? They'll check in PDFs without a second thought.

6

u/ten24 Nov 26 '18

Well so far a total of one government has their law posted to GitHub, and they didn't do that. But I'm sure you read the article already.

-2

u/meneldal2 Nov 26 '18

Only formats that make sense are some kind of xml, markdown, or TeX-like open formatting system. It's easy to compare files for changes and doesn't require too much skill to write stuff that stays in the same pattern (like laws tend to do).

Posting pdfs is very much impractical because you can't change them easily. Word files would be a bit better possibly but you need to unzip it for the diff and have people use word cleanly, and then you might as well use xml directly instead.

6

u/ten24 Nov 26 '18

Which is probably why DC used XML and not PDF, DOCX, GIF or WAV.

→ More replies (0)

-1

u/shevegen Nov 26 '18

Better to act early than late when all government departments are a shell of Microsoft.

3

u/binford2k Nov 26 '18

It's XML. Did you read the article or look at the repo?

0

u/[deleted] Nov 26 '18

[deleted]

1

u/ThisIs_MyName Nov 26 '18

Does this repo have such a webhook? It's not just PDFs, it's any high-entropy file.

1

u/svick Nov 26 '18

What if it's a random string added to the commit object?

Also, adding a random string to a file is the attack that exists now. Maybe there will be less conspicuous attacks in 5 years.

0

u/6501 Nov 26 '18

Are you proposing that we change something right now to prevent a theoretical attack that doesn't even exist yet?

2

u/svick Nov 26 '18

For something as important as the authoritative source of law? Yes. We already know that SHA-1 is weak. And it's possible that either someone has developed a different attack in secret, or will do so in the future, especially if it would give them the ability to change the law.

We already don't consider SHA-1 as secure enough to protect web browsing. Are you saying law is less important than that?

1

u/6501 Nov 26 '18

Correct me if I'm wrong, but won't a SHA1 exploit require write access to the repo? Also the people who generally have the means to develop these attacks won't risk its exposure messing with the municipal code of DC.

→ More replies (0)

1

u/mayhempk1 Nov 26 '18

It's secure enough for checksumming differences of files.

-1

u/mghoffmann Nov 26 '18

This sounds like a blockchain, but with only 2 authoritative nodes.

-6

u/shevegen Nov 26 '18

Then they should use precisely that repo - and let people access it.

But I think you are actually wrong because IF this were possible, they would do so - instead they are being lazy and now depend on Microsoft. Well done! </irony>

5

u/binford2k Nov 26 '18

That's not how distributed version control works. There is no practical way for anyone to change the github repository without the owners knowing almost immediately.

23

u/[deleted] Nov 26 '18

The source would be stored at github, not controlled by them. And obviously the intent is to run a renderer on this set of XML docs to produce a consumable version which is the definitive version to be hosted on a local government website or or distributed as PDF or similar. As already noted below, the maintainer would know if Github or someone with access to Github tried to manipulate the repo since the next push or pull would mismatch.

The person who suggested SHA1 collisions as an avenue of attack is a tin foil hat wearer. If someone wants to attack your git repo that bad, it's easier to social engineer yourself access to the maintainer's repo than it is to coordinate and deploy an SHA1 attack on the github repo. In that case, the fact that the repo is pushed to github is irrelevant - they are little more than remote storage for the already attacked maintainer's repo.

We're talking about a set of plain text documents here with an authoritative local and remote repo (and potentially hundreds or thousands of copies). A modification will be noticed, no matter how trivial. In fact, opening up the source on github allows public review of what might otherwise be shielded from the eyes of those who would seek to keep the system in check.

Those of you suggesting this is some how a major security issue either misunderstand security completely or are blowing things way out of proportion for sole purpose of playing devil's advocate.

-1

u/shevegen Nov 26 '18

The source would be stored at github, not controlled by them.

That is nitpicking.

Of course Microsoft can control access to any data hosted at github. How much can you do without having an account at MS GitHub? Not much at all. Why would a public site require access to a private commercial entity?

4

u/[deleted] Nov 26 '18

It seems like you aren't sure how git functions. Read up on it try again.

1

u/6501 Nov 26 '18

Github uses git as its protocol, to my knowledge you don't have to have a github account to do basic actions such as viewing & forking/downloading a repo

3

u/shagieIsMe Nov 26 '18

Compared to... something like this?

2

u/vgf89 Nov 26 '18

In case anyone's wondering what happened to that, Malamud appealed that decision and won back in October, so happy ending for all https://www.eff.org/deeplinks/2018/10/appeals-court-tells-georgia-state-code-cant-be-copyrighted

0

u/shevegen Nov 26 '18

That is pretty stupid - the law is public, so code that governs it or changes to it should be public as well. Which, by the way, has a problem in this case here since a private entity is put as a man-in-the-middle.

1

u/test6554 Nov 26 '18

It would be better if if they have a contract in place to ensure rouge employees don't have unrestricted access to make alterations.

1

u/port53 Nov 26 '18

Contracts don't stop anything, they just provide a remedy for after it happened.

39

u/earthboundkid Nov 26 '18

Then again, I have never worked in government, it's possible their cybersecurity contractors are much better than GitHub's inhouse team, with less on their plate.

They aren’t.

Source: I worked with the government.

24

u/DuroSoft Nov 26 '18

Gov IT and R&D is basically a circa-2007 (technology wise) dumpster fire, and this is 2018.

Source: I have worked with the DoD

0

u/[deleted] Nov 26 '18

[deleted]

3

u/[deleted] Nov 26 '18

You shouldn't talk about Cyber Command like that. DISA might be watching.

6

u/ex_nihilo Nov 26 '18

They’re absolutely watching. But if they want to do anything useful with the data they will call me, since I wrote most of the software they are using to do it. :D

6

u/nemec Nov 26 '18
if target == "ex_nihilio":
    break

1

u/TerrorBite Nov 26 '18

> visit internal https site
> self-signed certificate

8

u/msluther Nov 26 '18

This has been my experience in general: “I’ll go work at X, surely they know what they’re doing.” Nope. A person is smart, groups are dumb. Even on teams with a really specific goal, outside forces, differences of opinion, etc will always get in the way. I think if you’re lucky you can end up on a team that jives really well and is amazing, but it never lasts more than a year or two before it starts changing.

0

u/[deleted] Nov 26 '18

[deleted]

9

u/waldoj Nov 26 '18

We have some excellent security folks at 18F, but our entire staff is something like 250 people, of which just a handful are security experts. But the D.C. Council is not among our clients. :) AFAIK, they have no security expert on staff, and they do well to punt to GitHub here.

That said, GitHub is the authoritative digital source for Washington DC's laws. Nearly every state has an authoritative print source that trumps their digital source, procedurally.

5

u/earthboundkid Nov 26 '18

18F is good but a very small team. Ditto USDS.

3

u/mpyne Nov 26 '18

Then again, I have never worked in government, it's possible their cybersecurity contractors are much better than GitHub's inhouse team, with less on their plate

This is absolutely not the case, unfortunately.

-3

u/shevegen Nov 26 '18

It is not "publicly accessible". You need an account to do much at all there. And the Microsoft GitHub page could disappear at any moment in time.

I think this is truly awful of that government department to not care about this. They channel people through corporate sites in order to then access public areas (law == public).

1

u/6501 Nov 26 '18

The version they have on github is then parsed through their own government run website, which you would know if you had read the fucking article.

Also its laughable that you believe that Github would just vanish in a day, on nearly any scenario that would result in the CEO of Microsoft being fired.

48

u/DuroSoft Nov 26 '18

git is already by nature distributed as each person who uses a repo has a local copy. I agree that this looks bad, but the badness is overhyped. We could waste time doing some crazy distributed blockchain thing, but at the end of the day it's going to be pretty obvious if github tries to change the commit tree and all of a sudden your master doesn't align with github's master.

24

u/[deleted] Nov 26 '18

I don't think anyone's advocating for blockchain, maybe a gitlab.dc.gov

3

u/DuroSoft Nov 26 '18

A few were if you read some other comments

1

u/Decency Nov 26 '18

Eh, it's distributed by nature and that's nice but that doesn't really fly when you're trying to enforce the law...

"Oh well it was legal in my repo at the time."

3

u/ChaseMoskal Nov 26 '18

it's not like local copies of law books are any more up to date when they are printed on paper

nobody would be looking at outdated local copies of a law repository, they would look at the current-up-to-date copy from github directly, even in realtime -- it's not a problem

laws should be written in markdown

0

u/shevegen Nov 26 '18

But the issue is not git here - the issue is GitHub owned by Microsoft + account registration AT GitHub.

1

u/DuroSoft Nov 26 '18 edited Nov 26 '18

I think you might be missing the point of my comment. The point is that because GitHub uses git, the fears regarding centralization are overblown as the very nature of git largely mitigates these fears. If microsoft/github decided to change the commit history, it would become immediately obvious as no one's local master branch would be compatible with remote master, and the primary maintainers would cry foul. You can't make a change without changing an existing hash or creating a new commit, both of which would be impossible to ignore.

-77

u/GitCommandBot Nov 26 '18
git: 'is' is not a git command. See 'git --help'.

35

u/[deleted] Nov 26 '18

bad bot

11

u/errer Nov 26 '18

That depends on what your definition of is is.

1

u/sysop073 Nov 26 '18

The bot isn't even unintentionally stupid -- this is the only kind of comment it posts, even if the command is valid. What jackass comes up with a pure spambot like this

1

u/mrnate91 Nov 26 '18

git add .

4

u/[deleted] Nov 26 '18

You could sign it, no?

2

u/combuchan Nov 26 '18

The Municipal Code Corporation and American Legal Publishing do make authoritative sources of local laws like at municode.com and amlegal.com. They're used by cities all over the US big and small.

There's nothing special about them that's any better than github, in fact, I'd say github is more secure given that it's a high-value target that's regularly attacked and we're still safe with them.

/u/musketeer925

1

u/shim__ Nov 26 '18

They should allow only signed commits

-11

u/wung Nov 25 '18

Maybe we can put it in some kind of git based blockchain of some sorts :thinking:

30

u/shizzy0 Nov 26 '18

Git is a blockchain. Err, well, actually it's a Merkle Tree, which in the degenerate case is a blockchain. But it has the same anti-tampering properties as a blockchain. It's just its consensus mechanism isn't based on Proof of Work; it's based on authoritative acceptance, i.e., each repository holder is their own authority that chooses whether to accept new commits.

0

u/[deleted] Nov 26 '18

[deleted]

14

u/TerrorBite Nov 26 '18

If you want to get technical, a blockchain is a Merkle tree which has only one valid branch (selected by consensus). A Git repository is also a Merkle tree, but obviously branches are a desired feature. Just like in a blockchain used for cryptocurrency, in Git each commit (block) has a hash, and also contains the hash of its parent (or parents; unlike a blockchain, a commit may have two parents, in the case of a merge commit). Thus no commit can be modified without invalidating it and everything that follows it.

Ergo, Git is a form of decentralized branching blockchain (a blocktree, if you will); and has been for years.

"Blockchain", i.e. the implementation as used in cryptocurrency (including proof-of-work), may indeed be a stupid, broken idea that won't work in any other scenario, but the core concepts can be applied to other scenarios, as Git proves.

4

u/ex_nihilo Nov 26 '18

It's more of a directed acyclic graph than a merkle tree in practice. Though of course a git repo is a literal merkle tree, in practice the merkle tree forms a DAG. Even though you can traverse a branch in either direction, every branch maintains a canonical HEAD, or furthest legitimate leaf node from the merkle root. But you're never using the merkle tree feature as such because the tree is known before traversal for every operation you could conceivably want to perform. I might be thinking about this wrong, though.

1

u/CAPSLOCK_USERNAME Nov 26 '18

Well yes, Git works, but Git is far older than bitcoin anyways. The things that are broken about blockchains are the things that are new and different about them, in particular the concept of getting consensus from anonymous strangers competing to create blocks -- this only works when there's an economic incentive for them to waste electricity and time (and thus money) brute-forcing the hash, i.e. when they will get cryptocurrency out of it. Every single "blockchain as a business/government/etc database" proposal seems to either conveniently ignore this problem or "solve" it by cutting out the anonymous masses and having a small set of trusted permissioned miners. This gives up the only good point of a blockchain (decentralization and trustlessness) and turns it into just a slow-and-expensive database run by a central trusted authority.

-3

u/shevegen Nov 26 '18

Yeah - next step is to let Microsoft draw the laws there.

1

u/6501 Nov 26 '18

I want to know the logical leap that you took to get from the article to your boneheaded conclusion

12

u/HowIsntBabbyFormed Nov 26 '18 edited Nov 26 '18

I had the idea for using source control to track changes to rules/laws back in 2002-ish. I used a diff to present a proposed rule change to a school club's bylaws.

It just makes so much sense to have every law passed be an actual diff to an existing repository of text that represents the existing laws of the land.

One thing that confuses me about passing laws is if the bill passed stands on its own as it's own law (or laws) or if it always amends an existing document that has all the laws or if it's just added to the end of a growing list of laws.

Like, if I wanted to make whistling a crime, does my bill just say, "Whistling is illegal." Or does it say, "Section 20 of article B of chapter VI is amended by adding 'whistling' to the list of illegal annoying actions."

In which case, what is a law? Is it "section 20 of article B of chapter VI"? Is it the bill that amends that section? Is it the line item of whistling now on that list? What if my bill removes an item from the list, is the bill still a law?

The amendments to the Constitution seem to both stand on their own: you have to read the entire Constitution and all amendments to understand the supreme law of the land; and they sometimes amend the text of the original Constitution itself: you'd only have to read the (altered) Constitution itself to understand the law.

2

u/6501 Nov 26 '18

They can do both, if they are stand alone someone else will later codify it into the format we are used to seeing

1

u/HowIsntBabbyFormed Nov 26 '18

When does that process happen? And by what body? Isn't there risk that in the process of integrating a standalone law into an overall set of laws that the text/meaning might change slightly?

2

u/6501 Nov 26 '18

You generally codify a law so that it is one cohesive set of laws. I think in the US on a federal level the GPO/Federal Register might codify our laws. I cannot answer your other question without more research on the matter.

2

u/6501 Nov 26 '18

Office of the Law Revision Counsel is the US body that does the codification

1

u/HowIsntBabbyFormed Nov 26 '18

Interesting. From wikipedia, it says this counsel consolidates the laws:

with such amendments and corrections as will remove ambiguities, contradictions, and other imperfections both of substance and of form

So, a fair amount of editing is required. All editing ends up changing the original meaning, no matter how careful or how unbiased the editor is. Sometimes the change in meaning is explicitly desired, as in "removing contradictions". But to remove a contradiction, the editor has to decide which interpretation is "correct".

I wonder if there are ever political wranglings over this counsel and they way they resolve ambiguities and contradictions.

2

u/6501 Nov 26 '18

I haven't heard of any such wranglings over the office, I would assume that the office has been traditionally nonpartisan.

1

u/HowIsntBabbyFormed Nov 26 '18

This kind of addresses what I was wondering:

By law, those titles of the United States Code that have not been enacted into positive law are "prima facie evidence" of the law in effect. The United States Statutes at Large remains the ultimate authority. If a dispute arises as to the accuracy or completeness of the codification of an unenacted title, the courts will turn to the language in the United States Statutes at Large. In case of a conflict between the text of the Statutes at Large and the text of a provision of the United States Code that has not been enacted as positive law, the text of the Statutes at Large takes precedence.

(the "Statutes at Large" being the exact text of bills passed by Congress).

I guess Congress sometimes passes legislation that specifically references sections of the Code and how it should be amended, and sometimes passes a general law that the Counsel has to figure out how to fit into the Code (possibly modifying several different sections). And sometimes an act of Congress something like "section xyz of the code is the law", removing any potential conflict between the Code and the previous statutes that had to be interpreted to make that section.

I'd propose a system where the prefered form of legislation was essentially a diff to the existing Code. General laws that aren't in the form of a diff could still be passed. They'd still be the law of the land, and they'd be codified by the Counsel. But the next Congress would have to vote to confirm the official "diff version" produced by the Counsel or it would be automatically repealed. This "confirmation" vote would have a much lower threshold to pass, like 1/3, and it would only be an up-or-down vote on the text produced by the Counsel (the next Congress couldn't sneak in an entirely different version).

1

u/6501 Nov 26 '18

Most bills already modify the USC so I believe that the git diff system to be redundant with our existing safeguards such as the courts.

1

u/HowIsntBabbyFormed Nov 26 '18

It's not really about safeguards though. If laws were hosted through a public repository with a well defined protocol for modifying them, it would be much easier for anyone to be able to submit proposed changes.

Think about an open source project that doesn't have a public source code repo. They have source tarballs available via physical CD-ROM for users who send in a request via USPS with self-addressed stamped return envelope. They technically can accept patches, but have no publicly published method for doing so. There's also no guarantee they'll even see your patch.

With a public repo like git with github or gitlab, it's way more open and collaborative and easy for others to contribute with a pull/merge request.

1

u/6501 Nov 26 '18

But those changes would have to be approved by the Council or Congress. The current reason we have git to do this is so we can track the legislative history & the people who changed a documents etc

→ More replies (0)

44

u/lutusp Nov 26 '18

How I changed the law with a GitHub pull request

Only someone who understands law and legislation can see how misleading this is. Clerks don't change laws, elected officials do. If someone actually changed a law in the course of fixing a clerical error, the change would have to be vetted by elected officials and by the public.

The problem is with the phrase "changed the law". The law cannot have been changed in any material sense.

43

u/EdgeOfDreams Nov 26 '18

It is a misleading title, but the article itself goes on to explain in detail what you just said.

0

u/lutusp Nov 26 '18

So the title is clickbait, all too often seen above what might be a worthwhile article.

1

u/amunak Nov 26 '18

Well technically they "changed the [text of the] law". I wouldn't say that's really misleading. They just didn't change the meaning of the law.

1

u/lutusp Nov 26 '18

Well technically they "changed the [text of the] law". I wouldn't say that's really misleading

Of course it is. Changing how something is described doesn't change the thing itself.

They just didn't change the meaning of the law.

Imagine if the title has been "I changed the law ... but I didn't change what the law means."

13

u/trenobus Nov 26 '18

I see lots of parallels between software and laws. Both are trying to encode an intent using a language. Both are subject to interpretation: software by a computer, law by a court. Both have a tendency toward brittleness, and both often require corrections after the initial implementation. In some sense, when courts establish precedents on how a law is interpreted, they are acting as a sort of QA organization for laws.

Wouldn't it be great if we (or our lawyers) could file bug reports on laws, and have some way to expedite resolutions, either by a court ruling, or through some streamlined mechanism for bringing a vote on a fix before the legislature?

2

u/Adverpol Nov 26 '18

Wow, this is an awesome idea! Forwarded it to a local political party.

And it's also one step closer to us programmers finally taking over the world of course.

1

u/Pella86 Nov 26 '18

I m doing a social experiment. I love github ability to track edits and to compare text. It is not only useful in a strict programming sense so i funded a religion based on github. I know the idea sounds weird but i hope it will serve as a platform to exchange ideas and ethical conundrums. This said, im the only follower and also my only religious chief, im not looking into expanding my reach, i just would like people to found their own religion and compare it.

https://github.com/Pella86/Schrodinger-religion/blob/master/The%20religion.md

1

u/HALtheWise Nov 26 '18

My school's student government constitution and bylaws are stored in Github, to enable these sorts of behaviors. Feel free to fork them if you want to start your own student government :)

https://github.com/olin/studentgovernment

-8

u/shevegen Nov 26 '18

The District does something with its legal code that no other jurisdiction in the world does (to my knowledge): it publishes the law on GitHub. GitHub is a website used primarily by software developers to share and collaborate on software code.

This is quite bad. Why? Because Microsoft runs GitHub.

I do not think that the public law should operate on private websites. That also defeats the whole point of git.

6

u/ChaseMoskal Nov 26 '18

git is way ahead of you with this concern, from its conception

git is brilliant because nobody (even github) can tamper with a repo's information without exposing themselves -- it's impossible for github to tamper with a git repository they host and get away with it

this is because washington legislators can keep a true master copy on their own secure machines, and use it to keep github honest -- github merely mirrors/distributes copies to the public, and collects and organizes pull requests (changes)

linux works this way, the true master copy is kept by linus torvalds because he doesn't trust github, but he still uses github to distribute the sourcecode to the public

-7

u/GitCommandBot Nov 26 '18
git: 'is' is not a git command. See 'git --help'.

-4

u/[deleted] Nov 26 '18

Microsoft controls the law now