Hacker News (curated)new | past | comments | ask | show | jobs| show hidden

The Hacker News Community (hah) needs to lobby hard to pass a law (what boostrapping!) to require the https://en.wikipedia.org/wiki/Office_of_the_Law_Revision_Cou... to maintain the repo as part of their duties, and do it retroactively for the entire history of the US Code.

It's a simple idea; it's cheap; there are no outstanding technical questions; it benefits almost everyone. Let's get this done.



> The Hacker News Community

*from the US. Please remember that the Hacker News community is not limited to this single country.


Y Combinator is based in the US.

Which has no relevance to how the HN community has grown.

It definitely does...

don't be jealous

What do you see the value? What would this add? All of the data is currently available? What am I missing?

Did you read the linked piece?

The data is "there" in some some sense, but it is messy, coarse-grained, and arrives slowly.

Once the office is familiar with Git, we can start the conversation about having the new version of the US code instantly ready when a bill is passed. In particular, rather than voting on the informal patch, congress should vote on the final result. (bills are patches, but votes should be on the new state with the patch applied.) Then the office merely supervises the Git repo, and is freed up to focus on other codification tasks, such as hyperlinking definitions, overseeing formalization of the tax code like France did, etc.

Previous discussions often foolishly conflate version control with "no force pushing of any branch" and "all branches must be public". That is stupid. Vote trading will continue to make drafting happen in secret, since it is simple game theory that an "atomic transaction" of many possibly-unrelated things is an efficacious coordination mechanism. This is just about getting the final version and its already-public history cleaned up and mechanized to the greatest degree possible.


why not just do it?

Because I have want my government to use the right tool for the job.

I don't want to privatize this core civic function to some NGO.


It sounds lazy tbh. No one said privatize. It can be open source can't it?

It's easy and fun for volunteers to put in the effort once. It's doing the work on an ongoing basis that is less fun and less motivating. The ongoing work --- done without modern tools --- is already that office's responsibility, so this should be too.

> it benefits almost everyone

I want to see a practical benefit to maintaining this with public funds versus the usual redlines.


>> The Hacker News Community (hah) needs to lobby hard to pass a law (what boostrapping!) to require the https://en.wikipedia.org/wiki/Office_of_the_Law_Revision_Cou... to maintain the repo as part of their duties, and do it retroactively for the entire history of the US Code.

> I want to see a practical benefit to maintaining this with public funds versus the usual redlines.

The US government works for the people and, as such, changes made to the US Code over time must be traceable, discoverable, and therefore justifiable by or condemnable to those who are responsible for said changes without fear or favor.

That is as practical as it gets.


> changes made to the US Code over time must be traceable, discoverable

They are. The history of the USC is public. This is one way of visualizing it. It’s good. But I want to see the advantage of this presentation.





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact | github