Skip to content
This repository has been archived by the owner on Oct 21, 2019. It is now read-only.

Determine how plugin authors should mark their plugin as Gutenberg-compatible #6

Open
danielbachhuber opened this issue Feb 19, 2018 · 2 comments

Comments

@danielbachhuber
Copy link
Owner

Couple of options:

They could sign up for an account and mark it themselves, or we could set up an email address to process that feedback.

At the least, we should decide on a workflow.

@danielbachhuber danielbachhuber changed the title Determine how plugin authors should mark their plugin as fixed Determine how plugin authors should mark their plugin as Gutenberg-compatible Mar 1, 2018
@maevelander
Copy link

I've already triaged mine for compatibility so it would be quick and easy to login and mark them in your db?

@danielbachhuber
Copy link
Owner Author

At this point, we'd prefer to limit accounts to those testing dozens of plugins. If you'd like to send me a note at the email address listed on my GitHub profile, I'd be happy to mark your plugins as compatible.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants