Deprecate MooTools Forge

[arian]

Deprecate Forge, and notify owners of the move. Could use #mootools-plugin tag in npm search to create a listing.

[timwienk]

Although I agree the Forge in its current state is not maintainable for a long period, and I agree that standard ways of creating plugins/modules should be promoted, removing the Forge is a definite blow to users of the Core and More libraries, of which most plugins are not CommonJS compatible.

We should at least consider other options, like not moving but making it read-only, or even re-developing it in a better way (with NPM integration, and maybe only allowing NPM for new plugins, or something). In this latter case, the Forge is basically a browserify + support for old plugins.

We have to remember (and this is basically a quote from @fakedarren) that the Forge is not for us, but for the users. The people that use the Forge probably don't have another option for MooTools Core and More plugins.

[kentaromiura]

@timwienk, as I said yesterday during the conference call, by definition in order to deprecate something we must have an alternative first, we can consider providing a simple script to convert the project by adding the appropriate metadata to a package.json, but anyway we are not in a position where we can deprecate something as we don't have a solution to it yet. (that's why this issue has no milestone set)