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

Topic	Lead	Notes
Preservation statement Ready to distribute to the community pending any final comments	David
Semantic versioning and release schedule Moving to semantic versioning and managing the change	Andrew
Fedora and Modeshape	Andrew / Stefano
Membership update and final push Projecting $562,250 in funding, only $17,750 short of annual goal ($580,000) Please help reach out to new member prospects	David
Fedora Camp NYC 16 registrants so far Camp starts in about a month	David
CNI Meeting	David
Fedora's upcoming 20th anniversary How should we celebrate with the community?

None mentioned.

Ready to distribute to the community pending any final comments
Short 2-pager explaining what Fedora provides for digital preservation; followup document will contain more detail. Suggest adding to website; send out to mailing list for further community feedback.
Susan: Suggest adding definition of fixity
- ACTION: Susan will add footnote
Dan: Not clear why fixity is listed as both a current feature and upcoming feature
- David: Future refers to potential enhancements related to fixity - may want to clarify language
Next steps for getting it out?
- Send out email that includes context about how/why this document was created
- Who should send? Leadership Group chair (Declan)
  - ACTION: David will follow up with Declan
Stefano: Where should it go on the website?
- David suggests under Features heading, but may need spot to consolidate documents like this (under Resources?)

Moving to semantic versioning and managing the change
Two parts to this issue:
1. Move to strict semantic versioning - seems to be consensus around this
  1. Main reason we have not moved is "Fedora 4" branding, so need to be careful about this change
2. Decide on frequency and nature of releases
  1. Limit number of major releases (i.e. releases that change API in a way that's not backward compatible or require significant backend upgrades)
  2. Consensus seems to be no more than one major release per year (and only when necessary, so could be less than once per year)
Julie: Don't let PR issues stop us from moving forward with semantic versioning
Jonathan: Need to move away from the Fedora 4 brand
Find examples of other products that have undergone similar transitions
- Stefano: Chrome, Firefox?
- Are there other open source examples?
Need to keep in mind people who only follow Fedora casually (i.e. not on mailing lists)
Andrew: Suggest trying to finish up API spec this calendar year then spend following 6 months (first half 2017) to align Fedora implementation with API spec -> Fedora 5.0
Start planning messaging strategy in future calls or meeting at CNI

Suggestion arose on list to replace Fedora backend with something other than Modeshape
Aaron Coburn (Amherst) working in codebase to better separate generic Fedora functionality from Modeshape-specific code
Fedora API spec allows for alternative implementations of Fedora, e.g. Ben Armintor Cavendish proof-of-concept (mainly for sanity testing of API spec)
Schedule F2F meetings after API spec release to discuss designs?
Risk of splintering community or affecting reputation?
- Need to do whatever we can to make sure people in community who might have issues bring those issues to the community to be addressed
Some tension from those coming into repository community from Ruby on Rails background but not library or Java background
- Get Hydra Architecture Working Group more involved?
Next steps?

4. Membership update and final push (David)

7. Fedora's upcoming 20th anniversary (David)