* Be present and up-to-date in the plugin directory. * Be as ready to go on mobile as they are on desktop. * Undergo security, js fallback, i18n, and accessibility audits. * Have visual records for major flows through all new interfaces on all devices. * Have mature UI that isn't going to derail the release train. * Have a history of posting weekly updates to make/core. * Have a history of regular plugin directory updates. * Have a testing audience. * Publish a merge consideration post on make/core. * Exist for at least one release cycle. Plugins created at the beginning of a release cycle should not be considered for merge until the next release. * Merge at the beginning of a release cycle.