Five ideas for followup tickets after sprint

[patcon]

Each of us who participated in the sprint should aspire to, before leaving today (or at least before going to sleep), creating 5 tickets for possible next steps.

• Don't worry about overlap with others -- repeats are ok :)
• A one-liner is fine. Full context can be added later.
• we'll close this issue when all the new tickets have been spawned in the proceeding week

cc: @flyingzumwalt @titaniumbones @ebarry @dcwalk @b5 @patcon @jeffreyliu @ebenp @ibnesayeed @mhucka @rgardaphe

(@dcwalk edit: checking off list when we have issues to track 'em 😓 )

[titaniumbones]

• [x] testing for webapp (initial coverage https://github.com/datatogether/webapp/issues/61)
• [x] update webapp README datatogether/webapp#58
• [x] improved usage section in sentry readme https://github.com/datatogether/sentry/issues/47 https://github.com/datatogether/sentry/issues/7
• [x] new tickets for big upcoming webapp changes
• [x] issues for sentry architecture changes -- warc and job processing
• [x] standardize on waffle board use across org

[dcwalk]

• [x] PR to update roadmap repo list (or remove) #81
• [x] update ROADMAP with progress (woo!) from sprint
• [x] rename sqlutil to sql_util #83
• [x] spawn issues to track website work (e.g., wireframes, copy updates? (in website repo + #42 + #45

edit:

• [x] figure out a way to automate 🎛 : 1) updates to issue templates, readmes (avoid sed where possible ;)) 2) adding/updating labels to repos 3) ?? moar things #82
• [ ] document our newfound love of hub and ghi

[ibnesayeed]

I only really looked at the Coverage repo so my suggestions would be in that context, but some of these can be considered for other repos where they make sense.

• [ ] Run CI builds on each PR and subsequent commits to existing PRs, not just when they are merged into the master branch.
• [x] Utilize DockerHub's automated build feature to slim down the Circle CI and make it idempotent. https://github.com/datatogether/coverage/issues/26
• [x] Improve Docker images. https://github.com/datatogether/coverage/pull/22 and https://github.com/datatogether/coverage/pull/28
• [ ] Add a stackfile for production environment.
• [ ] Remove the Makefile and encourage using Docker Compose directly by improving Developer Docs, as wrapping Compose's functionalities into make tasks is less flexible and becomes pointless very quickly.

[ebenp]

I focused on the archivertools repo so my list reflects that.

• [x] Update extract_href so it matches the Go version outputs. Issue #6
• [x] Figure out the learning PR #25 that is related to the archivertools documentation
• [x] Add morph.io links to readme to close Issue #16
• [x] Help with testing the customcrawlers endpoint once it is implemented. Issue # 17
• [x] Find a really good Go / Python web scraping reference and documentation. issue # 23

EDIT: so these are almost all issues. For the Python / Go web scraping references I opened an issue and referred back to this.

[ebarry]

• [x] follow up with the wordsmithing crew on whether the Data Together website text can go up without a Mission at this point
• [x] use conversation on https://github.com/datatogether/datatogether/issues/32 to improve our less-than-precise uses of closely related terms decentralized, distributed, peer-to-peer, or simply "d-web"
• [x] use conversation on https://github.com/datatogether/datatogether/issues/33 to advance messaging to stakeholders

[dcwalk]

I'm closing this as we've spawned major issues in all areas to track out progress 🎺, now we just gotta work! :)