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

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**](https://github.com/dwyl/aws-lambda-deploy/issues/23#issuecomment-188792991) 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_?