search

BetaNYC / civic.json

A specification of the civic.json metadata standard for civic technology projects
47 stars 17 forks source link

Updated README to reflect new project direction #5

Open jpvelez opened 10 years ago

daguar commented 10 years ago

:thumbsup: Thanks! Was just about to do a similar PR. :smiley_cat:

noneck commented 10 years ago

have we come to a point where we have outlined the file standard?

in the meantime, Civic.JSON describes what BetaNYC is using to power our projects.betaNYC.us.

jpvelez commented 10 years ago

No, we need to start the convo by creating a few issues- Juan-Pablo Velez 312-218-5448 jpvelez@gmail.com

On Thu, Feb 20, 2014 at 2:44 PM, Noel Hidalgo notifications@github.com wrote:

have we come to a point where we have outlined the file standard?

in the meantime, Civic.JSON describes what BetaNYC is using to power our projects.betaNYC.us.

Reply to this email directly or view it on GitHub: https://github.com/BetaNYC/civic.json/pull/5#issuecomment-35666706

daguar commented 10 years ago

@noneck -- The working version of the file standard that is being implemented in CfA's "civic-json-worker" cross-municipality app is outlined by @ondrae here: https://github.com/codeforamerica/civic-json-worker/issues/14#issuecomment-35569288

I do think Juan's pull request is on-point. My understanding was that this repo would be the place for discussion of the data standard, and that repo would be discussing implementation of an "aggregator" API.

But if you're thinking this BetaNYC repo should preserve what yous guys are doing, we could potentially:

  1. Discuss the data standard over there (ie at https://github.com/codeforamerica/civic-json-worker )
  2. Fork civic.json to CfA's repo and work on the broader data standard going beyond BetaNYC in that area

Bottom line, though, to me is that right now the proliferation of things here makes understanding the state of play kinda difficult. So if Juan's PR isn't cool at this point, I'd still minimally like to see a ref in the README pointing at CfA's civic-json-worker page as the place to contribute and hash out the inter-municipality data standard.

jpmckinney commented 10 years ago

Why is there a project_needs field within the sample GitHub JSON? I'm not aware of GitHub offering that field.

noneck commented 10 years ago

Dave,

I'm sorry. Does that standard comply to schema.org standards?

Maybe you can propose better language?

N

Sent from my TI–85

On 23 Feb 2014, at 12:21, Dave Guarino notifications@github.com wrote:

@noneck -- The working version of the file standard that is being implemented in CfA's "civic-json-worker" cross-municipality app is outlined by @ondrae here: codeforamerica/civic-json-worker#14 (comment)

I do think Juan's pull request is on-point. My understanding was that this repo would be the place for discussion of the data standard, and that repo would be discussing implementation of an "aggregator" API.

But if you're thinking this BetaNYC repo should preserve what yous guys are doing, we could potentially:

Discuss the data standard over there (ie at https://github.com/codeforamerica/civic-json-worker ) Fork civic.json to CfA's repo and work on the broader data standard going beyond BetaNYC in that area Bottom line, though, to me is that right now the proliferation of things here makes understanding the state of play kinda difficult. So if Juan's PR isn't kosher at this point, I'd still minimally like to see a ref in the README pointing at CfA's civic-json-worker page as the place to contribute and hash out the inter-municipality data standard.

— Reply to this email directly or view it on GitHub.

daguar commented 10 years ago

@noneck -- civic-json-worker isn't my project. Could you bring up this issue over on that repo if you think it merits changing the implementation?

I opened an issue for that here: https://github.com/codeforamerica/civic-json-worker/issues/21

ondrae commented 10 years ago

Commented on #6 to show an example with all of our various attributes included. Lets start pruning them down there.

migurski commented 10 years ago

@jpmckinney, project_needs pulls out issues labeled in a way that suggests external help is welcome. We’re thinking forward to an automatic but still intentional way to surface possible opportunities for help.

jszwedko commented 8 years ago

Sorry to bump a dead issue, but is the format documented in the PR the recommended format for civic.json files?

ondrae commented 8 years ago

Hey @jszwedko. The most up to date civic.json stuff is either Code for DC's at http://open.dc.gov/civic.json/builder.html or Code for America's at https://github.com/codeforamerica/brigade/blob/master/README-Project-Search.md#civicjson.

The Code for America Project Search uses the status and tags attributes from the civic.json.

jszwedko commented 8 years ago

@ondrae thanks for the pointers :clap: