The contributor guide puts a lot of weight on the physiopy library code, but for those of us landing on that guide via the "Community Guidelines" documents your group has created, it's unclear how we can contribute back to those guidelines, or if that's even a thing you folks want.
(For context, I work at the UW–Madison Institute on Aging, and we've been running a longitudinal study that gathers MRI and physiological data for quite a while here, on a cohort that spans 7 decades. [We collaborate with Rasmus Birn here at UW, who you cite in the guidelines!] This group has possible thoughts to contribute back about the complexities of gathering physiological data in-scanner with diverse, aging subjects, but the current site makes it not super clear how that contribution should happen.)
The contributor guide puts a lot of weight on the
physiopylibrary code, but for those of us landing on that guide via the "Community Guidelines" documents your group has created, it's unclear how we can contribute back to those guidelines, or if that's even a thing you folks want.(For context, I work at the UW–Madison Institute on Aging, and we've been running a longitudinal study that gathers MRI and physiological data for quite a while here, on a cohort that spans 7 decades. [We collaborate with Rasmus Birn here at UW, who you cite in the guidelines!] This group has possible thoughts to contribute back about the complexities of gathering physiological data in-scanner with diverse, aging subjects, but the current site makes it not super clear how that contribution should happen.)