Thanks to those in the community who participated in the recent calls on the potential DSpace Futures initiatives on the REST API and DSpace and Hydra.
Here is the link to the notes from the calls: https://wiki.duraspace.org/display/DSPACE/DSpace+Futures
We invite everyone in the community to add their feedback in the comments section at the bottom of the either of the notes pages -- and if you have other use cases for a REST API feel free to add them to the use case grid (https://wiki.duraspace.org/display/DSPACE/DSpace+Futures+REST+API+Use+Cases).
The meetings affirmed there is a lot of interest in the community in pursuing both a REST API and DSpace and Hydra. The next step is to have the individuals or institutions formally identify their willingness to be a part of the initiatives. To do so you may either let us know via email or on the wiki page (https://wiki.duraspace.org/display/DSPACE/DSpace+Futures). Each initiative also needs a person from the community to take the lead. To clarify how this will work, we have outlined below the various roles.
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.
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.
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.
We look forward to helping the community move these initiatives forward!
Chief Executive Officer
Chief Strategy Officer
DSpace Technical Lead
Director of Community Programs