Stefan Appelhoff

+1 to remove the python validator from the JS repo and potentially even deprecating it in favor of the new schema based python validator.

cc @rwblair

> I think the idea was to make it harder to make uncaught typos, but this was always the other side of that coin. yes, and to some extend also...

I see, thanks! Why wouldn't you want to put this (seemingly free text, general info) into the README of the dataset? The danger with putting custom metadata into BIDS JSON...

@bids-standard/maintainers and also @robertoostenveld (with whom I imagine I talked about this many months ago) what do you think of allowing arbitrary metadata fields in sidecar JSON files? In MRI...

Thanks for the report! I think we should allow controlling these messages via the `verbose` parameter: ... see: [`mne.verbose()`](https://mne.tools/dev/generated/mne.verbose.html#mne.verbose) And we need to add a `verbose` parameter to `write_raw_brainvision` in...

- see also: https://github.com/mne-tools/mne-bids/issues/773

I added GitHub as a "trusted publisher" on PyPI:  following: - https://docs.pypi.org/trusted-publishers/adding-a-publisher/ - https://github.com/mne-tools/mne-python/blob/main/.github/workflows/release.yml

Hi @AmaiaBA I think I now agree with Mainak and think there is little harm in allowing mne-bids to produce experimental/BIDSish OPM datasets for now, so I'd be happy to...

@AmaiaBA I just realized we never finished this. All we really need are a changelog entry and your name in the authors list -- the steps are described here: https://github.com/mne-tools/mne-bids/pull/1222#issuecomment-2134679150...