Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data sets for AURA ATX #143

Open
6 of 17 tasks
rgreinho opened this issue Aug 16, 2019 · 0 comments
Open
6 of 17 tasks

Data sets for AURA ATX #143

rgreinho opened this issue Aug 16, 2019 · 0 comments

Comments

@rgreinho
Copy link

What problem are you trying to solve?

The non-profit organization AURA defends concepts to help building a better Austin for everyone. The organization being data driven, they are looking for information to back up what they claim.

The main goal is to create reproducible data sets for each claim, and generate artifacts to help advocate in their favor.

Here is the list of projects we are looking to kick-off:

  1. Cover Per Capita
  2. Schoolchildren Per Acre
  3. Parking as Traffic Calming
  4. Density and GHG Emissions
  5. Is Housing Segmented?
  6. Rent Burden Change
  7. Where'd they live before?
  8. Within-Metro Migration
  9. Land Value Per Unit
  10. Density and Transportation

Each project has its own steps, but the gist of it is:

  1. Evaluate existing sources and build a data set
  2. Create a pipeline to automatically build/update the data set
  3. Create artifacts for the advocates:
    a. Graphs
    b. Blog posts
    c. Infographics
    d. White papers

Who will benefit (directly and indirectly) from your project?

The first people who will be able to leverage our work is the AURA advocates themselves. A close second would be all the other local organizations helping to build a city for humans. Last would be the residents of Austin, and anybody else interested in urbanism.

What other resources/tools are currently serving the same need? How does your project set itself apart?

For the first series of claims we want to support, there is no data specific to the city of Austin. Therefore we will build the data sets and share them with the public in an open source fashion.

We will also share the automated pipelines and/or the methodology used to build these data sets.

Where can we find any research/data available/articles?

Each project will have its own set of resources.

What help do you need now?

We are looking for:

  • People who like to manipulate data, build automated pipelines, design and write
  • People who can code in Python

What are the next steps (validation, research, coding, design)?

See the steps described in the first section.

Not all the projects were created in the GitHub organization. The projects will be started on-demand, when maintainers/contributors will be able to allocate resources to them.

How can we contact you outside of Github(list social media or places you're present)?

The GitHub organization for AURA: https://github.com/aura-atx
AURA's website: https://www.aura-atx.org/


Project management

Checklist for NEW ideas 👶

Hey, you're official! You're now part of the growing civic hacking community in Austin. Here's a few things to get started (a couple you've probably already done).

  • Create this idea issue
  • Flesh out the who, where, and what questions above
  • Start the conversation about this idea on Slack Replace this link to the #general channel with your project's preferred channel.

Checklist for ACTIVE projects 🔥

Let's get this project started! When this idea starts taking off, the Projects Core Team will start helping this project's lead(s) out with project management and connecting you to resources you may need. To get there, please complete and check off the following:

  • Post an update at least once a month to this issue. Use BASEDEF for ideas, but it's ok even if your update is just "nothing new happened this month" or "we saw a small increase in traffic to our app this month". If there's no activity for two months, that's no problem, life happens. We'll just label this as backlog so others know you'll get back to it when you have the time. If nobody hears from you at all in more than two months, we may mark it as abandoned so that others can pick up this idea and run with it.
  • Take 30 minutes to complete Open Leadership 101
  • Create a GitHub repository. Ask for help setting up permissions if you want your repository to be within the Open Austin Github organization.
  • Create a README file in your project repository. This file should help newcomers understand what your project is, why it's important, and kinds of help you're looking for.
  • Create issues to describe each task that you plan to do or need help with and how a contributor can get started on that task. You might start and stop a lot, so consider issues as your to-do list.
  • Create a team for your core contributors
    • This will make it easier for you to manage your github repo access. People on a team have the same level of access. Admin access will allow your trusted contributors to make changes as needed.
    • You can remove and add people to your team as needed.
    • View some of our teams: https://github.com/orgs/open-austin/teams
    • Note: You can also allow collaborators outside of your team and give them more limited access.
  • Create a user group in Slack so you can "@" your core contributors all at once, without bothering other people who use the Slack channel. You'll need permission from a Slack admin, so just mention @Leadership on Slack to get this set up.
  • Create a Google Drive, Dropbox, or other cloud storage to share larger files. Github and Data.World are good for code and data, respectively, especially when you need version control. But they're not good for very large files, documentation, articles, etc. A cloud storage option will allow you to easily share, create, and collaborate on documents with your team and help organize ideas and thoughts.
    • Doing this early on can help your team stay organized and to onboard new contributors who wouldn't have access to files you all have shared over email.

Checklist for FEATURED Projects 🎉

To have your project FEATURED on Open-Austin.org, complete the following documentation. In past projects, well-documented featured projects have more contributions than other projects.

If you get stuck at any point, feel free to reach out to the leadership team on Slack by adding @Leadership to your message. We're here to help you make real changes to our city.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant