This is a summary of the Plugin Directory chat from April 27. (Slack log)
Attendees: @ipstenu, @matt, @obenland, @clorith, @dd32, @pento, @tellyworth
- Tagging system
@matt encouraged the participants to figure out a tagging system that gives people a better understanding what’s behind the installation of a plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. Something along the lines of a Free/Light/Pro classification, that illustrates the difference between (for example) Vaultpress (have to pay), Akismet (should pay if large), and Jetpack (no pay). This could be separate from the proposed 3-tag-limit and be based on an honor system starting out.
- Determine what it means if a plugin is truly published
After a detailed discussion about possible solutions and their repercussions around this topic, participants came to the conclusion that plugins should be approved, which triggers approval email and the creation of the SVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. repo, but need an initial commit, to be switched to publish and actually show up in the directory. The goal is to ensure plugin authors are at least familiar enough with SVN to make a commit, to reduce support burden after mass emails to plugin authors that ask them to update in preparation of a major release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality..
- Tickets for M2
After committing the updates to reflect the changes decided on above, #1570 should be ready to go and considered fixed. @dd32 already fixed #1575, and @tellywoth and @pento anticipate #1574 and #1614 respecitvely to be finished by next week. Dion has started thinking about #1579 and has a shortlist of items containing Favorites, Contributors, Zips, Screenshots, and Stats pages. @obenland will look at the remaining ticket #1572. @mapk will be working on design mockups for the new front-end, and @ocean90 offered post-meeting to be available for any translation-related questions @tellyworth might have.
The next meeting is on Thursday May 5, 00:00 UTC.