{"action":"created","issue":{"url":"https://api.github.com/repos/invinst/shootings-data/issues/37","repository_url":"https://api.github.com/repos/invinst/shootings-data","labels_url":"https://api.github.com/repos/invinst/shootings-data/issues/37/labels{/name}","comments_url":"https://api.github.com/repos/invinst/shootings-data/issues/37/comments","events_url":"https://api.github.com/repos/invinst/shootings-data/issues/37/events","html_url":"https://github.com/invinst/shootings-data/issues/37","id":162844134,"number":37,"title":"Proposal: Clarify purpose of repo and steps to organize","user":{"login":"jayqi","id":2721979,"avatar_url":"https://avatars.githubusercontent.com/u/2721979?v=3","gravatar_id":"","url":"https://api.github.com/users/jayqi","html_url":"https://github.com/jayqi","followers_url":"https://api.github.com/users/jayqi/followers","following_url":"https://api.github.com/users/jayqi/following{/other_user}","gists_url":"https://api.github.com/users/jayqi/gists{/gist_id}","starred_url":"https://api.github.com/users/jayqi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jayqi/subscriptions","organizations_url":"https://api.github.com/users/jayqi/orgs","repos_url":"https://api.github.com/users/jayqi/repos","events_url":"https://api.github.com/users/jayqi/events{/privacy}","received_events_url":"https://api.github.com/users/jayqi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-06-29T05:32:17Z","updated_at":"2016-06-30T21:51:47Z","closed_at":null,"body":"## Main idea\r\n\r\nGo back to the roots of this repo. From the README:\r\n\r\n>  This is a living repository of public data about Chicago’s police officers and their encounters with the public. \r\n\r\nThis means separating out:\r\n* The data (this repo)\r\n* Usage of the data (keep elsewhere)\r\n\r\n### Define a clear purpose of this repo\r\n\r\n* A copy of the data for anybody (not just InvInst and ChiHackNight people) who wants to use it for something. This is both cleaned data and raw data, as well as supporting primary documents like FOIA requests and responses.\r\n* A resource to facilitate people using the data. This means documentation of data, background and context, information about CPD/IPRA processes. This probably should be stuff in the wiki, and can be evolved as needed. \r\n* A central hub for community of data users to announce and coordinate their projects\r\n\r\n### Keeping projects using data elsewhere\r\n\r\nWe've ended up with a whole bunch of threads of people investigating different things. It doesn't make sense for those to be merged into this repo, but we still want some way keep track of that, facilitate their work, coordinate, and potentially build a community.\r\n\r\nBasic idea: projects or investigations using the data are separate, whether independent GitHub repo, Google docs, etc. This would include stuff like, e.g., mapping of incidents; resolving officer identities; analyzing pdf reports. Still encourage people to announce and document their projects so that everyone can know what they're working on. \r\n\r\n## What we need to do\r\n* Make sure we have all the baseline dataset files, e.g., make sure we have a Cleaned April, and a system for keeping an up-to-date scrape of June IPRA Portal\r\n* Clean up stuff in repo so we only have what any random person interested in using the data would need\r\n* Document what every file is. Document what each dataset contains\r\n* Startup guide for people for people to get started, potentially with examples. Great idea by Evan on Slack.\r\n* Design a process for data users to interact with each other and with InvInst. This needs to at least include ways to (1) ask clarifying questions about the data or about CPD/IPRA, (2) post info about their individual projects so that other people can get involved, and (3) raise issues about the repo or wiki.  \r\n\r\n\r\n### Idea: Use issue tracker as coordination tool\r\n\r\nWe're already kind of doing this, but here is a proposal to make it more structured using the tag system. We can have three tags:\r\n* **question** -- people can ask a question about the data or about CPD/IPRA, e.g. \"Why do POs have `INVOLVED_OFFICER_TYPE` set to `Victim`?\" For useful general questions we can add documentation to the wiki when the answer is figured out. \r\n* **project** -- people can document a project they are working on. Can link to wherever they are hosting their project. This repo would only host a link and some basic info. Inspired by new ChiHackNight breakout group tracker. \r\n* **repo issue** -- people can raise an issue about the repo, whether with the data or the wiki. e.g., \"IPRA portal scrape is missing CRID 0000000 that is on the website\"\r\n\r\n### Open question: Role of ChiHackNight group going forward\r\n\r\nMy idea here is as follows:\r\n\r\nIn short term:\r\n* Primary work is to implement the above.\r\n\r\nIn long term:\r\n* Once above work is done, then our group is done.\r\n* Still potentially value in keeping a general police accountability breakout group to facilitate ChiHackNight attendees who want to use this data for something, e.g., Chaclyn visits and answers questions; tutorial of datasets; mob programming session with data. Maybe less frequently than weekly if we don't need weekly.\r\n* If someone has a project idea that would want multiple people to contribute, can start new breakout group for that project specifically\r\n\r\n### Open question: Messaging platform (Slack or otherwise or none)\r\n\r\nDo we need/want a messaging platform to support a potential community of data users?\r\n\r\nRight now, contributors from ChiHackNight are guests on InvInst's Slack. Once this effort is finished, we probably wouldn't need it for that purpose anymore. Presumably, we would want to generally keep chat for independent projects separate (i.e., not open up InvInst's Slack to anybody random person from anywhere). \r\n\r\nWe could make a separate Slack. We could use a competitor product like [gitter](https://gitter.im) which has free public channels viewable to anyone and only requires a GitHub account to say something (advantages over Slack). Or we could decide that the Issues Tracker is sufficient for discussion and not have anything. "},"comment":{"url":"https://api.github.com/repos/invinst/shootings-data/issues/comments/229799525","html_url":"https://github.com/invinst/shootings-data/issues/37#issuecomment-229799525","issue_url":"https://api.github.com/repos/invinst/shootings-data/issues/37","id":229799525,"user":{"login":"alexsoble","id":3209501,"avatar_url":"https://avatars.githubusercontent.com/u/3209501?v=3","gravatar_id":"","url":"https://api.github.com/users/alexsoble","html_url":"https://github.com/alexsoble","followers_url":"https://api.github.com/users/alexsoble/followers","following_url":"https://api.github.com/users/alexsoble/following{/other_user}","gists_url":"https://api.github.com/users/alexsoble/gists{/gist_id}","starred_url":"https://api.github.com/users/alexsoble/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alexsoble/subscriptions","organizations_url":"https://api.github.com/users/alexsoble/orgs","repos_url":"https://api.github.com/users/alexsoble/repos","events_url":"https://api.github.com/users/alexsoble/events{/privacy}","received_events_url":"https://api.github.com/users/alexsoble/received_events","type":"User","site_admin":false},"created_at":"2016-06-30T21:51:47Z","updated_at":"2016-06-30T21:51:47Z","body":"@rajivsinclair ❤️ ❤️ ❤️ "}}
{"actor":{"display_login":"alexsoble"}}