dccouncil / law-xml Goto Github PK

Is it possible for each commit to be associated with a single act, or other cohesive change, that could be described succinctly in the commit comments? This would help watching the changes and reviewing/understanding all the changes associated with that one cohesive unit (e.g. an act).

Example: A single commit for all changes associated only with 23-134, where the commit title would be "Primary Date Alteration Amendment Act of 2019" (from commit f3c3c44#diff-f73e943e8f3fe924ea9d6f4c4dbb6db7)

I need to know how to changes the applicability of these sections as a group and individually. When I try to change 19-311.xml, nothing seems to happen or work.

Where do I find this language so I can change it because it is very wrong:

Applicability of D.C. Law 15-194: § 656 of D.C. Law 15-194 provided that the the addition of this section by § 651 of D.C. Law 15-194 is subject to the inclusion of the law’s fiscal effect in an approved budget and financial plan. Therefore that amendment has not been given effect as of September 30, 2004.

Currently the directories under dc/council/periods/ are all numbered 1, 2, 3, ..., 8, 9, 10, etc. This makes sense for text sorted by hand, but when this is displayed on GitHub and in other directories, it's sorted by the first digit meaning it shows up as: 1, 10, 11, ..., 19, 2, 20, ..., 4, 5, 6, 7, etc. The solution is to add a leading zero to the single digit periods. Is this something I can add as a PR or is there a reason it's done the way it is?

What if a law had a null pointer exception?
Laws need memory safety and an ownership system.

We need law-xml-rs as a library on crates.io.

Great article in Ars!

Any plans for Signed Commits? https://help.github.com/articles/signing-commits/

Provided there was a requirement that, say, all contributors must have something like a Keybase account (for extra verification of who they are) signed commits would enable better full attribution of who did what vs just relying on GH user ids.

What happen to the prior annotations at this section? Will they reappear when this file is merged into master? Also 5-651.xml does not appear on the branch 21-601-Ben. Is that to be expected.

your "as added" for 5-655.01 - 5-655.03 is incorrect. because you insist on amending law 15-194 (when the amendment is to law 19-311) and not the D.C. Code, I can not fix this. The earlier frustrations with the way you decided to amend the organic law and not the D.C. Code have returned. I think it best to never use the enrolled original to create the statutes-at-large, thus removing viable reason presented to me for amending organic laws. If I am going to continue to run into these types of issues in reviewing the rest of l21-160, then the launching of the new web-site will have to wait until sometime in 2018.