This meeting:
➤ Is for distribution developers, initiative contributors, the Drupal Association and anyone interested in the initiative.
➤ Usually happens every other Tuesday at 1600 UTC.
➤ Is done over chat.
➤ Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!
➤ Has a public agenda anyone can add to.
➤ *Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.

Comments

markie created an issue. See original summary.

markie’s picture

0️⃣ Who is here today? Comment in the thread below to introduce yourself and tell us why you are joining us.

Jim Birch :wave:
Bob Snodgrass (he/him) Good Morning Jim!
Bob McDonald Good morning.  Still lurking.
Rajab Natshah Hello everyone, Rajab, Joining to learn more about all new changes with recipes
Tim Lehnen Tim from the DA trying to check-in while double booked :sweat_smile:
eclipsegc Howdy!
Mark Casias ohai
Brian Gilbert :wave:
Amjad Amjad, AU

1️⃣ 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.

Bob Snodgrass (he/him) We had some Topics from last meeting to consider. Any word from @alexpott, I see he is online. Hopefully refreshed and not too buried with catching up on all the things
Jim Birch @bsnodgrass (he/him) I believe I covered all the topics from last week to consider.  Please let me know if I missed any.
Tim Mallezie IMO the unpacking of composer in a recipe #3355485: Dependencies should be 'unpacked' to the root composer.json and merged/resolved is sort of a blocker before really switching parts of a distribution / install profile to recipes. But does this initiative also sees this as a blocker? Since recipes are one-off install things, this is how i see this for being able to create recipes with predefined 'standard' contrib and settings.
Jim Birch Created #6 for you.

2️⃣ Model core's standard install profile as recipes #3301370

Jim Birch #3301370: Model core's standard install profile as recipes
Jim Birch I made some progress on this, and am getting closer.
Jim Birch Some things that are in the Standard profiles module that adds additional functionality that may not be configuration. * Assign user 1 the "administrator" role. * Populate the default shortcut set. * * Add content - internal:/node/add * * All content - internal:/admin/content * Sync the contact.form.feedback recipient to `site_mail`
Jim Birch and
Jim Birch standard.links.menu.ymlstandard.front_page: title: 'Home' route_name: '' menu_name: main1. This assumes there is a main menu right? Or would this create it also? 2. I don't think we can do this in config. Content maybe?
Bob Snodgrass (he/him) I was looking at that yesterday trying to wrap my head around how to contribute to that issue.
Jim Birch Installing the recipes would help, I don't think anyone has qa's them yet.
Bob Snodgrass (he/him) As we find issues, should we create child issues for #3301370?
Jim Birch On the issue is fine, or inline on the merge request.

3️⃣ Our maintainer has been on sabbatical for a few months.  Any updates on his availability with regards to this intitiative?

Jim Birch I DM'd on Slack to ask for an update since no one else knew.
Jim Birch Update.  Alex hopes to be back up to date by the next meeting.
Bob Snodgrass (he/him) Yay!

4️⃣ How will recipes will be listed/grouped on drupal.org?

Bob Snodgrass (he/him) Is there an issue for this yet? Who needs to be involved in the decisions?I know the Project Browser team has an interest and certainly infrastucture needs to be involved.
Jim Birch I am not sure if there is an issued, but we spoke briefly with @drumm it Pittsburgh, and he said if there could be an existing content type on drupal.org that could be used, it would be better for them.
Rajab Natshah I'm with having a category titled "Recipes" - any profile, module could choose to add it to the projectTo drop the use of Update Helper, or any custom recipe factory like our ConfigBits or Module Installer Factory(edited)
Neil Drumm Before getting into details like whether its a content type or field that labels what’s a recipe - what’s the big picture? Is there anything needed other than a list of recipes? Are there any filters or properties that would be useful in the future? Are we expecting 10s, 100s, or thousands of recipes? Other than browsing & repositories, what do people using recipes need, like what are the steps to getting one on a site?
Rajab Natshah If recipes was committed to Drupal Core 11 for exampleWe may switch all config in our starterkit profile into recipes. And the update config management too.A profile or a product for projects could manage 50 to 100
Jim Birch Thanks @drumm.  I think we should open an issue with these questions.

5️⃣ [META] Recipe maintainer and end user documentation

Jim Birch #3375542: [META] Recipe maintainer and end user documentation
Rajab Natshah Having a clear Config Script cscript as .cs or Recipe Script rscript  as .rs is important.    ( .yml ) will do for sure
Jim Birch Recipes have a file in them called recipe.yml
Jim Birch Here is a good example of a recipe https://gitlab.com/kevinquillen/drupal-base
Rajab Natshah Maybe then it could be auto indexed with a fixed category if the file is in the project.
Rajab Natshah This may do better, than following with projects which did not tag or add the category filter.
Rajab Natshah At this time I see that Drupal maybe is in need of new list of extensions
Rajab Natshah likeComponentsRecipes
Rajab Natshah Both could have their ecosystem ( like modules, themes )
Rajab Natshah I'm only dreaming :sweat_smile:

6️⃣ Unpacking recipes to root composer

Jim Birch @mallezie :IMO the unpacking of composer in a recipe #3355485: Dependencies should be 'unpacked' to the root composer.json and merged/resolved is sort of a blocker before really switching parts of a distribution / install profile to recipes. But does this initiative also sees this as a blocker? Since recipes are one-off install things, this is how i see this for being able to create recipes with predefined 'standard' contrib and settings.
Jim Birch I believe it is a want on the roadmap to have this as a part of Recipes, but I don't see it as a blocker currently as this package is currently working.https://github.com/woredeyonas/Drupal-Recipe-Unpack
Jim Birch You mentioned on the thread linked above:"Was wondering if we could just pull in symfony/flex and then use the symfony unpack command.https://github.com/symfony/flex/tree/2.x/src/Unpack"I just want to point our that the "we" in this initiative is a very small group.
Jim Birch If we could get eyes from a few other developers on the direction of that, and the direction of Yonas' approach, that would be helpful.
Tim Mallezie Thank you for the explanation. I'll try to find time to test more things in the issue and jump in. Sorry if I misphrased the 'we', did not want to put pressure on someone, I'm aware it's all a small group of volunteers, with time constraints. My main question was if others think also that it is something needed and think the same.
Jim Birch Yes.  It is on the roadmap in the code base under Phase 2.https://git.drupalcode.org/project/distributions_recipes/-/blob/1.0.x/do... 2Main aims are to create a user interface for applying recipes and manage recipes via composer.TBD, includes:Building UI for applying recipesHosting recipes on Drupal.orgDiscovery by some toolDrupal recipe testingCreate composer plugin react when a drupal recipe is installed to unpack the recipe's dependencies and copy it to PROJECT_ROOT/recipes

Participants:

Jim Birch, Bob Snodgrass (he/him), Bob McDonald, Rajab Natshah, Tim Lehnen, eclipsegc, Mark Casias, Brian Gilbert, Amjad

hestenet credited bircher.

hestenet credited vermario.

hestenet’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.