3 ms·

Washington DC's laws are in git. https://arstechnica.com/tech-policy/2018/11/how-i-changed-the-law-with-a-github-pull-request/ https://arstechnica.com/tech-pol

by Terr_ 2y ago

Washington DC's laws are in git. https://arstechnica.com/tech-policy/2018/11/how-i-changed-the-law-with-a-github-pull-request/ https://arstechnica.com/tech-policy/2018/11/how-i-changed-th...

jbaber 2y ago
This is wonderful.
CivBase 2y ago
More of this please.
neuronexmachina 2y ago
Direct link to the repo for DC's laws: https://github.com/DCCouncil/law-xml https://github.com/DCCouncil/law-xml
KennyBlanken 2y ago
Github, not "git." They don't appear to publish the XML formats they're using. There's no description of their fees/pricing. None of the software is open-source. There's barely any details about how the software even works. It's about as opaque as they seem to feel they can get away with. "Email us for pricing" is not how a service like that should work.
- Terr_ 2y ago
  > Github, not "git." No, I stand by my original phrasing: The important part here is that legislative changes are being recorded and shown through a version control system (i.e. git) not the fact that one of the repos is publicly visible via one of several possible web-GUI services. It would still be somewhat laudable even if the usage was: "Here's the repo, clone it yourself an poke around with desktop tools." In contrast, the opposite mix of "here's a website that shows diffs but you can't have the underlying data" would suck. > They don't appear to publish the XML formats they're using. I see XSD files...? Plus, this original design doc is probably still relevant. [0] [0] https://github.com/DCCouncil/dc-code-prototype?tab=readme-ov-file#dc-code-xml https://github.com/DCCouncil/dc-code-prototype?tab=readme-ov...
joshdata 2y ago
Hi. Author of that article here, and I worked with the DC Council to get the initial prototype going, if anyone has any questions. What's important in the story is that the law went from being not open to open and the law-publication-process was modernized internally. The fact that it ended up on GitHub was the least important, but most fun, outcome. GitHub adds nothing of any value for the transparency and accountability of the lawmaking process (I mean, what lawmakers do), but it is a great platform for publishing structured data files for the law to create open access.

by Terr_ 2y ago

Washington DC's laws are in git. https://arstechnica.com/tech-policy/2018/11/how-i-changed-the-law-with-a-github-pull-request/ https://arstechnica.com/tech-policy/2018/11/how-i-changed-th...

jbaber 2y ago

This is wonderful.

CivBase 2y ago

More of this please.

neuronexmachina 2y ago

Direct link to the repo for DC's laws: https://github.com/DCCouncil/law-xml https://github.com/DCCouncil/law-xml

KennyBlanken 2y ago

Github, not "git." They don't appear to publish the XML formats they're using. There's no description of their fees/pricing. None of the software is open-source. There's barely any details about how the software even works. It's about as opaque as they seem to feel they can get away with. "Email us for pricing" is not how a service like that should work.

Terr_ 2y ago
> Github, not "git." No, I stand by my original phrasing: The important part here is that legislative changes are being recorded and shown through a version control system (i.e. git) not the fact that one of the repos is publicly visible via one of several possible web-GUI services. It would still be somewhat laudable even if the usage was: "Here's the repo, clone it yourself an poke around with desktop tools." In contrast, the opposite mix of "here's a website that shows diffs but you can't have the underlying data" would suck. > They don't appear to publish the XML formats they're using. I see XSD files...? Plus, this original design doc is probably still relevant. [0] [0] https://github.com/DCCouncil/dc-code-prototype?tab=readme-ov-file#dc-code-xml https://github.com/DCCouncil/dc-code-prototype?tab=readme-ov...

joshdata 2y ago

Hi. Author of that article here, and I worked with the DC Council to get the initial prototype going, if anyone has any questions. What's important in the story is that the law went from being not open to open and the law-publication-process was modernized internally. The fact that it ended up on GitHub was the least important, but most fun, outcome. GitHub adds nothing of any value for the transparency and accountability of the lawmaking process (I mean, what lawmakers do), but it is a great platform for publishing structured data files for the law to create open access.