---
tags: TechMon
---

# 2025/05/27 (notes)

:::info
- **Date:** 25/05/27 12 pm EST
- **Participants:** CM, OE, MG, EM, JHL, MN

:::

:::success

## Agenda

1. fMRIPrep-rodents
* A [new issue](https://github.com/nipreps/fmriprep-rodents/issues/57) was raised, but unlikely to fix before refactor.
* How to address? Archive? Refactor with notice? Something else?
1. MRIQC after PETQC additions
* Rename?
* Split?
3. [NiPreps website](https://www.nipreps.org/)
* There is many passages that [refer to fMRIPrep](https://github.com/search?q=repo%3Anipreps%2Fnipreps.github.io+fmriprep&type=code&p=1) (see files `CONTRIBUTING.md` or `members.md` for example). Should these be made more general?
* Use a broken link CI check action? e.g. [PR #58](https://github.com/nipreps/nipreps.github.io/pull/58)
4. Template for new preps?
* Somehow linked to the above and [last week's Bi-monthly Roundup](https://hackmd.io/@NiPreps-technical-monitoring/bimonthly-20250521) comments (extending to other modalities): cookiecutter or something else?
5. Templateflow new template submission
* https://github.com/templateflow/templateflow/pull/181
* Checklist for reviews?
6. smriprep change to process sessions
* https://github.com/nipreps/smriprep/pull/480
* missing PR - https://github.com/nipreps/nireports/pull/193

:::

## Notes

### Item 1
* `fMRIPrep-rodents` will probably get archived as a breaking change, heavy refactoring is planned to integrate parts into `fMRIPrep`, `nitransforms`, etc.
* A possibility is to use a plug-in system (calling this particular one `nirodents`) in `fMRIPrep` that can be called with particular flags (e.g. `--rodents`).
* So mark the issue as `won't fix` and tell that issues will be considered in the potential `nirodents`.

### Item 2
* Similar problem as with `nibabies` and `nirodents`: trunk of shared code deviates from branches.
* Having a single repository is nice as a single tool would be able to QC all neuroimaging modality data.
* Renaming possibilities: `nipreps-qc`, `niqc`
* Would not be an issue dockerhub
* Could keep `mriqc.readthedocs` and create `pet.readthedocs`.

### Item 3
* BIDS has a link checker CI

### Item 4
* Current repository has no actual code to create a skeleton: https://github.com/nipreps/Cookiecutter
* Variety of ways to do things across the different projects, but maybe there are some commonalities.
* Merging back things when something is changed in a repository?
* May be difficult to support: sometimes we want to reuse many things from a given `Prep`, so easier to strip things rather than building things.
* Slightly related: have a central resource for things that affect all repositories (e.g. when do we drop Python 3.9?) and have these done at a single place. A CI that triggers downstream changes?
* Will be discussed in the next NSC.