{"id":13661205,"url":"https://github.com/divegeek/uscode","last_synced_at":"2025-04-24T23:32:08.305Z","repository":{"id":626403,"uuid":"266798","full_name":"divegeek/uscode","owner":"divegeek","description":"The United States Code","archived":false,"fork":false,"pushed_at":"2017-06-30T14:37:33.000Z","size":102406,"stargazers_count":812,"open_issues_count":7,"forks_count":57,"subscribers_count":43,"default_branch":"master","last_synced_at":"2024-11-10T15:45:43.292Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"http://uscode.house.gov/download/download.shtml","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/divegeek.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2009-08-02T02:15:48.000Z","updated_at":"2024-10-10T14:05:33.000Z","dependencies_parsed_at":"2022-07-07T15:41:14.527Z","dependency_job_id":null,"html_url":"https://github.com/divegeek/uscode","commit_stats":null,"previous_names":[],"tags_count":832,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/divegeek%2Fuscode","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/divegeek%2Fuscode/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/divegeek%2Fuscode/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/divegeek%2Fuscode/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/divegeek","download_url":"https://codeload.github.com/divegeek/uscode/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":250727760,"owners_count":21477366,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-08-02T05:01:30.998Z","updated_at":"2025-04-24T23:32:06.850Z","avatar_url":"https://github.com/divegeek.png","language":"Python","funding_links":[],"categories":["Novel uses of GitHub","Python"],"sub_categories":[],"readme":"This repository contains the complete United States Code.  Its purpose\nis to publish the federal code in a way that makes it easy for\ninterested individuals to access both its content and its changes over\ntime.\n\nAnother purpose for this repository is to explore some ideas around\nhow to better facilitate the legislative process.  Legislation comes\nin the form of bills which are essentially patches to the existing\nlegal code.  Many different versions of a patch may float around to be\ndebated, discussed, amended, etc., before a final version is applied\nto the \"trunk\".  The process is extremely similar to how developers\nmanage software changes, particularly in the open source world.\n\nI think it would be very cool if something like github were used to\nmanage the actual law, all in the open and fully visible to everyone.\nI imagine the official code as sort of a master repository.  Each\nlegislator could fork this repository and hack on his own copy.\nLegislators could pull from one another as they massage the language\nto get it right.  The House and Senate would each have their own\nforks, as would the committees.  The president, too would have a fork\nof the official repository.\n\nThe legislative process would then be fully visible to anyone who\ncares to look.  Congressman Blowhard commits a change to his code and\npushes it to the public fork.  Congressman Slick looks at it, likes\nit, pulls, commits a change and tells Blowhard about his change, etc.\nEventually, the bill makes it to committee, and the committee may have\nseveral branches indicating the status of bills as they progress\nthrough the committee.  Eventually, if the bill is voted for\npresentation to the House, it is pulled into the committee's \"trunk\".\n\nIf the House votes to approve the bill, then it's pulled to the\nHouse's trunk, available to be pulled by the Senate.  The Senate can\nmake its own modifications, and perhaps the result must pass through a\nHouse/Senate reconciliation committee, before being pushed to the\n\"Passed\" branch (or fork), with a message to the president.\n\nAnyway, that's the idea.  It may seem kind of silly, but if you've\never actually tried to track the progress of a bill through the\nexisting web interfaces, it's horribly difficult, and there's a lot of\ninformation about the bill's movement through the process that simply\nisn't available.  I think using revision management tools just might\nmake the whole process both easier and more transparent. By tracking the \norigin and history of amendments, riders, and just bill authorship generally, \nit becomes easier to hold legislators accountable. \n\nAnd that's what I want to play with.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdivegeek%2Fuscode","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdivegeek%2Fuscode","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdivegeek%2Fuscode/lists"}