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, @larowan, @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.
| mstrelan |
Michael, Australia |
| larowlan |
:wave: |
| mahaveer003 |
:wave: |
| catch |
Nat, UK |
| Kingdutch |
:wave: |
| Björn Brala (bbrala) |
:upside_down_face: |
| dww |
Derek :wave: |
| Aaron McHale |
Oh the meeting is 9am my time, I thought it was 9pm for some weird reason :smile: (edited) |
| Aaron McHale |
I wasn't clear if the meeting is in the core calendar? Can anyone confirm (I don't use Google Calendar so can't easily check) |
| longwave |
:wave: |
| quietone |
Hi, catching up. |
1️⃣ Do you have suggested topics you are looking to discuss? Post in this thread and we’ll open threads for them as appropriate.
2️⃣ Action items
2️⃣.1️⃣ Approve previous minutes
2️⃣.2️⃣ TBD (edited)
| mstrelan |
Sorry this is the same as 3.1 |
2️⃣.3️⃣ TBD
3️⃣ RTBC issues to review
| larowlan |
I think there's broad consensus amongst members here, so next step is to get +1 from committers |
| mstrelan |
The IS talks about two different things, the position and the spaces. I'm confused if there is consensus on the spaces. |
| larowlan |
I think there's consensus around no spaces, matching PSR 12 |
| larowlan |
Do folks agree? |
| catch |
No spaces is what everyone is doing, so I think we should use that. I think the idea about adding spaces was to make things easier for coder in other places where we require spaces, but that doesn't seem like a reason to diverge from what humans are naturally doing. |
| larowlan |
And there's already a coder rule for both flavours |
| dww |
So, committee is agreed? Next step is the blog post and the waiting? |
| quietone |
I've updated the IS and commented with a link to the issue for the blog post. |
| larowlan |
+1 from me |
| Björn Brala (bbrala) |
Yeah same, read through it and agree |
| dww |
There’s some disagreement in the issue on if there should be an initial condition in the first line with the if or not. |
| dww |
We need to be clear what we’re agreeing with. :sweat_smile: |
| Björn Brala (bbrala) |
Hmm |
| Björn Brala (bbrala) |
I'll revisit later |
| Aaron McHale |
Added a comment |
| larowlan |
+1 from me |
| Björn Brala (bbrala) |
Same for me. Thinking if I need to comment then. |
| dww |
I’ve been +1 on this one for a long time. :sweat_smile: |
| Aaron McHale |
+1 from me! |
| quietone |
This one is also tagged for change record updates.I think that should be done before the announcement. |
| quietone |
Does anyone have time to look into that? |
| Björn Brala (bbrala) |
Tomorrow I might have |
| larowlan |
There's a lot of action items/open threads on the Google doc still |
| quietone |
I am not convinced that the background section should be in the standards either. I think the standards should simply state what is done now. |
4️⃣ Fixed since last meeting
5️⃣ Wrap Up!!That's all folks for the meeting facilitation. Keep chatting in the threads and feel free to add new ones.
| larowlan |
Thanks for running the meeting |
Comments
Comment #2
quietone commentedComment #3
quietone commentedFollow up on issues that were announced on 26 Oct.
#3074131: Use null coalescing operator ?? instead of a ternary operator with an isset() condition
#2961791: Update Help Text Standards Examples to Modify Heading Structure
From previous meeting
this is to be announced #3295249: Allow multi-line function declarations
this goes to core meeting #3324368: Update CSS coding standards to include PostCSS and Drupal 10
Comment #4
quietone commentedAnd followup to item 7 in #3397055: Coding Standards Meeting Wednesday 2023-11-07 2100 UTC
Comment #5
jonathan1055 commented#3303206: Define a standard for adding declare(strict_types=1) is RTBC which I think means it is ready for review at this meeting.
Comment #6
urvashi_vora commentedComment #7
urvashi_vora commentedComment #13
quietone commentedI reviewed this and didn't find any errors. I have added credit.
Comment #15
quietone commentedComment #16
urvashi_vora commentedLGTM. Moving to RTBC.
Comment #17
quietone commented@urvashi_vora, thanks
There has been no further comments, so setting to fixed.