Want to propose/use a "new" technology/module/tool ?

[nelsonic]

We need a clearly defined process for proposing/introducing new tools/tech.
My suggestion is that it should start with (a person creating) an issue in this repo where an initial discussion can be had.
If the person feels strongly about a tool/tech and wants to "dive in" create a learn-xyz repo and start trying it out and writing notes!

Criteria for Proposing/Selecting New Tools/Modules

1. What need/problem/pain is it solving.
2. How have you already tried to solve the problem? (list your approach, methods & outcomes. so others know what your pain is). If you have not tried to solve the problem do that first.
3. Does the proposed tool/module solve the exact problem/pain you have?
4. Is the (proposed) solution specific and focussed? (or are you importing a giant Library for a one feature ... e.g: Babel 185MB just to use a few ES6 "features" const, {...} and => ... !?!)
5. Is the proposed tool/module Documented, Tested, Maintained/Stable and Secure?

What else should we be factoring in when making decisions about tech?

[nelsonic]

This is what we are trying to avoid: https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f ... 😕