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 monthly. 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.
| larowlan |
Hi |
| catch |
Sort of here. |
| bbrala |
im getting back into things, life is slowing down 🙂 |
1️⃣ What topics do you want to discuss? Post in this thread and we’ll open threads for them as appropriate.
| quietone |
Change to monthly meetings |
| larowlan |
Process for stepping down from the committee |
2️⃣ Action items
2️⃣.1️⃣ Approve minutes for previous meeting(s)
2️⃣.2️⃣ TBD
3️⃣ Switch to monthly meetings
| quietone |
Initially fortnight helped deal with the backlog and the challenges of re-activating the committee. |
| quietone |
Now that work is done we should switch to less often and monthly is the standard, so lets go to monthly. |
| larowlan |
This feels sensible |
| catch |
Makes sense to me there are usually only 1-3, issues to discuss so if that goes to 3-6 it would still be manageable. |
| quietone |
That would move the next meeting to the 1st week of December. Do we want to keep it on the first week, or switch to a different week? |
| borisson_ |
For december that would be fine, but I doubt a lot of people would be around in the first week of january 🙂 |
| bbrala |
agree with monthly |
4️⃣ Process for stepping down from the committee
| larowlan |
I don't feel I'm giving the role the time it requires and feel it would be best to make way so someone else can |
| quietone |
Thanks for your contributions! |
| quietone |
And thanks for bringing this up. What policy do we have for appointments? |
| larowlan |
I think some of us were added as part of being in the TWG |
| larowlan |
I guess we could ask for applicants |
| quietone |
So, like subsystem maintainers, we self nominate for stepping down? |
| larowlan |
I guess so? |
| quietone |
Does this also mean to step down from the TWG? |
| larowlan |
I think that is via role as FM, there are no meetings etc for that, so I don't feel like I'm letting anyone down |
| quietone |
Thanks for making that clear. |
| quietone |
That means, that the process is that the person who wants to step done does at their own request, which means to open an issue. |
| quietone |
The proposed job description will change that to a yearly renewal process. |
| bbrala |
all understandable @larowlan 🙂 |
5️⃣ Coding standards team job description
| quietone |
Work on this is at https://docs.google.com/document/d/1612Bx_qBQJaqkkNeAvoeHZjBg3QBKybq8aXA... |
| quietone |
One thing to be aware of here is that this is defining an initial term of two years with annual renewal. |
| quietone |
This also needs to be moved to the committee resources. And that needs a URL. |
| quietone |
What should the URL be? |
| quietone |
Do we all agree to the job description? |
| bbrala |
description seems pretty fine, read it earlier also.Annual renewal, how would that work. One gets asked to renew and if not removed? I mean, this could mean less inactive people ofcourse, which could be good. Also; this would also mean we should keep a membership list with join date on the project page opr a doc page i think. Keep a list of current and old memebers. |
Participants:
quietone, larowlan, catch, borisson_, bbrala
Comments
Comment #6
quietone commentedComment #7
quietone commentedComment #8
quietone commentedComment #9
borisson_Comment #10
quietone commentedComment #11
quietone commented