Adding this issue as a place to discuss ideas related to the future of Drupal core development and the packaging of components. This is after the core conversation Peter Wolanin and David Hernandez had at DrupalCon Baltimore to discuss the feasibility of removing core modules and APIs and what qualifies something for removal.
Link to session: https://events.drupal.org/baltimore2017/sessions/less-more-what-modules-...
Link to video: https://www.youtube.com/watch?v=jPdR82N8Wg0
Idea summary
What is the problem to solve?
The crux of the debate is the continuous clash between Drupal as a product and Drupal as a framework. As we continually progress with composer, and make workflows a little more difficult for site builders, we start losing that user base. We also could do more to advance product level features and interfaces, but risk further bloating core and making it less attractive as an api-focused framework.
Who is this for?
(Evaluators, site visitors, content authors, site managers, (advanced) site builders, developers, core developers, site owners, other?)
Result: what will be the outcome?
(Describe the result: how will this improve things for the stated audience(s)?)
Prior to drupalcon, I had various ideas about the removal of components, small core rehashing, etc. One idea that I've been settling on is removing modules from core and repackaging them as an official distribution maintained by the core team. I wrote some about this idea in a blog post. https://ffwagency.com/digital-strategies-blog/proposal-future-drupal-cor...
Tim Millwood also made a post encapsulating some of his thoughts. http://www.millwoodonline.co.uk/blog/the-future-of-drupal
How can we know the desired result is achieved?
(Usability test, a metric to track, feedback)