The Plugin team is small but mighty. We had a very productive summit and contributor day this year, pushing forward some of the changes we’ve been working on for a while. The following notes are the product of the sessions as well as some hallway chats over red wine, gin, and cheese.
Notes:
- Security issues in the new directory have to be corrected before new users can be added
- We intend to open reviews by everyone (yes, everyone) with a .org account
- Plugin Closures will be documented and then reported on
- Plugin Check code revisited – What can we catch as a ‘before a human reviews’
- Similar but not identical plugins will continue to be accepted
- We need to allow frameworks in, but we have to do so safely to protect developers from hate-reviews when someone deletes a required framework
To Do:
- Design a ‘dashboard’ for people to check the status of their plugins (and themes)
- Add more stats to the plugin page (or possibly move to the future dashboard…)
- Replace SupportPress (our email client) with something that works (possibly Support Flow?)
- Code out a way to publicly track why a plugin was closed (see Meta 2860 and 2627)
- Determine if we want to backfill why 6500-ish plugins are currently closed (owwwww)
- Determine the best way to track ‘dependancies’ (in lieu of 22316 ever getting traction …) so frameworks and add-on plugins can be clearly indicated and reduce errors
- Incorporate theme review features such as a11y and i18n ready flags
- Make sure the VVV repo for the meta environment is sufficient for more people to contribute (see Meta Env)
- Hold ‘open office’ hours to discuss topics like developer tools, what stats are needed, frameworks etc
Most of that to-do is on me to at least get the tickets started, but if these are things you’re interested in, then I encourage you to come to the open office hours! I’m hoping to have the first in August, as I have July Vacations 🙂 Sorry, family first!
I’ll post more about what I plan to do with the open office hours soon, including topics and schedules.