Time/Place
- Time: 11:30am Eastern Daylight Time US (UTC-4)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
Attendees
- Chris Awre
- Ginny Boyer
- Robert Cartolano
- Aaron Choate
- Sayeed Choudhury
- Stefano Cossu
- Dan Coughlin
- Tom Cramer
- Joanna DiPasquale
- Jon Dunn
- Declan Fleming
- Maude Francis
- Mike Giarlo
- Wolfram Horstmann
- Neil Jefferies
- Debra Kurtz
- Susan Lafferty
- Steve Marks
- Rosalyn Metz
- Tom Murphy
- Este Pope
- Matthias Razum
- Nick Ruest
- Robin Ruggaber
- Tim Shearer
- Jon Stroop
- Jim Tuttle
- Keith Webster
- Evviva Weinraub
- David Wilcox
- Andrew Woods
- Maurice York
Agenda
Topic Fedora technical plans Membership ideas from Task ForceLead Andrew Scheduling a code sprint to align the current Fedora implementation with the API spec Andrew Moving towards institutional developer commitments Andrew Agenda for OR2017 Fedora LG Meeting All Chris/Rosalyn Vote on Fedora/Islandora/Hydra proposals for DLF! All Formalizing the Code of Conduct committee Roundtable All
Previous Actions
Minutes
Fedora technical plans - gain consensus, highlight vision for technical work and how the pieces fit together.
- Finalize API spec - June 20th deadline for initial public working draft, five person editorial team with weekly, Wednesday meetings has ensured we stay on schedule. There is a delta between specification and current implementation, a certain amount of work needed to move the implementation forward to align with spec. Ideally this summer work will begin. We want to encourage community who have use cases that current implementation isn't addressing or isn't addressing well, that we try to address in newer spec. Given diversity of use case it's conceivable that there won't be a single specification that addresses all needs. Another set of work around test suite. Regardless of the implementation chosen, priority number one is to move outliers to chosen version. Have already made significant progress towards import/export tooling. Support for plan voiced. Are there ways to name implementations for easier identification? Part of branding conversation. Leadership needs to put more thought into this, as reference and community implementations evolve. Don't have a clear plan for branding questions. How do we want to position Fedora brand and implementations? Communicate dependability and avoid fracturing efforts. On agenda for leaders meeting at OR.
- Align ModeShape implementation with the spec
- Foster alternate implementations
- Move off ModeShape if a better alternative is identified
- Bring along anyone who is currently on ModeShape to the next implementation
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 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 - In Fedora 3.x era commitment more personal, did not seem like this was written into job descriptions and responsibilities. Ppl worked on this after office hours. Contributing to single projects vs. a suite of OSS. Would be helpful if 'on the ground contributions' development/testing, also helpful to have some time allocated to Fedora and other OSS projects of value to the community. Andrew notes some institutions reserve Friday for "Open Source Day". Majority of contributors are ad hoc. Need to operationalize this at your institutions. How can we increase time contributions at your institutions? Support voiced for "Open Source Day". Each institution needs to figure how they can contribute. Northwestern mandates that each developer has to participate in at least one sprint annually, ensures long-term sustainability of projects.
Actions
Andrew Woods - Add new ppl to Slack leaders, Ginny, Este, Rosaline, Joanna.