Tech Call Agenda - 2025-12-22

[cdils]

Meeting Purpose: Deep-dive, hands-on technical work & implementation for FAIR.

Audience: All technical contributors (not just committee members).

Please add agenda items as comments below and up-vote on the items you'd like to discuss.

Meeting details

• Meeting is December 22, 2025 – 17:30 UTC (see it in your time zone)
• Link to Join Meeting via Zoom
• Link to Calendar

How to join

This call is open to anyone, but note that you need to have a profile/account at OpenProfile.dev to join the call.

Reminders

FAIR is part of the Linux Foundation. Meeting attendees are subject to both the Code of Conduct and the LF Antitrust Policy.

This meeting is recorded and publicly available via your OpenProfile.dev account.

[toderash]

Last call for 2026 roadmap commentary! (gDoc) - check the various tabs for detail in each area of the overall FAIR project (Connect, Beacon, Documentation, website, etc.) and refer to the last tab for the public version proposed for the website. Each of the tabs is fairly short, just split for organizing them.

Next Step will be fleshing out a Gantt chart that shows dependencies between all the things and mapping it all to the calendar. This part will be fairly tentative and will try to leave room for things that come up as timely new ideas or re-prioritization of existing ones. Once we've got that, we can start tagging issues to milestones.

[toderash]

Release Cadence:

We've been talking 6-week release cadences for Connect & Beacon, but need to formalize whether or not we'll be changing that so we're all clear. Sticking to 6 weeks means most milestones would have 2 releases, but an occasional one will technically have 3. The milestones contain space for two 8-week cycles within them. Since we (attempt) release on Tuesdays, this would mean 7 weeks of dev, then a Tuesday release, followed by a few days of buffer before the next cycle starts on the Monday. I'd say that's fine, since we aren't really making the 6-week cycles reliably (yet), and the buffer allows it to slip a bit, but more importantly, if could allow for a proper week of testing & release prep after 6 weeks of dev and before release, making the release date more reliable. Post-release, that leaves some days available for retrospective and planning the next release cycle.

Either is fine, but if we stick to 6 weeks, we should identify and be comfortable with an explanation/plan for how we'll hit that cadence going forward - i.e., what's different about the future from the past.

[joedolson]

Agreed in the discussion to move to an 8 week release cycle. The intent is 7 weeks for dev with a 1-week window for the release. This allows flexibility to schedule the release based on availability and allows us to push a couple of days without actually impacting our overall schedule.