...
- Lead / Co-Leads
- The initiative "lead" would help to convene regular meetings amongst all interested participants and developers.
- Would help to build consensus around use cases and requirements
- Would strive to keep the initiative moving forward.
- The role is an "initiative management" role. The individual(s) need not be technical.
- Steering Committee (optional)
- Ideally, a committee would be formed to help support the "lead" in the goals of building consensus and ensuring the initiative stays on track.
- Again, committee members need not be technical, but should have a good grasp of the problem at hand.
- Developer Team
- Would help to develop, test and release the actual code
- Would communicate directly with the Lead and/or Steering Committee around use cases and requirements
- Ideally, each developer would have approval from their workplace to spend a percentage of their time on the initiative
- Ideally, at least one existing DSpace Committer would be on this team.
- DuraSpace
- Would attend regular meetings and contribute to consensus building
- Would offer perspective from other initiatives and projects, and help ensure cross-communication between initiatives and with the DSpace Committer Team
- Would provide necessary infrastructure: conference line, wiki space, JIRA, GitHub, etc.
- Provide administrative support for any fund raising required
- Provide and contribute to communication channels for project awareness, status, etc.