Gutenberg: Plugin: Let's get Gutenberg in the plugin repository 🎉

[jasmussen]

It's time we get this baby out into the wider world. Let's look at what's required for us to ship this plugin in the repository.

This would essentially fix #655 through other means.

[ntwb]

Creating a new #meta ticket to have it added as a _featured plugin_ regularly sync'd has would be ideal:

https://meta.trac.wordpress.org/browser/sites/trunk/api.wordpress.org/public_html/dotorg/github-sync/feature-plugins.php#L17

[nylen]

One thing we need to do first is make sure our vendor scripts are bundled with the plugin and not re-downloaded every day, or on each page load.

[westonruter]

I don't think the featured plugin sync will work with Gutenberg as-is because it creates plugins from master without doing any build step (unless it is updated to support that). I think instead a Travis CI integration should be done which builds pushes to master and then commits them to plugin SVN (via credentials stored in encrypted environment vars, though these credentials could be leaked by a malicious contributor hacking the .travis.yml file).

[mtias]

I was planning on just pushing the build manually on a weekly basis or so to the directory. Not sure if setting up something more complex is worth the time.

[mtias]

@nylen do you think you can handle the bundling tasks?

[westonruter]

Can part of this be to also exclude React and ReactDOM from being bundled into the app so that they can be re-used by other JS apps, such as in plugins that define their own blocks, to avoid multiple copies of React needing to be loaded? I believe this was already talked about in regards to JS modules in WP.

[aduth]

They shouldn't be bundled. They're referenced as externals to their respective globals enqueued server-side.

[nylen]

We should be ready to do this now. See https://github.com/WordPress/gutenberg/issues/1147 for other considerations for each release, such as git tagging.

[jasmussen]

Closing this as fixed. HOORAAAY! Great job everyone 🌟