Review/triage existing GitHub issues (+ new labels)

[patcon]

Re-ticketed from: https://github.com/pol-is/polis-issues/issues/128#issue-593756050

Reviewing all past issues seemed like it might be a good thing to do before proposing/tagging new labels, closing dups, merging, seeking more info, commenting, inviting contributions, etc.

Used github-csv-tools to export each queue to CSV, then dropped them all into a Google spreadsheet. The idea is to have a scratch space for myself or anyone else before creating a bunch of noise through commenting/closing/etc.

GSheet: Polis: Issue export from Github repos (others pls feel welcome to work in this sheet too)

New issues (created after export) will show up here:
https://github.com/search?q=org%3Apol-is+created%3A%3E%3D2020-04-23&type=Issues

---

This is what I expect to have done to consider this issue closed

To Dos

• make a summary spreadsheet
• review all open issues
• stretch: review all closed issues
• customize dependabot for monorepo Configure dependabot to work on monorepo #230
• suggest retitling and merging as appropriate
• get all open issues onto 🔒 org project board
• set project board as public (Q: is there a reason to keep it private right now?) Small, quick tasks related to community stuff #79
• determine any helpful labels
• ... [anything else?]

[patcon]

Re: potential use of labels. here are some projects i've worked on or learned from, which might provide inspiration for our own patterns of label use (though not advocating prematurely adding a billion labels 🙂)

• https://github.com/publiclab/plots2/labels
  • Ruby/HTML/CSS/Javascript/<language>
  • first-timers-only/fto-candidate/fto-in-progress
  • break-me-up
  • blocked, more-details-please, refactorization, add-code-links, outreach, systems, support, priority, brainstorm, multiple-use, installation, testing, documentation, search, metrics, hall-of-fame, supportive-task, community check-in, quality-assurance
• https://github.com/edgi-govdata-archiving/EEW_Planning/labels
  • ...
• https://github.com/gratipay/gratipay.com/labels
  • ...
• https://github.com/gratipay/inside.gratipay.com/labels
  • categories: tech/support/security/safety/product/core/compliance/accounting
• https://github.com/edgi-govdata-archiving/web-monitoring/labels
  • ...
• https://github.com/hoodiehq/hoodie/labels
  • needs: *, severity: *, frequency: *, type: *, invalid, dreamcode, starter

Related: https://github.com/pol-is/polisServer/issues/225

[patcon]

As I'm reviewing old issues, this here's a pending shortlist of candidates that might work for us:

• community: break-me-up, first-timers-only, outreach
• languages: Javascript, HTML, CSS, ReactJS, Docs, Clojure, Docker, SQL (?)
• components: server, client-admin, client-participation, client-report, math
• misc: API, infrastructure, accessibility, embeds

[patcon]

Just finished reviewing all past issues (open & closed) 🎉

[patcon]

Added labels:

• section:client-admin
• section:client-participation
• section:client-report
• section:math
• section:server

(Feedback or alt names welcome! Normally, I'd get prior feedback on changes to labels, but this one felt real safe.)

[patcon]

Example: Labels with emoji! https://github.com/mergeability/mergeable/labels

[patcon]

Added label for accessibility (incl localization) and discussion for open convos before next steps surface.

EDIT: Also, infrastructure and community labels. Also, I put emojis at the store of most labels, to make it friendlier to visual folks who show up.

[patcon]

We've got a decent set of labels, and we've brought all issues into this repo -- I think we're good to close this for now, but poke me if you disagree :)

[patcon]

Note, previously added labels for chore and first-timers-only