Coding Standards Meeting Wednesday 2024-04-10 0900 UTC

Item for discussion, didn't want to raise a separate issue for it. Suggested update to the project page, see attached screen grab.

1. Needs an line explaining what the links are
2. Can the links be a in a larger font? they are major important parts of the project, but do not stand out
3. The one line of text about PHP could be moved to the linked page. It is odd that PHP has some extra words here, but the other sections/links do not. Better to have just clean links here, with the words on the linked pages.

#3099562: [Policy] Consider creating coding standards depended on specific PHP versions →
#2689243: Import classes used in annotations →

Thank you for making the changes from #2

Thanks also for fixing the issue summary in #5. I saw that it was created with the default template. Is there an option for a project to have alternative templates? Or do you just keep this standard meeting text somewhere to copy/paste? Or do you take it from the previous meeting? Useful for others to know, to avoid work fixing things.

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.

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️⃣ Approve minutes for previous meeting(s)

3️⃣ Fixed since last meeting

4️⃣ RTBC issues

4️⃣.1️⃣ #3295249: Allow multi-line function declarations →  (edited) 

4️⃣ .2️⃣ #3339746: Decide on a coding style for PHP Enumerations →  (edited) 

4️⃣.3️⃣ #3074131: Use null coalescing operator ?? instead of a ternary operator with an isset() condition →  (edited) 

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

5️⃣ New issues

5️⃣ . 1️⃣  #3439004: Coding standard for attributes →

5️⃣ . 2️⃣ New activity on needs review issue 📌 Coding standards for "use" statements RTBC

6️⃣ via @Jonathan1055 suggesting updates to the project pageItem for discussion, didn't want to raise a separate issue for it. Suggested update to the project page, see attached screen grab.Needs an line explaining what the links areCan the links be a in a larger font? they are major important parts of the project, but do not stand outThe one line of text about PHP could be moved to the linked page. It is odd that PHP has some extra words here, but the other sections/links do not. Better to have just clean links here, with the words on the linked pages.

7️⃣ via @quietone #3099562: [Policy] Consider creating coding standards depended on specific PHP versions →

8️⃣ via @quietone #2689243: Import classes used in annotations →

9️⃣ via me :smile: #3360160: Stop using FQCN in PHPDoc annotations →

Participants:

Kingdutch, larowlan, Alex Skrypnyk, quietone, catch, urvashi_vora, bbrala, kim.pepper, dww, borisson_, Jonathan1055, mstrelan

@Kingdutch, thanks for recording the minutes. We put them in the Issue Summary so they are easy to find. I'll do that now.

longwave → credited catch → .

longwave → credited dww → .

longwave → credited kim.pepper → .

longwave → credited mstrelan → .

longwave → credited urvashi_vora → .

longwave → credited bbrala → .

longwave → credited borisson_ → .

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