Re:How I changed the law with a GitHub pull request
by dgreisen on Monday November 26, 2018 @10:29AM
(#18533960)
We take long-term access to the law very seriously. For the reasons you give, we rely only on native git operations. PRs are a convenient interface, nothing more.
Re:How I changed the law with a GitHub pull request
by WorldMaker on Monday November 26, 2018 @02:14PM
(#18535972)
There are technical solutions that could be used here. You can JSON dump the PR contents and Issue contents, for example, into another repository (or a branch in the same repository). It wouldn't be hard to automate that process with the GitHub API.
That doesn't solve the interop problem that would exist in trying to implement secondary UI systems that can redisplay that information usefully, but ETL of that sort is full of options and developers with experience.
JSON dumps of GitHub information would be useful to more open source projects beyond legislative history. I think a good automated solution could be generally useful, if someone wanted to invest in it.
That's the problem though. In principal, if they only use pure-git operations in the process, it would be easy to move at any point. But if they leverage the entire Github platform, i.e. PR discussion, issue tracking etc, then important parts of the legal history will be bound to the github platform.
And that's not great. Github is free for public projects for now, but as with any publicly traded tech company, they're able to change the terms of use of their product at any time to suit the needs of the company.
When we're talking about enshrining the laws of society, we're talking about a very long-term proposition. Technology companies pivot and or kill products all the time. What if we decided to record legislative history on Google Flow?