What are the mandatory requirements of each plugin?

[StevenDufresne]

What do the plugins require for submission?

• License
• Readme.md
• etc...

[racmanuel]

It would be great if you could add these requirements to contribute. I would like to support with a plugin to migrate from WooCommerce to WooCommerce but I need the requirements I assume they will be the same as the https://developer.wordpress.org/plugins/?

[jordesign]

Just thinking on this a little...

As a minimum - these plugins should meet the requirements of all plugins in the .org repo - does that seem reasonable?
https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#the-guidelines

I think it could be nice to include something in the ReadMe which references the Data Liberation project with links back to contribute further?

[racmanuel]

I think is great idea include something in the readme references the data liberation project with links back to contribute.

[StevenDufresne]

Agreed. We can start with those, but not all items apply:

• Software as a Service is permitted.
  • Not permitted, these are supposed to be tools for everyone to use
• Plugins must use WordPress’ default libraries.
  • I'm not sure about this one yet
• Frequent commits to a plugin should be avoided.
  • Will be irrelevant for these plugins

The really important addition is that all plugins must be "community" plugins. (Context)

[dd32]

I see no reason that the full guidelines shouldn't apply.

Obviously some guidelines will be irrelevant (SaaS, commit frequency - since it's on Github) but all others should.

Same as any other plugin, not all guidelines will directly be applicable to all plugins.

[StevenDufresne]

What about we create a /docs folder in this project and add a submission guidelines readme there? We can then create an issue template for submitting plugins that links to it.

[StevenDufresne]

Early attempt at the issue template:

---

What does the code do?

[help text]

Where is the code?

[help text]

Are you the original author?

[help text]

Code Checklist

• It contains a readme.md in the root directory?
  • It explains how to use the tool.
  • It explains how to develop the tool.
• This code has a GPL-compatible license.
• This code follows plugin guidelines.

---

I think, for now, we can accept a repository URL for submission but aim at something nicer should it become necessary. Thoughts?

[jordesign]

Would a suggestion of testing steps/instructions be something helpful to ask for as well?

[StevenDufresne]

testing steps/instructions

I tried to communicate that with:

It explains how to use the tool.
It explains how to develop the tool.

[StevenDufresne]

@dd32 What are your thoughts on forking repositories as mentioned in this ticket. Have we dealt with anything similar in the plugin directory itself?

[dd32]

Generally Forked projects aren't welcome in the Plugin Directory, unless significant changes have been made. With smaller changes the author being encouraged to submit it upstream to the plugin in question.

When the work is someone elses open-source work, that is then being submitted for the first time by someone else to the directory, that's rejected too, as the submitter doesn't own the copyright/works, regardless of whether the licence allows them to submit it. usually.