https://github.com/sunlightpolicy/github-for-policy
How to use GitHub for collaborating on public policy (especially for open data)
https://github.com/sunlightpolicy/github-for-policy
Last synced: 3 months ago
JSON representation
How to use GitHub for collaborating on public policy (especially for open data)
- Host: GitHub
- URL: https://github.com/sunlightpolicy/github-for-policy
- Owner: sunlightpolicy
- License: mit
- Created: 2017-02-07T16:46:42.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2017-02-07T18:28:42.000Z (over 8 years ago)
- Last Synced: 2025-01-14T13:14:49.771Z (4 months ago)
- Size: 9.77 KB
- Stars: 2
- Watchers: 9
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
github-for-policy
=======
How to use GitHub for collaborating on public policy (especially for open data).
Initial material copied from here: http://government.github.io/best-practices/collaborative-policymaking/
See also:
- [GitHub — Government best practices](https://government.github.io/best-practices/)
- [GitHub Showcase — Policies](https://github.com/showcases/policies)
- [The GitHub Difference: Overcoming Barriers to Collaboration in Government](https://www.brookings.edu/blog/techtank/2015/01/15/the-github-difference-overcoming-barriers-to-collaboration-in-government/)
- [Using GitHub in Government: A Look at a New Collaboration Platform](https://policyinformatics.asu.edu/content/using-github-government-look-new-collaboration-platform)
## Collaborative Policymaking
### Examples
* [Project Open Data](http://project-open-data.github.io/) (White House Open Data Policy)
* [New York State Open Data Handbook](http://nys-its.github.io/open-data-handbook/)
* [Australian Capital Territory Open Data Policy](http://actgov.github.io/opendatapolicy/)
* [NYC OpenData Technical Standards Manual (TSM)](http://cityofnewyork.github.io/opendatatsm/)
* [Chattanooga Open Data Executive Order](https://github.com/cityofchattanooga/Chattanooga-Open-Data-Executive-Order)
* [San Francisco Open Data Legislation](https://github.com/SupervisorMarkFarrell/San-Francisco-Open-Data-Legislation)
* [San Diego Open Data Policy](https://github.com/opensandiego/sandiego-opendata-policy/)
### Logistics
* Content stored as [Markdown](http://en.wikipedia.org/wiki/Markdown), a near-plain text markup language for non-developers
* Document(s) can be published using a custom HTML/CSS/JavaScript template using [GitHub Pages](http://pages.github.com), or displayed simply as rendered (unstyled) HTML
* Encourage editing via the web interface or via [prose.io](http://prose.io)
### Encouraging Contributions
* Expose process: publish pre-release revision history, have discussions in public, memorialize in-person discussions, leverage GitHub's [Issues](https://guides.github.com/features/issues/) feature, and strive to maintain one class of contributors
* Explicitly encourage contribution — both in your project documentation and along side the published content
* License the content as appropriate, usually either [Public Domain (CC0)](https://choosealicense.com/licenses/cc0-1.0/) or [CC-BY](https://choosealicense.com/licenses/cc-by-4.0/)
* Communicate the big picture: roadmap, timelines, goals, vision, and current status
* Whenever possible, open source the problem, not the solution
* Provide encouragement, feedback, and gratitude with each contribution
* Minimize friction through tooling
* Describe requirements and how to preview changes locally
* Use automated testing via [Travis CI](https://travis-ci.org/)
* Decentralize decision-making authority to technical and subject-matter experts as appropriate
* _See also: [community-building best practices](http://government.github.io/best-practices/collaborative-policymaking/community-building.md)_
### Releases
* Whenever possible, the agency should regularly accept/reject proposed changes and cultivate community feedback
* If necessary, if a document cannot be changed, community feedback can be curated on a seperate branch from `master`
* The `community` branch can be “released” (merged) on a regular release cycle in line with agency goals