...

Scheduling a code sprint to align the current Fedora implementation with the API spec - align community implementation with API spec, need at minimum three institutions who can commit resources to the sprint, lay ground work to open up to broader community. Need to have specific dates to engage with committers on those dates. For the leaders who might be interested in the broader plan and this specific work towards API spec, we need commitments from leaders. Call for participation. Will also send a note to Fedora leaders to approach institution. Question: Do we have a sense for timeline of work? Start work after OR, July, August, and September. Amherst voiced interest, need to confirm resources and commitment. Sprint just completed with import/export succeeded because there was a diverse work team, developers, testers, documenters. The ask isn't just exclusively for developers. Question: When API goes out in June will there be a solicitation for feedback? Getting feedback will lengthen timeline. Need to review for accuracy and to confirm they meet clients' needs. Server side feed back, those implementing. Context for specification work can be found here: https://github.com/fcrepo/fcrepo-specification/wiki/Fedora-API-Specification-Charter

FIrst First public working draft June 20th. 

...

. As new people come onto leaders are they invited to the channel on Slack? Several voiced this is not happening. Need to operationalize. When a request goes out to leaders, would be helpful if it was contextualized, verified.

Moving towards institutional developer commitments

Actions

Andrew Woods - Add new ppl to Slack leaders, Ginny, Este, Rosaline.