News for hackers. Stuff that matters.
Re:Git for US Legislation by dathanb82 on Tuesday October 27, 2026 @11:06PM (#50268866)
That’s like saying that the code in a repo belongs to the whole team once a PR is merged, so it doesn’t make sense to track its provenance back to its original authors.
Re:Git for US Legislation by JumpCrisscross on Tuesday October 27, 2026 @11:13PM (#50268904)
> so it doesn’t make sense to track its provenance back to its original authors

The legislative process is inherently collaborative in a way that's ordinarily undocumented. Who introduced an amendment and who supported it are entirely separate. Someone who introduced language can wind up not supporting it because of where the mix of trade-offs winds up.

At the level of a bill, knowing who wrote language matters. At the level of law, you should only care who voted for it. (I'm not even tackling the inherent subjectivity in tracing e.g. language in the CFR to specific language in a bill.)

Re:Git for US Legislation by blitzar on Wednesday October 28, 2026 @03:53AM (#50270416)
> you should only care who voted for it

even then you have three-line whips and numerous reasons to vote for / against things that are wrapped up in party politics and other stupid games

once something is passed; the intent of the writer, the intent of those that voted for it and the meaning of the words in the final legislation can all be wildly different.

Re:Git for US Legislation by JumpCrisscross on Wednesday October 28, 2026 @03:18PM (#50279363)
There is complexity behind the vote, yes. But the vote is what matters. Who initially introduced text into a bill that did or didn’t pass, with or without their vote, is on the legislative side. That’s a lot more complicated to track than the USC.