Grow GitHub community #88
Description
One of my big pitches for moving to JKAN/GitHub was to enable a community to grow around GitHub making it easier to maintain the data set. For the most part this hasn't happened - so let's set some goals (for the rest of th year) and try some things.
Today >> Goal
Starting point
- drive-by contributor fixes - 0? >> 5
- drive-by contributor opens issue for fix - 1? >> 3
- Stars - currently at 7 >> 50
Referrals
| Site | Unique visitors |
|---|---|
| opendataphilly.org | 85 >> 300 |
| github.com | 3 >> 30 |
Improvement ideas
To streamline contributions or otherwise increase visibility
Done
- Tag issues as beginner friendly? (Or is data catalog already good enough?)
Ready to go
- Add GitHub banner to site - easy #90
- Revise text to explicitly ask for contributions - easy #91
- See if we can make Open in Github link go to code and not preview (preview looks weird for this data). - medium #92
- Update README and/or Contributing to be for OpenDataPhilly and not JKAN (May require some thought going into how we keep docs/ up-to-date with JKAN if we want it customized too) - easy/medium #93
Hard or needs more thinking to hash out
- setup the decap cms and finish implementing open authoring - hard and requires ops work too.
- review Google analytics to see what flows we could improve - ?
- GitHub discussions - ?
- Promote this to students/others as a good public way to learn GitHub flows.
Just throwing some ideas out - please do add to it!