we’ve had a few conversations recently about what the DataSHIELD steering committee might look and function like. We are now at v0.1 of what that might be and we are looking for some input from the community to see if we are heading it the right direction.
Purpose of the steering committee (with some examples)
- Ensure funding sustainability.
- By contributing resources to core projects
- Volunteering groups for maintaining core components.
- Putting in (joint?) grants that cover core components.
- Guide the technical direction.
- Should we concentrate on particular development priorities?
- Is it ok to make a substantial breaking change to the code?
- Sign off policies.
- As the code of conduct and contribution policies are developed these need sign off.
Membership of the steering committee (in no particular order)
- 1 PI/senior representative from each engaged consortium/cohort group.
- 1 or 2 senior DataSHIELD user representatives who would gather feedback from the community.
- 1 independent software representative outside of DataSHIELD.
- 1 from OBiBa.
- 1 or 2 senior DataSHIELD developers.
- 1 lay person.
- 1 ex-benevolent dictator.
Ideally the steering committee will meet 3 or 4 times a year (mostly virtually, but we should aim to align with common face to face meetings where possible).
The Newcastle team is happy to support the initial administration of the committee, but that doesn’t mean we want to chair it - we’d rather that was someone external to us.
So, over to you. What major purposes have we missed and which other groups of people should be on the membership?