Update civic.json file to new specification#4
Open
emanuelfeld wants to merge 1 commit intocmgiven:masterfrom
emanuelfeld:update-civicjson
Open
Update civic.json file to new specification#4emanuelfeld wants to merge 1 commit intocmgiven:masterfrom emanuelfeld:update-civicjson
emanuelfeld wants to merge 1 commit intocmgiven:masterfrom
emanuelfeld:update-civicjson
Conversation
Hi, there! Code for DC is moving to an updated civic.json specification. This pull request formats your existing civic.json to the new standard. Feel free to look it over and make any updates. ======================== There are a few errors remaining in the civic.json, which will need a correction: Error in contact: '' is too short ======================== ======================== I also see that your repository has no license. Without a license, others have no permission to use, modify, or share your code. This site makes it easy to add an open source license: http://choosealicense.com/ ======================== The new civic.json spec keeps the required fields from the older one, but has a number of benefits. It: * removes fields that are hard to maintain and get out of date quickly * combines partner fields to be more broadly applicable * is usable by civic tech projects outside of government, as well as inside You'll see that DC Government is using this standard in its own repos: https://github.com/dcgov You can learn more about the specification requirements here: http://open.dc.gov/civic.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, there! Code for DC is moving to an updated civic.json
specification. This pull request formats your existing
civic.json to the new standard.
Feel free to look it over and make any updates.
There are a few errors remaining in the civic.json,
which will need a correction:
Error in contact: '' is too short
I also see that your repository has no license.
Without a license, others have no permission to use, modify, or share your code.
This site makes it easy to add an open source license: http://choosealicense.com/
The new civic.json spec keeps the required fields from the older
one, but has a number of benefits. It:
You'll see that DC Government is using this standard in its own repos:
https://github.com/dcgov
You can learn more about the specification requirements here:
http://open.dc.gov/civic.json