Agenda items

Standing items

  • Who is here
  • Any other suggested topics
  • Wins / Thanks / Frustrations
  • Statistics and functionality update. X new bugs created in last two weeks. Y closed by the initiative.
  • The bug I would most like to see fixed
  • Update on action items from last meeting
  • What should be the initiative focus for the next 2 weeks?

New items

  • @todo

Comments

dww created an issue. See original summary.

larowlan credited acbramley.

larowlan credited amjad1233.

larowlan credited catch.

larowlan credited jibran.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Status: Active » Fixed

Howdy and welcome to the third meeting of the Bug Smash community initiative :beetle::hammer::tada:
This meeting:
➤ Is for contributors who are interested in helping reduce the number of open bugs against Drupal 8 and Drupal 9 core.
➤ Usually happens every second Tuesday at 04:00 UTC.
➤ Is done over chat.
➤ Happens 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!
➤ Transcript will be exported and posted to a core issue for this meeting. 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.

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 timezones.

jibran Jibran, AU
acbramley :wave:
dww Derek, US, Black Lives Matter
pameeela here! Sunshine Coast, AU
pankaj.singh Hello everyone, Pankaj from IND
larowlan Lee, Aus
quietone Hi
Griffyn Heels Howdy, Griff, Aus
Indrajith KB Hi, Indrajith from India..
amjad1233 Amjadkhan, AU
Kristy Kristy, Melbourne AU
pratik_kamble Pratik, Pune India
jungle Jungle, from Chongqing, China
tr Tim, from Seattle
hansa11 Hi everyone! :wave:
Hansa, from India :slightly_smiling_face:
lendude Len, Amsterdam
hardik_patel_12 Hardik , India
Michael (g-brodiei) Michael, Taiwan
johnwebdev John, Sweden
himanshu_sindhwani Hi Himanshu, India
shaal Ofer Shaal, Florida :sunglasses:

1️⃣ Do you have suggested topics you are looking to discuss? Post in this thread and we’ll open threads for them as appropriate.

pameeela Initiative plans for DrupalCon contribution day?
Kristy I have a possible QA question. Some of the QA staff at Salsa are low on work so my immediate thought was they could do contribution for bugsmash, but I am unsure of the QA process for bugsmash and Drupal as a whole. From what I can tell, anything in `needs review` is essentially QA? Does this assume that a QA person needs to set up site locally, download the version of Drupal and version of the module the bug is reporting on, know how to apply a patch?
pratik_kamble Some of the JS people I know are looking to contribute in opensource. Does anyone have any JS related issues in mind.
dww What's our "official policy" [sic] as an initiative on tasks like test suite plumbing? I know we've tagged things for BSI that are features (e.g. the JS issue count thing), so I presume it's fine, but I'm thinking of tasks like https://www.drupal.org/project/drupal/issues/2702233

2️⃣ .1️⃣ Wins - what wins have you had this fortnight - share your successes!

acbramley https://www.drupal.org/project/drupal/issues/2914785 Commited to 9.1, 9.0, and 8.9. Cheers @larowlan!
larowlan We got the JS issue counts deployed to d.o - thanks to @drumm and @dww

2️⃣ .2️⃣ Thanks - a space for callouts to other contributors who’ve helped you this fortnight

jibran @berdir for helping with entity API related issues.
larowlan see 2️⃣ . 1️⃣
jibran In general, thank you for the initiative and everyone chipping in. It feels like I'm more involved in the bugs issue queue now.
Michael (g-brodiei) Thanks to @pameeela and @lendude for reviewing and closing the issue I posted and pointing out the correct guidance so I'll know how to deal with minor releases bugs in the future.

2️⃣ .3️⃣ Frustrations - what’s been a source of frustration this fortnight - a space to vent

pameeela rude replies from people who seem to think that open source projects owe them something :innocent:
amjad1233 :disappointed:

3️⃣ Core bug statistics - current state of open bugs

larowlan 67 bugs closed/fixed etc this fortnight with the Bug Smash tag
larowlan Unfortunately, 74 new bugs opened though, so we didn’t have a net gain this fortnight
jibran We might have committed no tagged bugs
jibran What is the triage plan for next fortnight?
pameeela keen to hear thoughts on this ^ last week i focused on 'needs screenshots' and 'needs steps to reproduce'

4️⃣ Bug I'd most like to see fixed

acbramley https://www.drupal.org/project/drupal/issues/3047022 and related
dww https://www.drupal.org/project/drupal/issues/2625136 since a) it's a horrible UX bug, b) it makes views with these kinds of exposed filters basically inaccessible and c) because it blocks a lot of other fixes in related areas.
tr There are hundreds of "small" bugs with patches that need review and can be committed. To me, this is where the most impact can be made - fix hundreds of things that have been hanging around the issue queue for years. Dealing with only one or two "major" issues is helpful, but won't make as much of an impact.
dww @tr: That might be a good point to make in 8️⃣ ...
dww Although, meta, it's all volunteer effort, there's really nothing "official" about anything "official". Folks work on whatever they want to work on... But yes, I'd _also_ love to see some effort go into cleaning out the NR queue and getting more of the stuff that's already solved to actually be fixed. :wink:

5️⃣ Update on action items from the last meeting.

dww We haven't been particularly solid on identifying and tracking actual action items from the meetings, so I'm not sure there's going to be much to update. Perhaps this time we can do a better job of this so we have something more concrete to report for this item next time.
Griffyn Heels A) Issue count deployed - https://www.drupal.org/project/project_issue/issues/3151163
B) Initiative triage issue credits - https://www.drupal.org/project/drupal/issues/3155716
C) What do we want to do about archiving the channel? Are the meeting items enough?
larowlan Yes, we also came to the same conclusion
Griffyn Heels Yep, I'll make a note of these this time @dww and make sure they are posted
larowlan I opened https://www.drupal.org/project/drupal/issues/3155716 for issue credit for triaging issues that ended up being closed etc - if you worked on an issue, please be sure to comment there. I’ll assign credit/mark it fixed/add a new issue in 24hrs or so.

6️⃣ Does anyone have any objections to auto closing issues? RE: https://www.drupal.org/project/drupal/issues/3156572

dww Yes, I thought Andrew raised some extremely good points on why auto-closing issues (especially "needs more info") can be problematic.
pameeela yeah as i said, I am -1 on automating it
larowlan Ok, so should we make the scope of that policy issue just ‘Do we agree on these principles for manually closing’ and leave the automation out of it
larowlan If we make the scope focus on just that, I think all we need to finalize this is someone to RTBC it and then we can mark it fixed. I think it would be important to get xjm’s opinion here
dww It's tricky. Andrew is basically arguing that we shouldn't close these, neither automatically nor manually. At the very least for anything tagged 'Accessibility'. But I think his points apply to non-accessibility issues, too...
dww I'm torn. I do like the goal of cleaning these out, but Andrew's points are pretty solid for why doing so can be a net loss. I don't know what else to say.
pameeela @larowlan i don't understand the RTBC to Fixed aspect? would we not mark them closed (whatever the reason)?
larowlan rtbc to fixed is for the policy issue @pameeela sorry for confusion
pameeela ahhh sorry i see
pameeela FWIW i was super gung ho to close old tickets, as i would on a client project. but after talking to x_jm about it and doing a lot of triage of old bugs, i can see now it's a problem to assume old = invalid
dww Yeah, sadly, the queue is full of 10+ year old issues that are still valid.
tr I'm super opposed to closing issues automatically. That just throws away valid work and discourages contributors.
jungle i am -1 on closing issues automatically too. yes, old !== invalid
pameeela i have found though that updating old issues to ask 'is this still occurring' tends to get some action. so perhaps it would be useful to have an annual bot reminder or something? just to post 'hey everyone this issue hasn't been updated in >12 months, anyone got anything to add'?
larowlan I think that is a good idea
dww We kinda do that already with the auto-moving-issues-to-the-next-version-of-core thing.
larowlan which kind of works https://www.drupal.org/project/drupal/issues/3015152#comment-13735875 but sometimes doesn’t
pameeela does that trigger an email notification though? i imagine not else massive mail spam? the reason i think commenting works is it sends an email
larowlan right there’s no notification there
pameeela yeah i think you need a notification.
dww Interesting. I've never done email for core issues. Seems like I'd drown in email. But yeah, I can see why some folks want that.
larowlan going to out myself and say I run my own tagging system in Gmail
larowlan
pameeela haha well yes for frequent contributors it is too much, but for infrequent ones who only care about issues they posted or selectively follow, i would say it's critical
jungle for old issues, or some issues with a lot of comments, Is it ok to close them and open new ones with updated IS if the IS is outdated? Reading through all comments is time-consuming and scary when seeing an issue with a lot of comments for the first time and some of the comments are useless.
pameeela no, i don't think so - when updating the IS for issues where there are a lot of comments, the task is to read through the comments and incorporate them in the IS as needed. so that people who arrive at the issue don't have to
dww That's both a great point, and kind of a scary can of worms, @jungle -- yes, many issues are hard to follow because of a ton of noise. And, there's very often valuable gems buried in the noise. At least when it's all in the same issue, there's *some chance* people will still notice and heed the gems. If we move to another issue, the chances that useful comments from the original issue will still be read becomes approximately 0.
tr I find the "is this still an issue?" bump to be discouraging. Please assume it's a valid bug report. Try to reproduce the issue if you're concerned that it might not be a bug any more. There are many issues I've worked on and posted patches for, then rerolled the patches after a few years when core changes from under me, but no one reviews or commits these patches. All I can do is wait, I can't RTBC my own issues ... I have issues that are 5, maybe even 10 years old that are still broken (one RTBC patch has been waiting for 6.5 years to be committed ...) .
dww I'm with @pameeela on this -- we need to foster a culture of keeping the IS updated with the useful stuff. But forking the issue prematurely would be bad.
tr @dww I agree - it is often the details that matter a lot - if there are hundreds of comments, that means it's not a simple issue. Closing and opening a new issue loses all that community input and risks making the exact mistakes the community warned about in the old issue.
dww (side note) @tr: One very positive outcome of this initiative is the proliferation of :recycle: review swap threads... you can't RTBC your own, but this is a channel full of folks who are generally happy to review something if you ask, especially if you're then willing to review one of our "pet issues".
jungle Yes, thanks, make sense, all good points.
dww So, instead of just waiting and hoping, we can now actively solicit RTBCs from qualified reviewers, and then it amplifies when we turn around and RTBC someone else's priority issue.
larowlan and then i’m happy for you to ping me rtbc stuff
larowlan your frustrations are part of the impetus for this group, we’re hoping to have people for each of the steps
tr @dww Yeah, I've tried that before, but I've given up because that never seems to get me very far ... I focus on the contrib space because there at least I have some hope that my contributions aren't ignored.
larowlan there’s been some issues where we’ve been able to do just that
dww @tr I hear you. Core can be frustrating. But that's part of what we're trying to address here.
larowlan is the RTBC for 6.5 years issue for D7 or 8?
tr Yup, I'm all for the effort, but I'm personally going to remain skeptical.
tr @larowlan Pretty sure D7, since it has been >6 years since RTBC and much longer since the issue was opened... let me see if I can find that
pameeela @tr i think there may be a broader conversation here? (I assume you are the same TR who replied to me recently.) In that case it was an old issue on a topic i know nothing about, but by asking the question, the issue got updated with important information. it isn't a dismissal. it's the opposite of that - it's someone paying attention.
larowlan ok, I can respect that, pretty sure you were around on when I signed up over there 12 years ago (before I signed up on ) so I know you’ve seen many things come and go.
tr @pameeela Yes, that's me. Yes, probably a larger conversation, it's about how the way the issue queue is managed (or not), which in my experience throws away valuable information and hurts Drupal because bugs go unfixed for 5, 10 years or more (literally - I'm not exaggerating here ...). The issue you commented on comes from a contributor who is not a native English speaker and points out a problem with the use of non-ASCII characters in a core Drupal API function. This was moved to "Postponed" after two years, asking the original contributor to verify that the bug still exists. The next step historically has been to close the issue - this never should have been postponed in the first place. The queue needs people to try to reproduce the issue, and people to provide patches, and people to triage patches, and people to aggressively commit patches, but a lot of time we have bikeshedding and efforts to shut down issues because we're more concerned about the size of the queue that the bugs themselves.
pameeela > The queue needs people to try to reproduce the issue, and people to provide patches, and people to triage patches, and people to aggressively commit patches
agreed, and that is what we're all doing here. i personally have triaged >200 issues in the last month. those that i am familiar enough with to try to reproduce, i have. if i don't know enough, i'll ask, and hope that someone who knows more will assist with more info. in the case of that ticket (and many others) it worked just that way.

> we're more concerned about the size of the queue that the bugs themselves
if this were true we're doing a pretty bad job considering >1000 critical / major issues!
tr @pameeela And to be clear, my response in that issue wasn't about your question, it was about the way that historically these "small" bugs have been ignored, discouraged, shot down, so new contributors tend to give up trying to contribute to core when their efforts are not acknowledged or appreciated.
tr @larowlan Actually, not RTBC, instead "to be ported". Same color, which is why I mis-remembered. It was always a D7 patch but I was required to open it as a D8 patch because D8 was the current -dev branch back then. D8 eventually changed so it was no-longer relevant to D8, and it looks like the issue languished because someone set it to "to be ported" instead of just changing the branch back to D7. Regardless, 9 years 3 months after I opened the issue it's still a bug but I'm no longer interested in working on it.
pameeela i created https://www.drupal.org/project/project_issue/issues/3157362 for feedback on my idea
xjm The only scenario where I think we will auto-close issues is when a major version goes EOL. For example, when D7 is EOL in November 2022, I could see all the 7.x issues getting a bulk update to Closed (Outdated) like the 6.x issues did.

7️⃣ Following on from the mentor discussion. Do we want to nominate one person per week/fortnight to act as a wayfinder to help new comers?

jibran The idea here is that if you are stepping into the initiative as a beginner you should have a goto person to contact so that you don't feel overwhelmed.
jibran As for mentor, we can check the channel periodically and get to the thread and help the beginners to navigate by contacting/pinging appropriate folks.
jibran So who is in now as a mentor :slightly_smiling_face:
dww I'm willing to help, time permitting. That's always the hurdle for me. Too many responsibilities, no one paying me for them, trying to also keep food on the table.

8️⃣ Suggest a focus for the next two weeks in this thread. Vote on the suggestions you like. We’ll pick the one with the most votes in 24 hours and use that as our focus until the next meeting.

larowlan I’d like to make some headway on the bundle of Views + Date filtering issues that Derek has flagged. But I think that will likely mean adding a BC layer to unblock it. Derek has indicated he’s not keen on that so we likely need some fresh contributors/opinions here.
pameeela strategy for tackling triage of stale major/critical issues? thinking of maybe identifying triagers per topic - views, a11y, etc - and then feeding those people issues
jibran @pameeela good idea.
larowlan ^ I think that is worthy of its own thread
jibran @larowlan see 4️⃣ as well. @dww #145 still needs addressing. Maybe @quietone and I can pick it up.
quietone @jibran, OK
dww I'm down to try to help, I'm just fairly burned out on trying to fix bugs without changing anything. :wink:
jibran Yeah, I know the feeling.
dww I weep every time I hear the argument that "we can't fix that bug, it'd be disruptive, since people might already be working around it..."
tr @dww And the opposite is also true - try to fix a non-disruptive bug with just a few lines of code, and it will be seen as too unimportant to spend time on. There are 100 of these for every critical disruptive patch...
larowlan @tr that’s what we’re trying to help with this initiative. See https://www.drupal.org/community-initiatives/drupal-core/bug-smash#work-... for what we’ve been doing - it seems to have been working
larowlan and welcome :wave:
dww @tr I don't know that there's a "that bug is too small" culture. I think the bigger problem is that we have so many hurdles^H^H^H "gates" to getting something into core that many people can't be bothered to keep jumping through hoops to get something officially fixed. They feel (correctly) that going through all the trouble to open a valid bug report, and _provide a working patch_ (!) should be enough. Once they solved it for themselves, they're ready to move on. But that's not enough for Drupal, so the issue just sits there once "we" mark it NW for All The Reasons(tm). Again, those reasons are _also valid_, so it's complicated. But I don't think "anyone" is opposed to fixing small bugs. It's just hard to get _anything fixed_, and so the effort doesn't seem worth it if it's too minor.
larowlan I love small bugs with a test
dww "... with a test". :wink:
jibran Yeah, one line views fix warrants 10KB of tests :stuck_out_tongue:
tr There are a lot of issues that don't need tests - a lot of these are documentation patches... We complain a lot about the documentation but it's impossible to fix it ...
jibran Doc issue are not bugs though they are task, right?
tr Depends on the problem. Spelling mistakes are a task, but missing or wrong documentation is a bug. At least IMO, I haven't read the guidelines recently.
tr Documentation comments define what the method is supposed to do, and many times these are the ONLY things we have to say what a method is supposed to do, what it is supposed to return, what the parameters are supposed to be, etc. If the documentation comments don't specify the return type and meaning, for example, it's hard to claim the method doesn't return the right thing ...
tr For example, https://www.drupal.org/project/drupal/issues/2733299 - why does it take >4 years to fix a missing @return ? Nothing to test here ...
lendude @larowlan Views + Date is a worthy target but pffffff it is hard

9️⃣ (split off from 8️⃣ ) strategy for tackling triage of stale major/critical issues? thinking of maybe identifying triagers per topic - views, a11y, etc - and then feeding those people issues

jibran I'm happy to help where I can.
pameeela what are your preferred topics, if you have them?
jibran views, entity(anything using it as well), shortcut, contact.
larowlan would it make sense to align the triage focus with the dev focus?
pameeela i'm not sure, with triage it's easier just to go through the list. hard to focus it i think, you never know what you will find
pameeela is it better to try to curate, or shall i / we just post with ? when we have an issue that needs input? i don't want to flood the channel but i could....
jibran ? works for me. Looking at the backscroll, it looks like people are responsive most threads have replies.
pameeela yeah i know but there's a limit
pameeela and also the replies tend to be from the same 2-3 people :laughing:
jibran at least better than no replies.
pameeela right but then it just feels like noise for 95% of the channel
jibran Do we need a new channel for triage only stuff?
jibran How do we get folks to join that?
larowlan I think its what we’re here for
jibran I agree
larowlan so I’m -1 to a new channel,
jibran Should I -1 on above comment or +1 to agree :smile:
jibran @larowlan also 1️⃣ 0️⃣
larowlan Do you think it warrants a link on the initiative page Pam? ‘This week’s triage focus’
dww We have a @todo section on the initiative page about "Focus", but we never actually decided one (yet).
dww "Bug Smash Initiative "official" targets"
lendude Yeah -1 for a new channel. Not responding is not the same as thinking of something as spam. I think people can (and probably do) learn a lot from reading along in the discussions, and might give them confidence to reply to other issues

1️⃣ 0️⃣ Initiative plans for DrupalCon contribution day?

jibran We have https://contrib2020.getopensocial.net/group/bug-smash-initiative/about thanks to @pameeela
pameeela yeah haha this was my addition to the agenda.
jibran I tried to create one before and it had too many fields so I left it :smile:
jibran I knew you'd do it :smile:
pameeela i would like to do a 'triage blitz' for like 1-2 hours where we just go through stale issues in the chat and try to move as many as possible.
larowlan Count me in assuming timezones fit

1️⃣ 1️⃣ How can QA resources help with bugsmash ?

Griffyn Heels from Kristy here: https://drupal.slack.com/archives/C014QES6HSQ/p1594095268050500?thread_t...
dww Seems like a bunch of our existing 'Needs triage' links would be easy for QA folks to work on... needs steps to reproduce, etc.
pameeela @Kristy i don't think that folks who are unfamiliar with drupal core contribution can easily jump in to needs review. i think the 'needs manual testing' tag would be better
jibran This is a really good question. @dww do we have action items for QA on initiative page?
larowlan would this fit well with the proposed webinar you were going to run when things got quieter @pameeela
dww https://www.drupal.org/community-initiatives/drupal-core/bug-smash#issue...
pameeela yeah but i really don't think that can be 'triage for beginners'
pameeela triage is not a low bar to entry
dww it's not specifically "QA" as such, but everything in that section is something QA folks could help with.
pameeela i'm going to add the needs manual testing tag to that list
jibran Yeah, we need to find a way to get beginners in. @Griffyn Heels is also interesting in that.
larowlan I will add ‘needs manual testing’ to our initiative page
pameeela @larowlan beat ya!
larowlan @Kristy the ‘needs manual testing’ link Pam just added to https://www.drupal.org/community-initiatives/drupal-core/bug-smash#issue... is a good place to start for QAs
larowlan they should be able to test it without installing Drupal locally, via http://simplytest.me
larowlan @Kristy i’m happy to do a screenshare/call this week on how to do that ^
Kristy ah yes `needs manual testing` might be a better one. Thanks for the above links. Will check it out.
Kristy I had looked at http://simplytest.me but a colleague told me it has been broken for a while (unless it’s not anymore)
pameeela some things are still broken, e.g. i don't think you can spin up a distro? but core and patches works fine AFAIK

@tr has joined the channel

1️⃣ 2️⃣ Are there any JS related issues that are available for contribution?

Griffyn Heels Raised by Pratik: https://drupal.slack.com/archives/C014QES6HSQ/p1594095563055000?thread_t...
jibran We have a 'javascript' tag and @nod_ is also in the channel.
larowlan There is a lot of work to be done with JS before Drupal 10. Which isn’t bug related obviously. See #d10readiness for details
pratik_kamble Thanks. I'll check there...
tr Yeah, JavaScript is what we call a target-rich environment ... it looks like 1500 issues in core tagged JavaScript. Contrib has a lot of JS issues as well. My suggestion is to look at the "Needs review" issues first - those should already have patches, so you can use your expertise to evaluate those patches and either approve them (mark the issue as RTBC) or add constructive criticism, or re-roll the patches against current HEAD if they no longer apply. These are the easy things to do. Dealing with "Needs work" or "Active" patches is harder.
himanshu_sindhwani https://www.drupal.org/project/drupal/issues/3092536 , this issue needs some attention

1️⃣ 3️⃣ What's our "official policy" [sic] as an initiative on tasks like test suite plumbing?

Griffyn Heels Raised by dww: https://drupal.slack.com/archives/C014QES6HSQ/p1594095891062600?thread_t...
dww Basically, a lot of stuff gets filed as a 'task' that's related to the test suite, which in turn blocks actual bug reports. Any objection to tagging test-related issues, even 'task', for Bug Smash?
dww Don't want to get too lost in the weeds with the massive 'task' list, but I'm talking specifically stuff to add tests, make test writing easier, etc.
jibran Yeah, I like the idea but I'd like to hear what other folks think about it.
quietone I too like the idea but I still don't have a clear understanding of what qualifies as work for this initiative and what does not. I could argue that we have been creating tools (the templates) to aid closing bugs and a test suite is another tool. Or I could argue that no, it is not a bug and there are already plenty of bugs that could be worked on now and that as the bubble of work expands we lose focus.
dww Fair point. But many bugs are blocked on tests, and Tests Are Hard(tm), and I think we all have an interest in making our test suite easier to make sense of, maintain, expand, etc.
lendude Hmm yeah with quietone on this one, it sounds great to provide the tools we need to smash bugs, but keeping focus is also very important. I think people should be free to post task that help make bug smash tools in the channel, but maybe not tag them with the initiative tag?

@DeepaliJ has joined the channel

1️⃣ 4️⃣ Okay, Bugsmash meeting 3 is over. Thanks all for coming! Please feel free to keep chatting in the threads. I'll work on getting the notes on d.o in the next 24 hours.

jibran Threads are open for next 24hrs.
quietone @Griffyn Heels thank you for facilitating!
jibran Thanks, @Griffyn Heels for running this.
dww Opened https://www.drupal.org/project/drupal/issues/3157348 for next week and updated https://www.drupal.org/project/drupal/issues/3153713 to point there.
jibran lol @dww what have you done :smile:
dww ?
jibran https://www.drupal.org/project/drupal/issues/3154066 for next meeting.
jibran ah!
jibran I'm so confused now.
dww https://www.drupal.org/project/drupal/issues/3154066 is this meeting.
dww I guess I should wait for the 24 hours to end and then refresh the parent meta. ;)
jibran ah! ok. Ignore me then :smile:
dww I'm probably confusing things a bit by being too on the ball. ;) For the 24 hours while the meeting is still "open", I/we should probably leave the "next meeting" as the current day (maybe update the issue with "meeting happened, but threads are still open"), and then when we close the threads and post the minutes, we can refresh the parent meta and open the issue for the date of the next meeting.

larowlan credited Berdir.

larowlan credited Lendude.

larowlan credited TR.

larowlan credited g-brodiei.

larowlan credited griffynh.

larowlan credited himanshu_sindhwani.

larowlan credited johnwebdev.

larowlan credited jungle.

larowlan credited pameeela.

larowlan credited pratik_kamble.

larowlan credited quietone.

larowlan credited xjm.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented

larowlan credited kristydv.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
griffynh’s picture

griffynh commented

Hi team, I've put together a quick list of highlights and links to catch up on Tuesday's meeting:

pameeela’s picture

pameeela commented

@griffynh can you update these links to reference the Slack transcript in the first comment? The Slack links will stop working before long and the whole chat is captured there so it makes for a better archive.

Status: Fixed » Closed (fixed)

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