Plugin Review Process | Some issues I think we should fix and details to clarify transparently

[viktor]

Overall I agree, but this is the part I disagree with. Specifically:

@anon66243189

C) I believe it should be made public in the relevant forum here, when a new submission is made, what the status thereof is (use tags in the forum such as reviewing, rejected) and why it is rejected, if. That same for Developers Submissions.

1. Plugin review process is to ensure plugins comply with guidelines and are safe for the community to use. Community should not participate in this process until plugin is reviewed and published by the review team. Giving people access to a plugin before the review process defeats the purpose of the process.

2. Learning from WordPress review process, reviewers should always remain anonymous. All emails should be from the review team without any identifying information. This is to protect revewer from harassment.

3. Developers should definitely get a reason for rejection or suspension, and they can choose to bring it to the forums for a discussion. But the whole process doesn’t need to be public, this is especially true if it’s vulnerabilities or malware, etc.

Hopefully, we’ll get the directory integrated soon. I’m trying to get that process going again.