Fedora Council Meeting Agenda 2024-03-13

Continuing the discussion from Upcoming Fedora Council meetings:

Agenda

  • Welcome and Roll Call
  • Revew of tickets tagged with ‘Next Meeting’
    • #484 - Fedora Hackfest Outputs Write up
    • #485 - Update all docs pages with current community initiative information
    • #483 - [2024 Hackfest] Complete the Strategy 2028 logic model
    • #482 - Devising a community schedule to compliment the release schedule
  • Ticket clean up - time allowing
  • Open Floor - time allowing

Looking forward to seeing you there!
Aoife

1 Like

Text Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-03-13/council.2024-03-13-14.00.log.txt
HTML Log: Meetbot Logs
Text Minutes: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-03-13/council.2024-03-13-14.00.txt
HTML Minutes: Meetbot Logs

Meeting ended at 2024-03-13 15:00:24 UTC.

Added council

Ah, I realized that I did not get the email for this because it did not have the council tag. Fixed now!

@amoloney I can do the meeting recap here! Just lifting the Meetbot minutes and we can dig deeper on anything in the specific issue/topic as needed.


#meeting:fedoraproject.org: council

Meeting started by @jflory7:fedora.im at 14:00:33 UTC

Meeting summary

TOPIC:Hellos, welcomes, & greetings (@jflory7:fedora.im, 14:00:56)

TOPIC:Team news and community announcements (@jflory7:fedora.im, 14:07:12)

  • INFO: F40 go/no-go meeting is scheduled tomorrow, Thursday 14 March. (@jflory7:fedora.im, 14:08:01)
  • INFO: Outreachy applicant phase is in full swing with over 150 different active contributors contributing to various projects! (@jflory7:fedora.im, 14:08:25)
  • INFO: F40 Beta missed its target last week. Now targeting current release date of March 19th and go/no-go meeting is here in #meeting:fedoraproject.org at 17:00 UTC. (@jflory7:fedora.im, 14:10:08)
  • INFO: F40 Beta missed its target last week. Now targeting current release date of March 19th and go/no-go meeting is here on 14 March in #meeting:fedoraproject.org at 17:00 UTC. (@jflory7:fedora.im, 14:10:37)
  • INFO: @dcantrell’s birthday was yesterday, woot! (@jflory7:fedora.im, 14:12:01)
  • INFO: Also, FESCo accepted the request to assist CPE’s Product Owner jednorozec in prioritising work requests tagged as infrastructure-projects in the hopes that there will be a curated list for the CPE team, and other folks in the community, to select work from. The discussion on these work requests will be in discussions.fpo and tagged under fedora-infrastructure-projects. (@jflory7:fedora.im, 14:16:13)

TOPIC:Review of tickets tagged with ‘Next Meeting’ (@jflory7:fedora.im, 14:20:10)

  • INFO: #484 - Fedora Hackfest Outputs Write up (@jflory7:fedora.im, 14:20:28)
  • INFO: #485 - Update all docs pages with current community initiative information (@jflory7:fedora.im, 14:20:32)
  • INFO: #483 - [2024 Hackfest] Complete the Strategy 2028 logic model (@jflory7:fedora.im, 14:20:35)
  • INFO: #482 - Devising a community schedule to compliment the release schedule (@jflory7:fedora.im, 14:20:38)

TOPIC:#484 - Fedora Hackfest Outputs Write up (@jflory7:fedora.im, 14:20:50)

  • LINK: Issue #484: Council Hackfest Outputs Write-Up - tickets - Pagure.io (@jflory7:fedora.im, 14:20:55)
  • LINK: https://docs.google.com/document/d/18h6nna1vyFLM_TAvi-BoeTNIllEqj0yofZnF4REpfxE/edit?usp=sharing (@jflory7:fedora.im, 14:23:11)
  • INFO: Q: Who will author the post(s)? A: The git forge announcement will be standalone - and that will be from the FPL mattdm. (@jflory7:fedora.im, 14:25:48)
  • AGREED: Mini-series format for the Council Hackfest updates to make it easier to spread the load and to break up our messages into focused points. (@jflory7:fedora.im, 14:26:18)
  • INFO: Proposed mini-series articles: Git Forge Evaluation Update, Bugzilla and Fedora, Community Initiatives, Moving to Matrix & Sunsetting IRC, Fedora Strategy, Elections (@jflory7:fedora.im, 14:30:45)
  • AGREED: A biweekly cadence (ahem, two posts each week) for a six-week period. (@jflory7:fedora.im, 14:32:17)
  • AGREED: REVISED: A biweekly cadence (ahem, two posts each week) for a three-week period. (@jflory7:fedora.im, 14:33:34)
  • INFO: Dropping FPCA Decision as a Council Hackfest blog post, but acknowledging we need a policy draft first to drive more conversation there. (@jflory7:fedora.im, 14:42:35)
  • HALP: Richard Fontana (@ref) to help us come up with a policy that covers the need for the FPCA. (@jflory7:fedora.im, 14:42:51)
  • AGREED: Articles to draft and publish: Fedora Strategy Update, Git Forge Evaluation Update, Bugzilla and Fedora, Community Initiatives (Mentored Projects, CommOps 2.0), Moving to Matrix & Sunsetting IRC, Elections (@jflory7:fedora.im, 14:43:31)
  • ACTION: @mattdm Draft “Fedora Strategy Update” for Community Blog (@jflory7:fedora.im, 14:43:51)
  • ACTION: @amoloney @mattdm Draft “Git Forge Evaluation Update” for Community Blog (@jflory7:fedora.im, 14:44:10)
  • ACTION: @t0xic0der @dcantrell Draft “Bugzilla and Fedora” for Community Blog (@jflory7:fedora.im, 14:44:27)
  • ACTION: @ffmancera @smeragoel Draft “Community Initiative Update - Mentored Projects” for Community Blog (@jflory7:fedora.im, 14:44:48)
  • ACTION: @rwright Draft “Community Initiative Update - CommOps 2.0” for Community Blog (@jflory7:fedora.im, 14:45:04)
  • ACTION: @jflory7 @dcantrell Draft “Moving to Matrix & Sunsetting IRC” for Community Blog (@jflory7:fedora.im, 14:45:28)
  • ACTION: @amoloney Draft “Elections update” for Community Blog (@jflory7:fedora.im, 14:45:43)
  • ACTION: @mattdm Talk to Richard about replacement policy for FPCA (@mattdm:fedora.im, 14:46:21)
  • AGREED: Tentatively aiming for the weeks of April 8th - 26th to run our Council Hackfest mini-series posts. Authors should come with a first go or full draft of their content by the Council meeting on 27 March. We will build out scheduling for the posts based on what is furthest along and urgency of topic. (@jflory7:fedora.im, 14:52:37)
  • ACTION: @bt0dotninja Also support the Community Initiative Update CommOps 2.0 article :slight_smile: (@jflory7:fedora.im, 14:52:59)

TOPIC:#485 - Update all docs pages with current community initiative information (@jflory7:fedora.im, 14:55:04)

TOPIC:Open floor (@jflory7:fedora.im, 14:57:59)

Meeting ended at 15:00:24 UTC

Action items

  • @mattdm Draft “Fedora Strategy Update” for Community Blog
  • @amoloney @mattdm Draft “Git Forge Evaluation Update” for Community Blog
  • @t0xic0der @dcantrell Draft “Bugzilla and Fedora” for Community Blog
  • @ffmancera @smeragoel Draft “Community Initiative Update - Mentored Projects” for Community Blog
  • @rwright Draft “Community Initiative Update - CommOps 2.0” for Community Blog
  • @jflory7 @dcantrell Draft “Moving to Matrix & Sunsetting IRC” for Community Blog
  • @amoloney Draft “Elections update” for Community Blog
  • @mattdm Talk to Richard about replacement policy for FPCA
  • @bt0dotninja Also support the Community Initiative Update CommOps 2.0 article :slight_smile:
  • @rwright Add Fedora Council docs as an action item to the next CommOps Initiative Leads meeting
  • @ffmancera @smeragoel Add Fedora Council docs as an action item to the next Mentored Projects Initiative Leads meeting

People present (lines said)