zlacker

>>waffle+(OP)
This is a laudable idea.

Unfortunately, the key challenge with the problem isn't architecting a DVCS-like service for legal documents (for an MVP, you could easily get by simply designing a novel frontend to git), it's an adoption problem. The current system is flawed, yes, but merely offering a superior product for less money isn't enough to make a dent in the bureaucratic nightmare of modern-day Washington.

I'm reminded of an article I saw here on HN a few months back: http://www.informationdiet.com/blog/read/dear-internet-its-n...

>>lazerw+A3
Adoption isn't the problem. We don't need Congress to use such a system initially; we need bills, the US Code, etc. mirrored on Github. When it's there, people will get it. The information is out there, it just needs to be processed into a usable form so that it works with Git. And it'd take millions of dollars, and have no conventional ROI, so no one's going to do it.

>>gordia+P4
>And it'd take millions of dollars, and have no conventional ROI, so no one's going to do it.

Your pessimism is unwarranted. There is already one user on GitHub that scrapes the US Code and mirrors it. He even tags the changes so you can diff them quite easily.

https://github.com/divegeek/uscode

>>sc68ca+p9
It also wouldn't have $0 ROI because there are people who will pay for advanced services built around the law-making process.

Here's an example of a service built on Ontario laws (disclosure: I made it): www.ontariomonitor.ca. It emails people when a bill passes a committee or when new laws are introduced (+ lots of other stuff).