| Griffyn Heels | :wave: Griff, Aus |
| pameeela | :wave: Pam, currently in Brisbane, AUS |
| quietone | Hi |
| Akhil Babu | Akhil, India |
| larowlan | :wave: Lee |
| mstrelan | :wave: Michael, always in Brisbane, AUS (edited) |
| mohit_aghera | :wave: Mohit, India |
| atul ghate | :wave:Atul, India |
| jibran | Jibran, Syd, AU |
| lendude | Len, Amsterdam |
| Tinto | Thijs, currently in Kuala Lumpur, Malaysia :flag-my: :blob_wave: |
| Kristen Pol (she/her) | Kristen, California, catching up |
| Griffyn Heels | Holidays were great, didn’t rain nearly as much as I’d feared. Lots of sun and cricket! |
| pameeela | Went to NZ and had great weather. Even swam i Lake Wanaka! |
| quietone | I had lots of alone time to recharge. |
| lendude | Got a couple of hundred hours of Dwarf Fortress in between all the family stuff, so pretty good :wink: |
| Tinto | Went back to the island of Penang in Malaysia where I did an exchange semester more than 20 years ago. Caught up with an old friend and shared stories about our days living on campus. Sweet memories. |
| Kristen Pol (she/her) | We had our first vacation in 3.5 years! Spent almost a month in Australia… Sydney, Tassie and Melbourne… had a great time except for 3 of us separately seeing 3 Tiger snakes on the same day :scream: (edited) |
| quietone | Add "Set to RTBC when passed core gates" to the remaining tasks in the standard template |
| pameeela | Possibly a silly question but is there any established etiquette for PMNMI issues, as far as coming in and closing one that someone else postponed, with a timeframe? |
| Kristen Pol (she/her) | Wondering if anyone is doing any special bugsmash contribution for Global Contribution Weekend? |
| pameeela | I was able to triage all of the remaining Bartik issues in the core queue. |
| quietone | I was able to do a reroll that catch asked for and soon after a 12 yr old was committed (edited) |
| mohit_aghera | #3105643: "More link" does not take display arguments into account |
| Tinto | Organised another Drupal contribution meetup in Malaysia and presented about the Bug Smash Initiative. Helped one new contributor triage and close his first core issue. :tada: Closed several PMNMI issues myself. |
| Kristen Pol (she/her) | Properly took a vacation and ignored contribution for a month :joy: |
| pameeela | Thanks to @quietone for doing all of the organising -- I wouldn't have known about the Bartik triage but for the work she did to make it easy! |
| quietone | And credit due to @pameeela for triaging all the bartik issues. |
| mstrelan | Thanks to @quietone for transcribing my thoughts I vomited on Slack threads in to issue tags, status updates and comments on issues. |
| Kristen Pol (she/her) | Thanks to all who made D10 happen :tada: |
| lendude | Usually I can spend some left over training budget in December, but got dragged into a pitch for a new client which ate up all my time. Waay outside my comfort zone, so good learning experience I guess, but not what I planned :shrug: |
| Tinto | Client work (as usual). |
| Kristen Pol (she/her) | Vacation :beach_with_umbrella: |
| quietone | Priority (goal): actual Critical (50): 62 Major (1000): 920 Normal (6000): 4633 Minor (300): 335 Total: 5950 |
| Griffyn Heels | Is there any way to compare this to beginning of ’22? |
| quietone | I don't see it in the minutes for Jan or Feb last year. |
| Griffyn Heels | Ah bummer |
| mstrelan | You can try search this channel for "Priority (goal): actual" and sort by date, the oldest one is May 10 2022 - https://drupal.slack.com/archives/C014QES6HSQ/p1652157706123939?thread_t... |
| Griffyn Heels | Good thinking chickens, here’s the first one I can see in ’22 |
| Griffyn Heels | https://drupal.slack.com/archives/C014QES6HSQ/p1642717451091100 |
| Griffyn Heels | hmm, different structure |
| quietone | Today: 2023-01-17
From: 2022-12-06 to 2023-01-17 All bugs Status Count Approximately 453 yr reduction in total number of years of all open bugs. Only bugs tagged Bug Smash Initiative Status Count Approximately 306 yr reduction in total number of years of all open bugs.(edited) |
| quietone | Note the above is for 6 weeks. |
| quietone | I originally pasted incorrect results. These are not correct for the 6 week period. |
| lendude | We had a small discussion on one of the triage issues about maybe setting some targets to fix this YEAR. The two week period seems too short for some of the really hard ones out there |
| Griffyn Heels | That's a good idea, I'll bring this up in the next meeting. I'm not sure how effective the targets have been so far.Open to feedback on changing the process. |
| lendude | A number have crept over the year mark since last update, so probably worthwhile to take a look at |
| quietone | It would just be nice to not have to constantly update the remaining tasks to say something like this. |
| quietone | I would much rather make a comment referring to the Issue Summary than having to comment the say thing about core gates all the time. |
| quietone | I think we should be encouraging people to read and use the issue summary. |
| pameeela | I saw some but hesitated to do it :slightly_smiling_face: |
| quietone | As usual, it depends. |
| quietone | The older/stale ones may have a three month warning. For those, I think they can be closed but it is always best to check the comment by the person who added the three month warning. |
| quietone | For example. the warning could have been added to an issue that was created by a past committer but the commenter didn't know that. So, it is more likely that those issues need to stick around. |
| pameeela | i just meant as far as the person posting the three month warning would have first dibs on then closing |
| quietone | Oh I see. The only concern I have with that I can explain by example. Say that I add the three month warning to a stale front end issue. When the three months have passes I should not be the one to close it because it is more likely that I will miss something. |
| quietone | I have closed some that I added the three month notice too but I am cautious and often ask for someone to double check. |
| pameeela | ohhh i see. so you think it's better if someone else closes. |
| pameeela | that makes sense! |
| quietone | It is subjective based on the reviewer experience. I am much more confident closing migration issues than others. |
| borisson_ | I agree, having someone else close it feels safer because it reduces chance on missing something |
| lendude | Yeah, agree, have somebody else do it. (unless it happens to be your subsystem of choice, like @quietone, Views issues I have less trouble with closing myself) |
| Tinto | This is what I figured too. I’ll leave issues that I put on PMNMI alone, allowing for others to close it - and in the process, offer an extra pair of eyes / review. |
| Tinto | I think it’s good practice when you change an issue to PMNMI, to mention in the comment that “this issue may be closed after … months, preferably by someone other than me”. (edited) |
| Kristen Pol (she/her) | One related thing… if you close it and someone did the postponing and/or 3 month warning from bugsmash, I try to now include them in my comment on the triage issue since ideally they’d also get credit for their past work (edited) |
Participants:
Griffyn Heels, pameeela, quietone, lendude, Tinto, Kristen Pol, mohit_aghera, mstrelan, borisson_
Comments
Comment #2
griffynh commentedComment #11
larowlanComment #12
larowlanThese look good to me