Coding Standards Meeting Tuesday 30 January 2024 21:00 UTC

Created on 12 January 2024, 9 months ago
Updated 18 April 2024, 5 months ago

Hello all, it’s time for the fortnightly coding standards meeting.

This meeting:
➤ Is for anyone interested in the Drupal coding standards.
➤ Is held on the #coding standards channel in Drupal Slack (see www.drupal.org/slack for information).
➤ Usually happens fortnightly. Alternating between Tuesday 2100 UTC and Wednesday 0900 UTC.
➤ The meeting open for 24 hours to allow for all time zones.
➤ Discussion is done 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 by adding a comment to the meeting issue.
➤ A transcript will be made using drupal-meeting-parser 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.
➤ The transcript will include comments made during the 24 hours of the meeting. However, comments made after the 24 hours may not be in transcript.

Current ping list: @catch, @larowlan, @longwave, @quietone
@dww, @borisson_ @longwave @Björn Brala, @Aaron McHale, @Alex Skrypnyk, @Urvashi, @Kingdutch

0️⃣ Who is here today? Comment in the thread to introduce yourself. We’ll keep the meeting open for 24 hours to allow for all time zones.

0️⃣.5️⃣ Share a highlight since our last meeting, which has been over the holiday period for most of us.

1️⃣ What topics do you want to discuss? Post in this thread and we’ll open threads for them as appropriate.

2️⃣ Action items

2️⃣.1️⃣ TBD

3️⃣ Fixed since last meeting

4️⃣.1️⃣ Step 5 #3074131: Use null coalescing operator ?? instead of a ternary operator with an isset() condition

4️⃣.2️⃣ Step 8 #3295249: Allow multi-line function declarations

4️⃣.3️⃣ Step 8 #3324368: Update CSS coding standards to include PostCSS and Drupal 10

5️⃣ Stale issue #1795750: Revise coding standards to use IETF RFC 2119 standards

6️⃣ Admin

6️⃣.1️⃣ Process update, #3405089: Refine CS process based on the experience of #3303206

6️⃣.2️⃣ Reminder to sign up for your turn at admin duties in our calendar

7️⃣ Wrap Up. That's all folks for the meeting facilitation. Keep chatting in the threads and feel free to add new ones.

8️⃣  Could we consider the Git history part of the "code" and spend some energy on improving the format of our commit messages?

quietone, Jonathan1055, dww, larowlan, mstrelan, mherchel, catch, dww, larowlan, kim.pepper

🌱 Plan
Status

Fixed

Component

Meeting

Created by

🇳🇿New Zealand quietone

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024