fixup! doc: document considerations for inclusion in core

doc/guides/modules-in-core.md

@@ -18,6 +18,14 @@ not.
 ## Strong arguments against including a module in core
 
 1. None of the arguments list in the previous section apply.
+2. The module has a license that prohibits Node.js from including it in core
+   without also changing its own license.
+3. There is already similar functionality in core and adding the module will
+   provide a second API to do the same thing.
+4. A module (or/and the standard it is based on) is deprecated and there is
+   a non-deprecated alternative.
+5. The module is evolving quickly and inclusion in core will require frequent
+   API changes.
 
 ## Benefits and challenges