Let us not confuse git and Github, the later belonging to a reviled US monopoly.
Github is high quality, software engineering enablement platform
And git is letter management engine
101–110 of 179 posts
Let us not confuse git and Github, the later belonging to a reviled US monopoly.
Github is high quality, software engineering enablement platform
And git is letter management engine
Some of the voting results on https://abstimmung.eu/git/2024 are misleading. Votings are about a decision recommendation (Beschlussempfehlung) which sometimes negates the original request (Antrag), e.g., https://abstimmung.eu/votes/55
This needs human curation to be useful.
I first parsed this as [(German parliament) votes as a (Git contribution graph)]. But now I realize that the intended tree is [(German parliament votes) as a (Git contribution graph)]
There are also a repository containing some laws in markdown format on GitHub. They even used PRs for actual changes proposed by the parties in the parliament. Also, the commits have their proper date, so you can `git blame` on the laws and even see which president signed-off that change. Sadly, it is unmaintained. https://github.com/bundestag/gesetze
This kind of digitization is great. I don't know if they are doing it, but I always thought that it should be easy for regular citizens to see the historical reasons why a law or regulation exists. Because there is sometimes a good reason why a regulation exists, but nobody knows it.
Earlier quoted context omitted.
Nice. I kinda wish they went all the way and modified the commit details to have the actual authoring dates for each amendment/etc. Anyone know how well git plays with pre-epoch timestamps?
I just poked around a bit. So git was first created with u32 time in mind only. However because of the looming year-2038 problem, they are working on expanding that. Apparently git internals are almost ready to support more interesting timestamps. However, much of the git tooling and UI (like command line parsing and output) refuses to deal with pre-epoch timestamps. I briefly tried with git 'porcelain' and also via…
At least you won't need to worry about figuring out historical leap seconds.
There are also a repository containing some laws in markdown format on GitHub. They even used PRs for actual changes proposed by the parties in the parliament. Also, the commits have their proper date, so you can `git blame` on the laws and even see which president signed-off that change. Sadly, it is unmaintained. https://github.com/bundestag/gesetze
One of the nice thing about having an underlying structured representation of those texts is that I can also render them to e.g. Markdown[1].
I've experimented about generating the Markdown files corresponding to multiple versions (archives) of a given text and committing them to the same Git repository to be able to see diffs or blames[2].
I would like to assign the proper dates to each commit, but given there are texts in e.g. 1791, it's not possible.
0: https://refli.be/fr/lex 1: https://github.com/hypered/iterata-md 2: https://github.com/hypered/iterata-archive
Earlier quoted context omitted.
This kind of digitization is great. I don't know if they are doing it, but I always thought that it should be easy for regular citizens to see the historical reasons why a law or regulation exists. Because there is sometimes a good reason why a regulation exists, but nobody knows it.
I don't know, something tells me that lawmaking-by-git is somehow less accessible to the 'regular citizen'.
Earlier quoted context omitted.
I just poked around a bit. So git was first created with u32 time in mind only. However because of the looming year-2038 problem, they are working on expanding that. Apparently git internals are almost ready to support more interesting timestamps. However, much of the git tooling and UI (like command line parsing and output) refuses to deal with pre-epoch timestamps. I briefly tried with git 'porcelain' and also via…
Things get ugly if you go back far enough that you need to account for jurisdictions which no longer exist switching between calendars at different times from one another. I don't know how well Unix timestamps will fare for dates prior to approximately the 1600s. At least you won't need to worry about figuring out historical leap seconds.
I think that would be a 'timezone' conversion you do at display time. Internally, it's still stored as a unix timestamp.
There are also a repository containing some laws in markdown format on GitHub. They even used PRs for actual changes proposed by the parties in the parliament. Also, the commits have their proper date, so you can `git blame` on the laws and even see which president signed-off that change. Sadly, it is unmaintained. https://github.com/bundestag/gesetze
This kind of digitization is great. I don't know if they are doing it, but I always thought that it should be easy for regular citizens to see the historical reasons why a law or regulation exists. Because there is sometimes a good reason why a regulation exists, but nobody knows it.