Hey @WG-triage those who are around, (delayed) meeting :smile:
sorry about the delays, got stuck with some work but free now :grinning:
first of all, as usual thank you for all your efforts in triaging and helping. still trying to work on getting the number of pull requests down and most of them moving faster than they are, but most are stuck on people trying to find the bandwidth so there isn't much we can do about it
now given it is december, a.k.a. holiday season, we normally take a break from triaging during the holiday break since most people will be away and i'm assuming you folks need a break as well
/me is planning to take over the PR queue while other people are on break image.png
so we will take a break from 21st December to 3rd January (2 weeks)
you don't need to triage during those 2 weeks even though we have a release scheduled for 31.12 :upside_down:
we can resume triage on 04.01
(meanwhile i just got a calendar reminder for this meeting, looks like i still need to fix the calendar ;P )
also if you need a longer break during the holiday break, that's not a issue, you can skip triaging the weeks before or after we take a break
and yes joshua you are free to take over the pr queue :stuck_out_tongue: just don't ping anyone that should be fine
moving on -
we don't usually ping members if their prs are waiting on them to make changes, the problem i see here is the "definition of a member"
most of you look at the "member" badge github adds to the user's name on the right when they open a pr / comment, however it isn't accurate
referring to: image.png
i would say we could be "stricter" by hovering over the user and seeing if th ey belong to any of the main rust teams (such as t-libs, t-compiler, t-lang, etc) and not pinging them, but if they belong only to a working group, then it is fine to ping them
unfortunately, i can't find an example right now
but it is fine if you ping anyone who belongs only to a working group or a sub-team and not the main team
i think that is it from my side, anyone has anything to add?
That's good to know. Thanks
nothing from my side.
Same here, nothing to add
yeah we know that members often are working on multiple prs and also need time to review pull requests, and often the pull requests they work on are complex enough that it requires a longer time
speaking of which, I finally got around to https://github.com/rust-lang/rust/pull/76467 after like 3 months :laughing:
that should be it for today, thanks for attending and have a safe and happy holiday season :smile:
happy holidays everyone :)
next meeting should be on , as usual if you have anything to add before that, you can add it to the agenda doc or make a thread here
thanks everyone :smile:
Sorry I missed the meeting today! I'll read through the chat history.
@WG-triage just an update:
yest at the t-release meeting we decided to have a longer break this year.
So instead of the holiday break lasting till 03.01 as we decided on Wednesday, it will now be till 10.01
Also January's meeting will be moved to 13.01.2021 instead of 6th.
Last updated: Jan 26 2022 at 08:46 UTC