>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3317436. --> Reported by: [hestenet](https://www.drupal.org/user/54034) >>> <h2>Transcript</h2> <h2>0&#65039;&#8419; Who is here today? Comment in the thread below to introduce yourself and tell us why you are joining us.</h2> <table> <tr> <td>bsnodgrass (he/him)</td> <td>Bob Snodgrass, bsnodgrass most places, from St Charles IL (far western burbs of Chicago)</td> </tr> <tr> <td>kreynen</td> <td>Kevin Reynen - University of Colorado</td> </tr> <tr> <td>Shefali</td> <td>Shefali from the Promote Drupal initiative :wave: Here to check the decision on the logo! :drupalparrot:</td> </tr> <tr> <td>bircher</td> <td>Fabian Bircher, long term interest in this area of Drupal</td> </tr> <tr> <td>nerdstein</td> <td>Adam</td> </tr> <tr> <td>Marios Anagnostopoulos</td> <td>Mario's from Athens :)</td> </tr> <tr> <td>thejimbirch</td> <td>Forgot to check in @thejimbirch</td> </tr> <tr> <td>Warped</td> <td>Dave in&nbsp; Chicago</td> </tr> </table> <h2>1&#65039;&#8419; Timezone weirdness -Daylight savings ends on Sunday Oct 30 in Europe, and on Sunday Nov 6 in the USA (not to mention other regions) Our next meeting won't be until Nov 8th, so we shouldn't have scheduling weirdness here - but be aware for other initiative meetings you may have in the gap week. (edited)</h2> <table> </table> <h2>2&#65039;&#8419; Do you have any topics to propose for the meeting today? Feel free to propose them in this thread, and then I will give them their own unique threads for discussion. Conversation moving slow? Go ahead and open your own thread in the next numeric order.</h2> <table> <tr> <td>dimkritsotakis</td> <td>vote for initiative logo<a href="https://drupal.slack.com/archives/C2THUBAVA/p1666364956543729">https://drupal.slack.com/archives/C2THUBAVA/p1666364956543729</a></td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>Fox Valley Drupal needs to pick a new namespace for <a href="https://www.drupal.org/project/drupalrecipes">https://www.drupal.org/project/drupalrecipes</a> - Looking for ideas and feedback&nbsp;(edited)</td> </tr> <tr> <td>kreynen</td> <td>I&rsquo;ve been distracted by non-Drupal work, but as the academic term winds down I have more time. I had an interesting conversation with Leslie Glynn at BADCamp about a desire by that group to eventually limit the Recipes that would show up so there weren&rsquo;t competing Recipes. I really like the way Salesforce&rsquo;s App Exchange allows admins to find apps and Components built on the standards they&rsquo;ve adopted for their org like Lightning or EDA. I know this is beyond the scope of either initiative, but I would really hope that the ability to install multiple recipes and/or switch recipes, we can avoid trying to define a single recipe for any use case.</td> </tr> <tr> <td>kreynen</td> <td>I also talked to a few people still maintaining D7 distributions on Drupal.org at BADCamp who weren&rsquo;t aware of the goal to end packaging with drush make on Drupal.org. I have to on my TODO list for this week to open issues in all active D7 distribution projects this week.</td> </tr> </table> <h2>3&#65039;&#8419; The primary initiative page has been reorganized thanks to @nerdstein<a href="https://www.drupal.org/about/core/strategic-initiatives-distributions-and-recipesWith">https://www.drupal.org/about/core/strategic-initiatives-distributions-and-recipesWith</a> three tracks:drupal.org improvements (<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/project_composer/-/issues/3252534" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/project_composer/-/issues/3252534</a></span>)core features: recipes/config actions (needs a plan)core installer: installation, replace standard/umami/etc (needs a plan)Please review and provide any feedback in this thread</h2> <table> <tr> <td>bsnodgrass (he/him)</td> <td>@thejimbirch did you get a look at some of the suggestions I posted on that google doc we started with? (I posted those Saturday morning)&nbsp;(edited)</td> </tr> <tr> <td>thejimbirch</td> <td>Not yet!</td> </tr> <tr> <td>nerdstein</td> <td>I&rsquo;d like to make plan issues for each track to organize the issues</td> </tr> <tr> <td>nerdstein</td> <td>I will be working on the plans in the coming days. there is a lot of great context from the meeting today</td> </tr> <tr> <td>nerdstein</td> <td>@hestenet (he/him) @thejimbirch ^</td> </tr> <tr> <td>hestenet (he/him)</td> <td>++ :thankful:</td> </tr> </table> <h2>4&#65039;&#8419; The Poll for an initiative logo is still open - thanks to those who have responded already: <a href="https://drupal.slack.com/archives/C2THUBAVA/p1666364956543729">https://drupal.slack.com/archives/C2THUBAVA/p1666364956543729</a></h2> <table> <tr> <td>Marios Anagnostopoulos</td> <td>Would the drop of number 8 falling into a pan like number 7, be an overkill;; :D</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Hehe - good question</td> </tr> <tr> <td>Warped</td> <td>Sounds like an alteration on XKCD Standards. All we need is one more alternative. :rolling_on_the_floor_laughing:</td> </tr> <tr> <td>Marios Anagnostopoulos</td> <td>@Warped not sure what that means xDI really think that the pan makes the logo more catchy... Maybe we should really consider merging the two most popular options</td> </tr> <tr> <td>hestenet (he/him)</td> <td>@Marios Anagnostopoulos <a href="https://xkcd.com/927/">https://xkcd.com/927/</a></td> </tr> <tr> <td>bircher</td> <td>yes we should have a second round where the most popular ones get recombined to new options, and if that doesn't produce a clear winner.. repeat the procedure. Organic design by committee.Only a half serious suggestion of course</td> </tr> </table> <h2>5&#65039;&#8419; Namespace collission!Fox Valley Drupal is asking for ideas and feedback to pick a new namespace for <a href="https://www.drupal.org/project/drupalrecipes">https://www.drupal.org/project/drupalrecipes</a></h2> <table> <tr> <td>hestenet (he/him)</td> <td>Raised by @bsnodgrass (he/him)</td> </tr> <tr> <td>thejimbirch</td> <td>Site builder How-To's</td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>We had a ton of conversations around site building strategies and best practices. Historically we also talked about cookbooks (filled with recipes) and test kitchen events. We are thinking this will be a likely direction for us to continue with. Makes for great discussions in user groups.I also think we can extend the idea out to other user groups and recruit more volunteers for this Core Initiative.</td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>Opened a ticket for this <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupalrecipes/issues/3317442" title="Status: Active">#3317442: Namespace Change for Drupal Recipes</a></span> on our user group project</td> </tr> <tr> <td>Warped</td> <td>Didn't Palantir have a spreadsheet they used for designing websites? Having a structured checklist for different stages of a project would be helpful. Just building off prior comments, and maybe a way to tie together several concepts.</td> </tr> <tr> <td>dinarcon</td> <td>As for the spreadsheet, are you referring to the one linked here? <a href="https://www.palantir.net/blog/developing-drupal-sites-plan-or-perish">https://www.palantir.net/blog/developing-drupal-sites-plan-or-perish</a></td> </tr> <tr> <td>Warped</td> <td>That looks vaguely familiar. I think I looked at it when it was first posted. Been a few years. :rolling_on_the_floor_laughing: Says the spreadsheet is in the trash and to make a copy. I saved it as a PDF and LibreOffice Spreadsheet.</td> </tr> <tr> <td>Warped</td> <td>I suppose the post date on that article of 2013 means it needs updating.</td> </tr> <tr> <td>thejimbirch</td> <td>I forked that years ago and have been keeping it up to date for the most part.&nbsp; And ods is attached.</td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>I was going to say, the other one is quite out of date!</td> </tr> <tr> <td>Warped</td> <td>I remember concepts a lot longer than details. But I put them together for new ideas, then work out the details, or trigger thoughts in others, so hopefully useful. Thanks for keeping it up-to-date. That was almost 10 years ago.</td> </tr> <tr> <td>Warped</td> <td>It may not fit into this initiative, but I think that pulling together all the pieces to make it easier to learn Drupal will go a long way to helping newcomers to scale the Drupal cliff. There are so many pieces of information, but finding where to start is most of the battle. A structured layout would be very helpful.</td> </tr> </table> <h2>6&#65039;&#8419; (early days for this but..) Thinking about policies/systems for handling multiple competing recipes for similar use cases.</h2> <table> <tr> <td>hestenet (he/him)</td> <td>Raised by @kreynenI&rsquo;ve been distracted by non-Drupal work, but as the academic term winds down I have more time. I had an interesting conversation with Leslie Glynn at BADCamp about a desire by that group to eventually limit the Recipes that would show up so there weren&rsquo;t competing Recipes. I really like the way Salesforce&rsquo;s App Exchange allows admins to find apps and Components built on the standards they&rsquo;ve adopted for their org like Lightning or EDA. I know this is beyond the scope of either initiative, but I would really hope that the ability to install multiple recipes and/or switch recipes, we can avoid trying to define a single recipe for any use case.</td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>Tough problem with many possible variations. Some way to override or lock down potential conflicts will need to be in the strategy as well.</td> </tr> <tr> <td>bircher</td> <td><a href="https://www.drupal.org/project/kit">https://www.drupal.org/project/kit</a> comes to mind from D7 times...</td> </tr> <tr> <td>nerdstein</td> <td>It might be worth looking at a workflow that shows changes and allows more granular review when a recipe is installed</td> </tr> <tr> <td>nedjo</td> <td><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/distributions_recipes/issues/3284777" title="Status: Closed (fixed)">#3284777: Produce guidelines and/or a standard/spec for interoperable recipes</a></span> is relevant. While we made some small initial progress there, the larger questions are still open.</td> </tr> <tr> <td>nerdstein</td> <td>@hestenet (he/him) is there an issue where we can capture background and help make a decision?</td> </tr> <tr> <td>hestenet (he/him)</td> <td>I'm not aware of one yet.. @kreynen was this something you've opened an issue for yet?</td> </tr> <tr> <td>nerdstein</td> <td>Ok should we make one? I would hate to leave it in slack</td> </tr> <tr> <td>kreynen</td> <td>@hestenet (he/him) not that I know of. It was just a hallway conversation. In my BADCamp session I talked about how I want CU to transition from each campus defining similar, but incompatible content types with custom theming and configuration specific to that type to leveraging the work Jacob Rockowitz is doing with Schema.org in Blueprint. Treat CMS development similar to how we treat CRM development around the objects defined by Salesforce&rsquo;s Education Data Architecture. In Salesforce we have hundreds of solutions for something like event management. Only a handful are designed to work with EDA&hellip; and even fewer are fully compatible with the Lightning UX. When we are looking for Apps/projects, we are looking for things are compatible with the decisions we&rsquo;ve already made. This ends up being less about Project Browser and more about how projects are categorized on Drupal.org. Leslie mentioned issues related to simplifying the project vocabularies, but I haven&rsquo;t looked for a specific issue. I know this has been discussed many, many times over the years. What I&rsquo;m talking about is more of a cathedral/bazaar discussion and Drupal.org approach to project discovery.</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Worth making an issue, I think.</td> </tr> <tr> <td>hestenet (he/him)</td> <td>I can do so in maybe an hour if someone doesn't get to it first.</td> </tr> <tr> <td>nerdstein</td> <td>I also can after this meeting</td> </tr> <tr> <td>nerdstein</td> <td>(Not our virtual meeting but a work meeting I am in)</td> </tr> <tr> <td>leslieg</td> <td>The initial thinking from the Project Browser initiative was that we would have one community vetted&nbsp; "Recipe" for a use case like "Event Management". (We hadn't gotten to how that would be accomplished)</td> </tr> <tr> <td>leslieg</td> <td>Since then we have added Sources for modules, so we could have Recipes tied to Sources as well. If the source is ABC University, they could have specific modules and recipes flagged to be displayed by the Project Browser when that Source is specified.</td> </tr> <tr> <td>leslieg</td> <td>Lots to be discussed in this area</td> </tr> <tr> <td>nerdstein</td> <td>I&rsquo;d love to get as much context transfered into issues and start holding discussions on where they are to be had</td> </tr> <tr> <td>nerdstein</td> <td>I&rsquo;d like for the plan issues to effectively show issues and discussions</td> </tr> <tr> <td>hestenet (he/him)</td> <td>(I'm starting an issue here)</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Just a basic outline, but we can add to it: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-6"><a href="https://www.drupal.org/project/distributions_recipes/issues/3317475" title="Status: Closed (works as designed)">#3317475: [Policy] Can we adopt standards for interoperability of recipes and to prevent conflicts and duplication?</a></span></td> </tr> <tr> <td>nerdstein</td> <td>Can we link that to our track 1 plan if not already?</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Done</td> </tr> </table> <h2>7&#65039;&#8419; Planned end-date for Drush Make packaging on Drupal.org in November- need to make sure distro maintainers are informed and have a path forward.<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/infrastructure/-/work_items/3266927" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/infrastructure/-/work_items/3266927</a></span>&nbsp;(edited)&nbsp;</h2> <table> <tr> <td>hestenet (he/him)</td> <td>Raised by @kreynen&nbsp;I also talked to a few people still maintaining D7 distributions on Drupal.org at BADCamp who weren&rsquo;t aware of the goal to end packaging with drush make on Drupal.org. I have to on my TODO list for this week to open issues in all active D7 distribution projects this week.</td> </tr> <tr> <td>hestenet (he/him)</td> <td>What is the standard message we want to give to these maintainers about how they should handle their distros moving forward?Can we include that in any of our comms?</td> </tr> <tr> <td>kreynen</td> <td>There are lots of options. Some better than others. The easiest one is ugly. Simply run drush make locally and commit the result. This would happen when people didn&rsquo;t understand how to use drush make. It&rsquo;s not ideal, but the resulting tar/zip is the same.</td> </tr> <tr> <td>hestenet (he/him)</td> <td>@drumm this issue has kind of snuck up on us, timing-wise, want to raise on your radar here as well.can't believe it's almost november</td> </tr> <tr> <td>drumm</td> <td>22 projects have made drush-make packaged release in the last yearMariaDB [drupal]&gt; SELECT nid, title, from_unixtime(max(changed)) last_release FROM (SELECT n_p.nid, n_p.title, n.changed FROM node n INNER JOIN field_data_field_release_files fdf_rf ON fdf_rf.entity_id = n.nid INNER JOIN field_data_field_release_project fdf_rp ON fdf_rp.entity_id = n.nid INNER JOIN node n_p ON n_p.nid = fdf_rp.field_release_project_target_id AND n_p.type = 'project_distribution' WHERE n.status = 1 AND n.changed &gt; unix_timestamp(date_sub(now(), INTERVAL 1 YEAR)) GROUP BY n.nid HAVING count(1) &gt; 2 ORDER BY n.changed) q GROUP BY nid;<br> +---------+--------------------------------------------+---------------------+<br> | nid | title | last_release |<br> +---------+--------------------------------------------+---------------------+<br> | 195997 | Hostmaster (Aegir) | 2021-11-09 22:00:08 |<br> | 644536 | Localized Drupal Distribution | 2022-09-10 13:55:48 |<br> | 681432 | Open Atrium | 2022-03-28 19:28:47 |<br> | 685884 | Media Development Profile | 2022-04-07 15:34:52 |<br> | 912086 | Recruiter | 2022-08-15 21:09:23 |<br> | 1079066 | Commerce Kickstart | 2022-08-04 21:10:12 |<br> | 1484528 | Panopoly | 2022-07-28 17:31:33 |<br> | 1592456 | Guardr | 2022-02-20 19:00:09 |<br> | 1700356 | Opigno LMS | 2022-07-21 09:29:51 |<br> | 1813432 | OpenFed | 2022-10-03 11:44:53 |<br> | 1972380 | Web Experience Toolkit (7.x) | 2022-03-07 18:30:31 |<br> | 2168035 | Campaignion Starterkit | 2022-09-13 13:10:38 |<br> | 2208549 | farmOS | 2022-02-16 18:16:21 |<br> | 2235853 | Drupal voor Gemeenten | 2022-08-04 06:18:52 |<br> | 2289589 | Responsive blog theme installation profile | 2022-08-05 09:25:28 |<br> | 2366707 | GovCMS | 2022-08-08 04:39:23 |<br> | 2797589 | Dimpact WIM | 2022-07-28 06:48:51 |<br> | 2850014 | Food Delivery Profile | 2021-12-03 10:24:23 |<br> | 2859174 | Seeds - Drupal Starter Kit | 2021-12-09 10:20:05 |<br> | 2859216 | Druppio - Small Business Distribution | 2022-01-21 12:19:16 |<br> | 2990842 | Real Estate Landing Profile | 2022-08-05 09:26:15 |<br> | 3069523 | WeeShop | 2021-12-19 03:43:29 |<br> +---------+--------------------------------------------+---------------------+<br> 22 rows in set (0.031 sec)</td> </tr> <tr> <td>drumm</td> <td>Bit better ordered by dateMariaDB [drupal]&gt; SELECT nid, title, from_unixtime(max(changed)) last_release FROM (SELECT n_p.nid, n_p.title, n.changed FROM node n INNER JOIN field_data_field_release_files fdf_rf ON fdf_rf.entity_id = n.nid INNER JOIN field_data_field_release_project fdf_rp ON fdf_rp.entity_id = n.nid INNER JOIN node n_p ON n_p.nid = fdf_rp.field_release_project_target_id AND n_p.type = 'project_distribution' WHERE n.status = 1 AND n.changed &gt; unix_timestamp(date_sub(now(), INTERVAL 1 YEAR)) GROUP BY n.nid HAVING count(1) &gt; 2 ORDER BY n.changed) q GROUP BY nid ORDER BY last_release;<br> +---------+--------------------------------------------+---------------------+<br> | nid | title | last_release |<br> +---------+--------------------------------------------+---------------------+<br> | 195997 | Hostmaster (Aegir) | 2021-11-09 22:00:08 |<br> | 2850014 | Food Delivery Profile | 2021-12-03 10:24:23 |<br> | 2859174 | Seeds - Drupal Starter Kit | 2021-12-09 10:20:05 |<br> | 3069523 | WeeShop | 2021-12-19 03:43:29 |<br> | 2859216 | Druppio - Small Business Distribution | 2022-01-21 12:19:16 |<br> | 2208549 | farmOS | 2022-02-16 18:16:21 |<br> | 1592456 | Guardr | 2022-02-20 19:00:09 |<br> | 1972380 | Web Experience Toolkit (7.x) | 2022-03-07 18:30:31 |<br> | 681432 | Open Atrium | 2022-03-28 19:28:47 |<br> | 685884 | Media Development Profile | 2022-04-07 15:34:52 |<br> | 1700356 | Opigno LMS | 2022-07-21 09:29:51 |<br> | 2797589 | Dimpact WIM | 2022-07-28 06:48:51 |<br> | 1484528 | Panopoly | 2022-07-28 17:31:33 |<br> | 2235853 | Drupal voor Gemeenten | 2022-08-04 06:18:52 |<br> | 1079066 | Commerce Kickstart | 2022-08-04 21:10:12 |<br> | 2289589 | Responsive blog theme installation profile | 2022-08-05 09:25:28 |<br> | 2990842 | Real Estate Landing Profile | 2022-08-05 09:26:15 |<br> | 2366707 | GovCMS | 2022-08-08 04:39:23 |<br> | 912086 | Recruiter | 2022-08-15 21:09:23 |<br> | 644536 | Localized Drupal Distribution | 2022-09-10 13:55:48 |<br> | 2168035 | Campaignion Starterkit | 2022-09-13 13:10:38 |<br> | 1813432 | OpenFed | 2022-10-03 11:44:53 |<br> +---------+--------------------------------------------+---------------------+<br> 22 rows in set (0.033 sec)</td> </tr> <tr> <td>drumm</td> <td>I&rsquo;d push back actually EOLing it at least 4 weeks after they&rsquo;ve been notified via an issue</td> </tr> <tr> <td>kreynen</td> <td>Letting the EoL slide was always a likely possibility&hellip; but if we never picked a date we wouldn&rsquo;t feel any pressure to move in this direction. In addition to the fact that Drush Make is no longer supported, there&rsquo;s also the scary legacy of the allow listed url patterns. There are several patterns that allow domains that are no longer used to host the projects on <a href="https://www.drupal.org/packaging-whitelist">https://www.drupal.org/packaging-whitelist</a>. I have no idea if the developers in the project still own the domain and just moved the project or the project died and they let a domain squatter get control, but cleaning that up would be a lot of effort.</td> </tr> <tr> <td>hestenet (he/him)</td> <td>+1 to Neil's suggestion about '4 weeks from issue' and - yeah would be awesome to get those issues opened. Thank you @kreynen</td> </tr> <tr> <td>hestenet (he/him)</td> <td>We should try to finalize the language to go in that issue, that'd be good to share with the group here and maybe get feedback from some of the maintainers who are already in the loop</td> </tr> <tr> <td>kreynen</td> <td>@hestenet (he/him) <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/infrastructure/-/work_items/3266927" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/infrastructure/-/work_items/3266927</a></span> captures the why, but doesn&rsquo;t answer the &ldquo;what to do now&rdquo;</td> </tr> <tr> <td>hestenet (he/him)</td> <td>@rszrama - maybe you have some thoughts for that issue on what kind of instructions we should include for distro maintainers, from what y'all have been thinking about for commerce?</td> </tr> </table> <h2>8&#65039;&#8419; I wanted to discuss the overlap with project browser &nbsp;(edited)&nbsp;</h2> <table> <tr> <td>hestenet (he/him)</td> <td>Why don't you give this thread an 8&#65039;&#8419;&nbsp; and we can make it official &#128578;</td> </tr> <tr> <td>nerdstein</td> <td>Done :)</td> </tr> <tr> <td>nerdstein</td> <td>@chrisfromredfin and I were having a brief discussion. I want to get to a point where we have any issues documented and captured in the plan to achieve track 3 noted above</td> </tr> <tr> <td>chrisfromredfin</td> <td>I DM'd @nerdstein recently but putting here for posterity - I think the best way to implement this is as a backend plugin inside of PB, but we're open to other alternatives.</td> </tr> <tr> <td>bsnodgrass (he/him)</td> <td>lost in the threads... @nerdstein and @chrisfromredfin are&nbsp; you referring to #3, third bullet?core installer: installation, replace standard/umami/etc (needs a plan)to clarify what "this" is :wink:&nbsp;(edited)</td> </tr> <tr> <td>nerdstein</td> <td>Yes</td> </tr> <tr> <td>nerdstein</td> <td>Harness PB&rsquo;s installation to load recipes</td> </tr> <tr> <td>nerdstein</td> <td>@hestenet (he/him) is there an issue to create a recipe project type</td> </tr> <tr> <td>chrisfromredfin</td> <td>I think we still need the one I just created in distributions_recipes but I would welcome one and all to look at and comment / revise it - <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-6"><a href="https://www.drupal.org/project/distributions_recipes/issues/3317471" title="Status: Closed (works as designed)">#3317471: [PP-1] Define a new project type for drupal.org</a></span> - and then we can move this to the d.o webmaster's queue when we think we have a solid proposal, so they can do the buildout. Again, big question mark in there is whether we just do this on @fjgarlin&rsquo;s D9 d.o site... as it's at least 50% for PB integration...</td> </tr> <tr> <td>chrisfromredfin</td> <td>Next question - I'm not sure 100% architecturally, but if we assume all this goes into core, will Recipes be a core module? If so, it makes sense for Recipes to provide the plugin to Project Browser. However, we could also put the plugin in PB (and/or at least develop it there). Any thoughts on where it should live? I guess I'm wondering which queue to put it in first, and my inclination is to put it in distrib_recipes'</td> </tr> <tr> <td>nerdstein</td> <td>Distrib recipes project is basically a clone of core</td> </tr> <tr> <td>nerdstein</td> <td>With plans to merge it in when it&rsquo;s ready</td> </tr> <tr> <td>chrisfromredfin</td> <td>right.</td> </tr> <tr> <td>nerdstein</td> <td>We can effectively make sure it pulls in the PB plug-in system and then it&rsquo;s part of the merge when recipes is ready</td> </tr> <tr> <td>chrisfromredfin</td> <td>but it's mostly like... a core patch, right? Or will there be a "recipes module" to turn on?</td> </tr> <tr> <td>chrisfromredfin</td> <td>Basically we need a src/Plugin/project_browser/source plugin or something to that effect.</td> </tr> <tr> <td>chrisfromredfin</td> <td>actually a&nbsp; src/Plugin/ProjectBrowserSource/Recipes.php specifically</td> </tr> <tr> <td>nerdstein</td> <td>Let&rsquo;s just capture what PB needs for it&rsquo;s plug-in and go from there</td> </tr> <tr> <td>chrisfromredfin</td> <td>k</td> </tr> <tr> <td>chrisfromredfin</td> <td>I've gotta scoot but the very next thing I think is having that available as a composer project type... like we have drupal/library and drupal/theme and drupal/module, we need to have a drupal/recipe project type so that we can composer require drupal/news_recipe</td> </tr> <tr> <td>chrisfromredfin</td> <td>also wondering if that composer needs its own namespace, like composer require drupal-recipe/news</td> </tr> <tr> <td>chrisfromredfin</td> <td>cuz then you couldn't have a theme called 'news' and a recipe called 'news' if you didn't have that</td> </tr> <tr> <td>hestenet (he/him)</td> <td>That can be accommodated with the 'general' project type right now, and we've discussed some ideas for that</td> </tr> <tr> <td>hestenet (he/him)</td> <td>But more dedicated types might be worth revisiting at some point</td> </tr> <tr> <td>nerdstein</td> <td>I prefer a dedicated type so people have the right semantic meaning</td> </tr> </table> <p>Participants:</p> <p>bsnodgrass (he/him), kreynen, Shefali, bircher, nerdstein, Marios Anagnostopoulos, thejimbirch, Warped, dimkritsotakis, hestenet, dinarcon, nedjo, leslieg, drumm, chrisfromredfin</p>