Hello, everyone. Welcome to the :sparkle: CLI in Core Initiative :sparkle: Meeting! :calendar: This meeting:
➤ Usually happens weekly either at Wednesday 14:00 UTC or Wednesday 22:00 UTC.
➤ Will start synchronously for 30 minutes with an open agenda.
➤ Will then switch to threads to continue discussions.
➤ Please comment on the roll call thread throughout the day.

0️⃣ Roll Call! Who is here today? Introduce yourself including your name and drupal.org username. If you feel comfortable, mention something about yourself today such as listening to birds during meetings.

mradcliffe Matthew, mradcliffe (he/him). When I can, I try to join meetings from outside so that I have a "reality" background rather than a virtual background, which means that I get to listen to birds or crickets.
mradcliffe Synchronous attendees: @tekNorah, @mradcliffe, @moshe, @Thomas from Bluefly, @Jack Franks (he/him), @bircher, @penyaskito, @kerasai.
moshe moshe weitzman :wave:
mott Ryan Mott (u/rymo) :wave::skin-tone-2:
bircher bircher :wave:
Jack Franks (he/him) franksj :wave:

1️⃣#3582246: [meta] CLI in Core community initiative
1️⃣ 0️⃣ Issue credit organization.

mradcliffe We asked during DrupalCon whether we needed to have issues for meetings. bircher mentioned his experience with CMI2 and doing individual issues at the beginning before tapering off as another initiative took over. We asked ourselves whether the issues would only be for credits or also contain meeting notes, but did not make any decisions. mradcliffe mentioned that the notes for meetings, especially if duplicated from meeting to meeting, tend to clog up his search results. Opinions still needed on whether we should be doing this?
bircher I think it is good to have a record for the meetings that lives on drupal.org rather than slack. if things repeat it will be because they are talked about at several meetings. I sometimes used slack meeting minutes to find links to other issues.But I am not going to try to impose that. I don't "need" meeting issues as such.

1️⃣ 1️⃣ Meeting structure

mradcliffe We agreed on a flow of synchronous to asynchronous following the format of bringing notes from the meeting as Slack threads that can be worked on and updated for the next week.

1️⃣ 2️⃣ Sub-task organization.

mradcliffe We wanted a way to track tasks better than on drupal.org, but we are not on GitLab yet where this is possible. We will use the meta issue for managing tasks and adding child issues for items.
mradcliffe This is still kind ofpossible by pressing the "Add a Todo item" button on a merge request and visiting https://git.drupalcode.org/dashboard/todos regularly.

1️⃣ 3️⃣ Meetings

mradcliffe At the end of the meeting, we decided that instead of trying to do a synchronous -> asynchronous -> sychronous -> asynchronous flow in a 24 hour period that we would try switching the meeting time.mradcliffe has volunteered to attend both synchronous meeting times (except on the 1st wednesday of the month (UTC time, thursday Asia, Oceania), but is seeking anyone else whoh also is available.Next week’s meeting will be Wednesday 22:00 UTC / Thursday 09:00 AEDT.
Jack Franks (he/him) This is 1800 eastern, for super Americans like me? Oh well I guess if I was super American I would say 6pm :sweat_smile:

1️⃣ 4️⃣ Meta issue alignment

mradcliffe @Thomas from Bluefly volunteered to compare and align the meta issue write-up mradcliffe did with the spreadsheet document to get a polished MVP proposal. Anyone one else available to review?
bircher @mradcliffe could you please link that issue here?
mradcliffe https://www.drupal.org/project/drupal/issues/3582246
mradcliffe https://docs.google.com/spreadsheets/d/1L857AeGeAZw05bHtWpmuYR9W88S9Wnf4...

1️⃣ 5️⃣ Administrative setup and supporting roles

mradcliffe @tekNorah is seeking guidaince on how best that she can help out administratively. At the moment, she is volunteering for meeting attendance and organization, but it would be nice have multiple people available for things like creating Slack threads after meetings.
mradcliffe What I did. I reviewed the generated notes, both summary and details, and reorganized based on our initiative issues into a text editor. I created sub bullets for each discussion point.

2️⃣ #3453474: CLI entry point in Drupal Core (Dex)
2️⃣ 1️⃣ API documentation.

mradcliffe @Jack Franks (he/him) has volunteered to help this week, but seeking guidance and documentation.In the merge request, mradcliffe suggested adding a new defgroup "cli" in core.api.php.
bircher I think a cli group makes a lot of sense.
Jack Franks (he/him) I saw a notification flash and disappear - I didn't provide status for this here, but I did commit this change to the MR, just to keep here and the issue up to date!
Jack Franks (he/him) I should have updated the thread, I didn't think of it at the time
mradcliffe yeah, sorry, that was me, I realized I was reading your changes and not what was in main branch.

2️⃣ 2️⃣ Renaming test module and classes.

mradcliffe @moshe has volunteered to help this week, and is seeking anyone else who wants to also work on this.
moshe The task is to rename the dex_test module to console_test. In the main MR - https://www.drupal.org/project/drupal/issues/3453474. I'm happy to do it if nobody else wants to.
mott I can take a pass at this
mott done!

2️⃣ 3️⃣ Address merge request questions and reviews by @longwave and mradcliffe.

mradcliffe @moshe has volunteered to do this, and is seeking anyone else who wants to also work on this.
moshe The main MR is found at[#3453474]

2️⃣ 4️⃣ We confirmed that we did not want to include Drush Formatters in scope of the initiative. The meta issue needs to be updated as well.

mradcliffe .

2️⃣ 5️⃣ Ideal schedule: We want this RTBC and merged prior to Drupal Dev Days.

mradcliffe I think we can get this to Needs Review status in a week.
mradcliffe We probably want Needs product manager review and/or Needs framework review manager at that point so the core team can discuss and review.

Participants:

mradcliffe, moshe weitzman, rymo, bircher, franksj, tekNorah, flux423, penyaskito, kerasai.

Comments

mradcliffe created an issue. See original summary.

smustgrave’s picture

smustgrave commented
Status: Needs review » Fixed

Assigned credit for everyone listed above.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.