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]

• testing for webapp (initial coverage Add repo to Codecov webapp#61)
• update webapp README improve readme for new devs webapp#58
• improved usage section in sentry readme Improve README for new developers sentry#47 Good README needed sentry#7
• new tickets for big upcoming webapp changes
• issues for sentry architecture changes -- warc and job processing
• standardize on waffle board use across org

[dcwalk]

• PR to update roadmap repo list (or remove) [WIP] Restructure readme to rely on icons #81
• update ROADMAP with progress (woo!) from sprint
• rename sqlutil to sql_util Rename sqlutil to sql_util? #83
• spawn issues to track website work (e.g., wireframes, copy updates? (in website repo + Website: Review and update copy on datatogether.org  #42 + Website: Document deployment for datatogether.org #45

edit:

• 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 Automate creating set of standard labels and keeping repo organization consistent #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.
• Utilize DockerHub's automated build feature to slim down the Circle CI and make it idempotent. Setup automated build on DockerHub coverage#26
• Improve Docker images. Reworked Dockerfile for flexibility coverage#22 and Docker workflow improvement coverage#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.

• Update extract_href so it matches the Go version outputs. Issue #6
• Figure out the learning PR #25 that is related to the archivertools documentation
• Add morph.io links to readme to close Issue #16
• Help with testing the customcrawlers endpoint once it is implemented. Issue # 17
• 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]

• follow up with the wordsmithing crew on whether the Data Together website text can go up without a Mission at this point
• use conversation on Discontinue use of "distributed", instead use "decentralized" or "peer to peer" datatogether#32 to improve our less-than-precise uses of closely related terms decentralized, distributed, peer-to-peer, or simply "d-web"
• use conversation on Develop user journeys to shape website messaging datatogether#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! :)