add wp-block-converter

[laxmariappan]

Add the wp block converter to the classic to Gutenberg tools list.

[StevenDufresne]

Awesome! To ensure that the codebases will be safe for community members to use and open to contribution, each plugin will go through a code review and should be moved over to the github.com/WordPress repository. We haven't figured out all the details yet, but would will you be willing to submit this plugin?

[laxmariappan]

@StevenDufresne I would love to submit the plugin. The plugin is created and maintained by Alley Interactive.

If we move it to the WordPress repository, should we fork it?

I have used this plugin recently, and it does a pretty good job based on my experience.

[StevenDufresne]

Good questions. I think we need to open a meta ticket to firm up the details to figure out guidelines.

A few questions off the top of my head:

• What is forkable or considered a valid submission?
  • Supported licenses
  • Do the main contributors need to submit it?
• How should credit be given?

[dd32]

I'm not sure any forking is needed here, since the tool in question is a GPLv2 library, designed to be used as part of something larger.

The upstream library would be a development dependency of either a plugin, or a CLI tool, the library as it stands doesn't appear to be something that I would expect to exist here.

As for Forking things, I'm not sure we should be encouraging that, or requiring migration to the WordPress org, forking is not exactly something I would consider to be a good thing, it's an action that occurs in open-source, but it's not something that necessarily betters a project. Forking should be left as a last-resort or as part of development, not a way to keep a copy of something under our control.