---
# System prepended metadata

title: 'Nov 12, 2025'
tags: [steering]

---

Steering Group - Meeting Minute
===

###### tags: `Templates` `Meeting`

:::info
- **Location:**   https://utexas.zoom.us/my/kimray 
- **Date:** Thursday, November 13th at 11 am PT / 8 pm CEST(?)
- **Participants:**
:::
    
**Agenda**

1. Welcome new BIDS steering group members! 
    -please orient them to links, invites, meetings
    -hack md folder, gmail permissions, meeting timing
    -do thursdays still work for this group?
3. Maintainers Update (Ross)
##### Bep Process Updates for Steering: 
::: spoiler How the review period / queue going?
    - 9 bep leads were reached out to by email (which month was this again?)
    - 2 review periods from originally planned 3. (US shutdown, etc.)
    - Are any ready now? 
      - Atlas review starts monday
      - BEP028 e.g.  status / delays?
        - Boris: getting up to speed, large changes, prioritizing tasks/scope (e.g should validating provenance metadata be part of BEP028 ?)
:::
::: spoiler What would help?
    - schema documentation, user feedback/testing for pain points, maybe get a bit more direct feedback soon, who/when?
    - [Anthony's PET bep->schema walkthrough](https://bidsschematools.readthedocs.io/en/latest/doc_to_schema.html) could be a useful model to share more 
    - Schema pre-review should be strongly recommended & communication (BEP Process WG)
    - Start schema earlier. 
    - Keep communicating through the process, because BEP changes will also change assumptions/guidance on schema work needed
    - Multiple points of community review, not just near the end, to help alleviate 1 lone reviewer blocking at the end.
    - (Julia) Ask BEP leads to use public channels, like Neurostars, at these points
    - (Julia) design it like a few iterative (agile) cycles, so that's clear for BEP leaders 
    - (Yahya) BEP leaders could regularly update the state to the community. If they stick to it, maintainaers should moderate blocking comments in the official review.
:::
::: spoiler Was email a good way to do those communications to the BEP leads/community?
    - (Chris) worked well enough
    - 9 beps offered, 6 beps said they were ready, 3 were actually ready/reviewed
        - Good idea to go back and consult those BEPs that fell off to find out what would have helped (BEP Process WG please note for follow-up)
    - (Julia/Chris) Eye-tracking - got stuck on a) not urgent until release b) deciding who/how/where to respond to Kay, this could be quasi-standardized. (e.g. does steering or all maintainers, or one maintainer respond?). Otherwise it's accepted and good to go. 
    - eye-tracking comms missing from Maintainers to BEP leads: Actually tell the BEP leaders review period is over and it is expected to be merged with the next update.
:::
::: spoiler what should change for 2026?
   -  BEP Process working group back on track now that Eric is back at work. Open-letter is being drafted, no ETA on when it will go out.
:::

#### Chatbot discussion 
  - ~~https://bids-assistant.vercel.app/chat~~ new:  https://bids-assistant.neurosift.app/chat
  - meeting notes [here](https://hackmd.io/@mnJQvyboRfeHeOzygpc5Ow/S1-jdXqJWe/edit) and full transcript/video [here](https://drive.google.com/file/d/16lTTSPZwIkSnBoi1HMNlaEVSGLghW8Rf/view?usp=drive_link)
  - ::: spoiler next steps:
      - Adding PRs/Issues, Community convo (NeuroStars). Requires DB and regular updates, Yahya is developing one option.
      - Feedback from steering is requested can be put in this [issue](https://github.com/bids-standard/bids-specification/issues/2256)
      - should be clear what is/isn't resources consulted by the spec. 
      - ready to put it on the spec, if no feedback 
      - followup work: neurostars and other resources would be good to integrate. 
          - database would be needed, api key etc. 
          - working example of bids-assistant with pr content

#### Election updates in the Mattermost channel post-meeting: 
  - Chris: It's all over and wrapped, only a post-mortem  we might want to do. Results have been published and announced on bids-discussion/neurostars. JB and Martin have been invited to the steering call. I guess I should send someone a receipt for the election.
  - 


4. [name=Camille] Call for BIDS communication maintainer

todo camille : liaise w maint + sterring to define which communication and then advertise

5. Fiscal sponsorship for BIDS? 
        - please reach out to Christine Rogers for a timeline to revisit this



2. [name=Camille,Yarik] BIDS in-person meeting before/after OHBM 2026 10 min
  - JB: propose BIDS projects (like BEPs etc) for hackathon projects since people would be there and could work/present/...
  - Yarik: wait for brainhack to be announced and then organize BIDS folks
  - start planning in https://github.com/bids-standard/ohbm-hackathon
  - 
4. BIDS at SfN 2025, San Diego Nov 15-19
    -Kim is here, come say hi at the APEX/Brainlife.io booth :) 
    
1. [name=Camille] BIDS overview, who is doing what and what is needed in the future as a pre-discussion to BIDS OHBM meeting and town hall



:books: Meeting Minutes
---

**Maintainers updates**
- 

**For the next meeting agenda**

1. 
2. 