TSC General Meeting Agenda - 2025-09-25

[cdils]

Meeting Purpose: Strategic direction, governance, policy, cross-team priorities, and project oversight.

Audience: FAIR TSC members & open observers (as allowed).

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

Meeting details

• Meeting is September 25, 2025 – 19:00 UTC (see it in your time zone)
• Link to Meeting 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.

[cdils]

Discuss future release planning and organization beyond 1.0 and how we can better utilize Github for project management.

• Any final thoughts before merging First version of Github Management Process #81 ?
• @bensternthal can you suggest next steps for helping with adoption as we move past the 1.0 release?

[bensternthal]

@cdils here is what I am thinking:

• I can go ahead and create the rollup board now, for it to work properly we do need to setup milestones and have the projects use them
• Is there a roadmap with milestones already defined, if not thats OK, I would just want to know what the next release would be numbered
• After that I think its just socializing and ensure folks are tagging their issues appropriately, reviewing the rollup board in the weekly meeting can help with building that muscle memory

[cdils]

Is there a roadmap with milestones already defined, if not thats OK, I would just want to know what the next release would be numbered

Not yet. Re: numbering, that will be a problematic considering FAIR encapsulates many individual software repos, each with it's own versioning. We were trying to solve for this with named releases per #86, but still need a resolution on that.

[bensternthal]

No worries, we can finish the setup whenever that is resolved.

[cdils]

1.0 Retrospective from a broad TSC perspective (e.g., oversight and process). Monday's tech call could have their own tech-specific retrospective.

Proposed Discussion guide:

1️⃣ Context & Purpose (5 min)

• What was the primary objective of this release from a TSC perspective?
• Did we meet the strategic goals we set at the outset?

2️⃣ What Worked Well (10 min)

• Which TSC decisions or processes added the most value?
• Where did we communicate especially clearly or act quickly?
• What helped us stay aligned with the overall roadmap?

3️⃣ Challenges & Gaps (10 min)

• Where did our decision-making or guidance slow things down?
• Were there risks we could have spotted or escalated earlier?
• What feedback did we miss from engineering, product, or stakeholders?

4️⃣ Key Improvements & Next Steps (10 min)

• What’s the single most important change for the next release?
• Do we need to adjust our charter, meeting cadence, or documentation practices?
• Who will own each action and by when?

[toderash]

Great looking discussion guide, @cdils ! I was just dropping in ahead of the meeting to suggest discussing some overall priorities that we could slot into the next couple of releases. Here's what's top-of-mind:

1. Completion of tech independence with translations & patterns
2. FAIR plugin (& AspireCloud) support for DID:Web
3. AspireCloud to add Elastic Search
4. AspireExplorer & FAIR Plugin faceted search UI
5. Mini-FAIR Repo - add DID document update for alsoKnownAs
6. Documentation Project - short-term deliverables
7. Trust Model - security review of architecture, team review of draft model, & labeller scope
8. New: SKC's work on MU-config & WP-CLI support
9. New: Nameth's work on CLI scripts for DID creation
10. New: AspireBuild project scope

[toderash]