Review and curate plugins included in bundles

[majick777]

As part of creating an installation bundler for the OpenProducer stack, we need to decide which plugins are suitable for inclusion. Related to this we came up with the idea of having differently named "bundles" (or substacks) and having different plugins within each bundle. eg:

• Base - foundational plugins common to all installs. (Akismet, All in One SEO, AMP, Google Site Kit, Gutenberg, Jetpack, PWA, Redirection, User Avatar, ?TablePress, ?AMP for TablePress)
• Newspack - all the Newstack plugin modules (Ads, Blocks, Content Converter, Image Credits, Media Partners, Popups, Rename Comments, Supporters, AMP Disqus) and related extras (Co Authors Plus, Disqus Comment System, Organic Profile Block, Publish to Apple News) and optional extras (Broadstreet, Constant Contact Forms, DocumentCloud, Instant Articles for WP, LaterPay, MailChimp 4 WP, Parse.ly, Password Protected, Pym.js Embeds, Super Cool Ad Inserter, Coral Project)
• RadioStack - Radio Station (+ Blubrry PowerPress? or other Podcasting?) ...
• EventRack - The Events Calendar (+ GigPress?) ...
• eCommerce - WooCommerce (+ related plugins)

As we are basing on Newspack, we start with their list of already-curated plugins for the Newspack bundle. But of course we can come up with other relevant plugins for the other bundles (without going too overboard of course!)

Further, since we are looking at providing an option for which of the plugins in a bundle to install (unlike Newspack) this open up the possibility to include extra plugins also but only have the main ones enabled by default. Sane defaults can provide the balance here between the too-minimal and "kitchen-sink" approaches.

So again for example with Newspack, there are a bunch of Newspack-specific plugins (and some base/ecommerce plugins mixed in), but also a lot of extra plugins for more specific needs that they include in their curated list. Rather than remove these entirely, we could just have them be unselected by default, rather than forcing them to be installed with Newspack. These are the "optional extras" marked in the list above.

[tonyzeoli]

@majick777 I guess you could add both GigPress and The Event Calendar and the user can choose which one they want to use. There are clear overlaps though with these two, so we just want to be mindful. The only other thing I can think of that competes is Constant Contact and MailChimp, but there's also ConverKit too, which is shifting to focus more on creators in the entertainment industry. My wife is working on a potential project with them, so that's how I learned about their pivot to focus on the creative industry.

[tonyzeoli]

@majick777 @gusaus Also, we may want to think about creating Discussions before Issues, so that we're not filling the Issues column with items that should not go through the product queue. I've set up Discussions tab in Git here, so maybe we can transfer this until we get to a clear decision process - then we can add the issue.