...

1. Welcome to Joanna DiPasquale (now as a Community member) and Roger Smith (replacing Declan Fleming), joining Leaders. Looking for ideas for next year for expanding the Community members - continuing to get better representation on the group. There were two Community member slots and only 1 person (Joanna) was nominated.
   
   
2. Pairing new members to acclimate to Fedora Leaders. Members can add their names to the document and then partner folks up. Pairings haven't been assigned yet, the two columns in the document are just for listing names. Will help to have a smoother onboarding process for new Leaders.
   
   
3.  Fedora Vision and Strategy update (Stefano).
   1. Subgroups have been created to address different aspects of the Strategy and Vision process. Most groups are well staffed now (thank you for volunteering, everyone). Sub-Groups will self-organize into biweekly meetings and report back to Fedora Leaders. The sub-groups can now begin working together.
   2. Also the Guiding Principles has been updated, this document summarizes the Strategy and Vision spreadsheet along with a brief Value Proposition. 
   3. We still will want to create a letter to send the the larger Fedora community.
   4. Great appreciation for everyone in making the time to help move this effort forward!
   5. Gratitude for Stefano for organizing this and making a commitment to this effort!! And for Maurice as well, for the spreadsheet structure and backbone for our work!

4. Voting on Policy for long-term support and Supported JVM

   1. These are not new documents, looking for comments and then voting to make them official.

   2. LTS software will require effort to support and maintain

   3. LTS releases will come with the following guarantees: (from the document)

      • 3 year period of support
      • Ensure stability of the API
      • Ensure compatibility with a supported version of the JVM per: Policy - Supported JVM
      • Ensure backporting of critical bug fixes and security patches
      • Provide documentation and tooling for migration from one LTS to the next

   4.  Next steps - an email to the Leadership group looking for support to both of these policies.

   5. Question: what are the current LTS versions? What is the overlap with the next LTS (if given a three year support window), could it be that at times you have three supported versions, in terms of the window of three years? (ex: two LTS versions and the current release)
      1. Suggest 4.7 the LTS, b/c 5.0 reflects a significant change
      2. Suggest that there be overlap, that we don't wait the full three years between LTS versions. But might not be possible to have every time. Will want to consult with Committers and Leadership group about this topic.
   6. Question: can you estimate the cost of the LTS versions 
      1. Can identify significant costs , budgeting with milestones (tooling, breaking changes, etc)
      2. Not sure quantifying the costs of the effort is possible in all cases

Action Items 

1. Draft letter about Strategy and Vision (Stefano), along with executive summary (David will get in touch with Aaron Choate who offered to draft the summary), to send out to the Fedora community. 
2. Voting on the Policy for long-term support and Supported JVM will happen over email soon.