Roadmap & guidelines for contributors

[indexzero]

Since publishing the 3.0.0-rc this past November a number of things have kept me quite busy in my personal life. I won't go into the details, but those who know me know it's been a rough 18-months. Things have not calmed down, but hey, that's life.

The purpose of this PR is to outline the current roadmap in the context of issues that have been triaged. There are a number still to triage so the list may change. If you're interested in contributing please respond to this issue with the number of hours per month you could dedicate and how complex of an issue on a scale of 1 - 10 you feel you want to take on:

• 1 being trivial, probably a duplicate.
• 10 being you feel comfortable running a custom build of node to verify it's not a bug in node itself if it comes to that.

A few folks have volunteered to help triage issues (virtually) face-to-face over the next month to six weeks. Current strawman goal is to ship 3.0.0 out of RC by end of March.

[cdaringe]

• 2 hrs/month
• 1-5 complexity commit

if we want to do organized triage sessions on IRC/gitter/whatever, that would be the most motivating. i'm not intimate w/ the source, but willing to learn.

[cdaringe]

^ so important. love these. the ampersandjs triage process golden rule emphasized always "be nice"~

[ctrom]

• 4 hrs/month - at least for the next couple months
• 5

Cleaning up the list of issues and PRs would go a long way toward instilling confidence in the long term viability of this project. I'm willing to spend some time helping to triage and review if a more authoritative member of the community is willing to go behind and verify my work.

[indexzero]

Thanks all! I'd like to welcome @DABH as a new maintainer of winston. We'll be working on triage the next 1-2 months and trying to get the final winston@3.0.0 out in April!

@cdaringe @ctrom thanks for reaching out. Will be in touch with you soon about how you can help.