Bug triaging in our repositories

[larrysalibra]

As a first step to getting a better handle on the status of outstanding technical debt, we need to go through all of the open issues and pull requests on our repos and triage them.

We should also make notes about issues that we think should be addressed.

We should avoid working on any of the issues but just stick to triaging: tagging, closing, asking for more info, etc.

We don't have to spend time on repos that are being deprecated.

[larrysalibra]

Let's divide up repos: What do you think about this:

I can take:

• blockstack.js
• blockstack-browser and
• forum sign in related ones: blockstack-ruby, omniauth, discourse-blockstack, ruby jwt

@jcnelson can you take the core-related repos?

@jackzampolin can you take the others such as gaia, the blockstack repo, app generator, and dev ops related ones?

[jackzampolin]

I've done gaia, blockstack, app generator and I'm going to go ahead and take blockstack-core too per @jcnelson. I'll get into the smaller repos after that, but there really isn't much there rn.

[larrysalibra]

This is going a bit slower than anticipated.

I've finished blockstack.js today and about 25% of the way through blockstack-browser.

Will try to plow through the remainder on Sunday (time permitting) and Monday.

[jackzampolin]

I still have a couple of issues on blockstack-core left but almost done on this one.

[jackzampolin]

Done with my side of this. Can we go ahead and close @larrysalibra?

[moxiegirl]

Closing as outdated with our processes. Feel free to reopen if you have a problem with the close.