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

• Julie Allinson
• Chris Awre
• Carolyn Caizzi (for Evviva Weinraub)
• Robert Cartolano
• Aaron Choate
• Stefano Cossu
• Dan Coughlin 
  
• Tom Cramer
• Jon Dunn (notetaker)
• Declan Fleming 
• Maude Francis
• Mike Giarlo
• Wolfram Horstmann 
• Neil Jefferies
• Debra Kurtz
• Susan Lafferty
• Jonathan Markow
• Steve Marks
• Tom Murphy
• Sandy Payette 
• Matthias Razum
• Robin Lindley Ruggaber
• Dan Santamaria
• Jon Stroop
• Jim Tuttle
• Keith Webster
• Evviva Weinraub
• David Wilcox
• Andrew Woods
• Maurice York 

Agenda

Previous Actions

None mentioned.

Minutes

1.  Preservation statement (David)

• 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?)

2. Semantic versioning and release schedule (Andrew)

• 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

3. Fedora and Modeshape (Andrew/Stefano)

Actions