Does the civic issue finder actually work? Lets explore the data to find out.
The civic issues finder is a widget that fetches open issues in projects included in the Cfapi. More information about how the civic issue finder works is available in the project Readme. We want to ask questions around how these open issues become solved. We are looking at metrics like timestamps of activity and how frequently some issues get viewed or clicked. Hopefully this leads to a better understanding of how to have larger amounts of contribution on open source projects.
- Pull down all the acitivty from Google Analytics
- Go explore those GitHub Issues
- Perhaps visualize number of clicks, number of closed issues, number of commented on issues, relationships between people.
This project is currently in its exploration phase. You can see gotissues's progress and milestone activity here.
pipandvirtualenv- https://github.com/codeforamerica/howto/blob/master/Python-Virtualenv.md- Google Analytics credentials for your
.envfile. Ping @ondrae to get the credentials, then fill in yourenv.samplefile. Thenmv env.sample .env
git clone https://github.com/codeforamerica/gotissues
cd gotissues
virtualenv .venv
source .venv/bin/activate
pip install -r requirements.txt
Either use
source .env
python run.py
or to mimic Heroku use
foreman start
In the top level, run
python tests/tests.py