Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Advanced Tables - Table Plus
autoNumbertrue


Topic

Lead

Fedora technical plans

  1. Finalize API spec
  2. Align ModeShape implementation with the spec
  3. Foster alternate implementations
  4. Move off ModeShape if a better alternative is identified
  5. Bring along anyone who is currently on ModeShape to the next implementation
Andrew
Scheduling a code sprint to align the current Fedora implementation with the API specAndrew
Moving towards institutional developer commitmentsAndrew
Agenda for OR2017 Fedora LG MeetingAll

Membership ideas from Task Force

  • Merging Fedora, Islandora, and Samvera site information into a master list
  • Allow individuals to declare their support (similar to DORA)
  • Develop corporate sponsorship model (ideally based on the VIVO model)
Chris/Rosalyn
Vote on Fedora/Islandora/Hydra proposals for DLF!All
Formalizing the Code of Conduct committee
RoundtableAll


Previous Actions

 

Minutes

Fedora technical plans - gain consensus, highlight vision for technical work and how the pieces fit together. 

  1. 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. 
  2. Align ModeShape implementation with the spec
  3. Foster alternate implementations
  4. Move off ModeShape if a better alternative is identified
  5. Bring along anyone who is currently on ModeShape to the next implementation

Actions