Page Comparison

Core devs/tea times

Jeff Wagner

• Core devs meeting deprecated in favor of tea times/discuss team-building

  • Tea-times are serving same purpose as core devs meeting (brief updates on what everyone is doing, putting out fires if needed)

  • Three tea-times

  • Serves same function as core devs but in less grumpy timeslots

  • Take-away: Join the two that work best for your timezones and you’ll overlap with everyone.

  • These are shared with/overlap with OpenFE

Annual meeting save-the-date/recap

Jeff Wagner

• Recap/field quesetionsquestions

  • Jeff did a good summary of plans/tentative layout but I did not take detailed notes on this.

GitHub Discussions

Lily WagnerWang

• Announce/demo GitHub discussions forum

• Info on what goes where

• LW – This is a good spot for issues that don’t seem discretely resolvable. There are a few categories where different sorts of discussions should go. I expect Q&A to be the most popular, but there’s also science and infrastructure.

  • To transfer an issue, click “transfer issue” on the bottom of the right bar, transfer it to the discussions repo, and then once it’s done transferring, convert it to a discussion.

  • Importantly, you can usually mark one reply as being “the canonical answer”. And if you make a mistake you can start a new issue from a discussion.

• JW – I’m excited that this will help us have good discussions without being confused about whether they’re tied to work items. But I generally see discussions as “potential issue and PR generators”

• DM – Right, and we shouldn’t assume that all discussions will be resolved or lead to action. More commonly, I expect that a good discussion will lead to a real-time discussion in an actual meeting before turning into work items.

alchemiscale update

David Dotson

• Slides here: https://docs.google.com/presentation/d/1Vy_dYbl67HMb0gCQKGQxLLI_GceyGaLbp_OWVxTXlco/edit?usp=share_link

• (see recording, starting around 20 minutes)