>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1262752. --> Reported by: [sun](https://www.drupal.org/user/54136) >>> <p><strong>Do not answer the questions</strong> here (yet). Where and how to answer the questions is part of what we need to discuss. (yuck! ;)</p> <p>The following list is based on <a href="http://www.unleashedmind.com/en/blog/sun/crisis-conclusions">initial conclusions</a> and <a href="http://www.drupal4hu.com/node/303">@chx's blog post</a>.</p> <p>Since then, discussion moved on and analyzed more in-depth issues in:</p> <ul> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-17"><a href="https://www.drupal.org/project/drupal/issues/1255674" title="Status: Closed (outdated)">#1255674: [meta] Make core maintainable</a></span></li> <li><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/sandbox/sun-1255586/-/work_items/1260214" class="drupalorg-gitlab-link">https://git.drupalcode.org/sandbox/sun-1255586/-/work_items/1260214</a></span></li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/1242448" title="Status: Active">#1242448: [meta] More flexibility for core installation profiles</a></span></li> </ul> <p>Especially @eaton's, @catch's, @Crell's, @EclipseGc's, and @sun's follow-ups need some attention - we need to check whether they contain additional discussion items, or whether one of the below needs to be adjusted and re-phrased.</p> <h3>Discussion items</h3> <p>We need to discuss...</p> <ol> <li>What <em>we are able</em> and <em>want</em> to maintain in Drupal core?<br> (needs to cover all stuff that core provides, not just platform vs. product vs. framework; i.e., also subsystems, APIs, etc) </li> <li>Which core features are actually product features?</li> <li>A <em>deadline</em> for finding maintainers for product features?</li> <li>What we are going to do with stuff that no one wants to maintain?</li> <li>Whether we can or want to move product features into a separate product project? <p>...having the sub-topics:</p> <ol> <li>Whether product modules are going to be separate projects or contained in the same repo as the installation profile.</li> <li>Who is going to maintain the installation profile and/or product feature modules.</li> <li>How the "core" development workflow would look like, what changes are involved, and whether those are for the better or worse.</li> <li>Whether this change is going to be harmful in the long-run due to core developer "fragmentation" and separation (who would be kinda "split" into framework and product contributors) and how that affects Drupal's future.</li> <li>Which organizational/technical challenges exist for "core contributors" (since the identical people that maintain the product feature modules now would probably have to maintain them further in the short-term).</li> </ol> </li> </ol> <h3>Procedure</h3> <p>Lastly, we also need to discuss where and how to discuss these discussion items.</p> <p>@sun suggested:</p> <blockquote><p> Originally, I thought of everyone just simply copypasting those discussion topics, and publishing their input, opinions, and arguments on each item, on their very own blogs. That is, because these perspectives are not going to be directly actionable, but instead, they are independent answers to pretty tough questions. I'd still be in favor of doing that (and perhaps revising/completing the list of questions/discussion topics first, not sure whether it's complete). The only downside I'm able to see is that those opinions can't be "tracked" easily, and also can't be "merged" back into a d.o issue easily due to the fragmentation/distribution. But even with those constraints, the independent answers (not +1s) would be far more interesting and appealing to me. Lastly, I think everyone knows - publishing something on your own blog instead of some random issue on a community site makes you think twice about what exactly you write and propose ;) </p></blockquote>