#1 Fedora Personal Systems Working Group Action List
Opened by timaeos. Modified

The Council approved the creation of the Personal Systems Working Group (tentatively) but explicitly approved the creation of a KDE Edition. https://pagure.io/Fedora-Council/tickets/issue/504

The next part of the plan is to address the caveats provided by the council members and also create the change proposal that integrates the feedback received:

Post Approval Actions

  • [ ] Marketing Story Clarification (Meeting)
  • [ ] Quality Scope Definition and Improvement
  • [ ] Change Proposal Creation
  • [ ] Fedora Personal Marketing Icons / Image Development
  • [ ] Fedora Personal Website Creation
  • [ ] Fedora Personal Announcement Article (Fedora Magazine / Fedora Podcast Episode)
  • [ ] Fedora Personal Systems Working Group Logistics and Administration work (i.e. Separation of Domains)
    • [ ] Meeting Establishment
    • [x] Matrix Channel Creation Matrix Channel
    • [ ] SIG Coordination and Communication (e.g. inviting stakeholders)
      • [x] KDE Sig - @ngompa @tdawson
      • [x] Asahi Remix - @dcavalca
      • [x] Gaming SIG - @q5sys @dogphilosopher
      • [ ] Mobility SIG - ?
      • [x] (Downstream) Bazzite - @dogphilosopher
      • [x] (Downstream) Nobara - @gloriouseggroll
    • [ ] Mailing List Creation
    • [x] Pagure or Discourse Forum Creation Pagure
    • [ ] Policy and Procedures Docs Creation
    • [ ] Fedocal Calendar Creation
    • [ ] FAS Group Creation

Metadata Update from @ngompa:
- Issue set to the milestone: Fedora Linux 42

Maybe: Take ownership of #gaming:fedoraproject.org (And the defunct gaming sig)?

Maybe: Take ownership of #gaming:fedoraproject.org (And the defunct gaming sig)?

It looks like ngompa and q5sys are going to be taking over the defunct gaming sig
https://pagure.io/fedora-kickstarts/pull-request/1073

I still haven't heard word from the people in the mobile land of fedora yet. There's also the RISC-V and ARM people that have some intersection with these due to device enablement coordination

The tentative discussion for meeting cadence is ~ 2 weeks in the beginning until things are stable. The first few meetings will likely be about vision alignment and general administrative tasks and action delegation. If there are people interested in taking on any of the tasks already listed in this tickets, please speak up.

Until a dedicated meeting time can be determined, @ngompa proposed using the standing KDE Sig meeting place and time (Mondays at 1300 US/Eastern, Meeting link: https://meet.kde.org/b/ale-swq-39j)

@ngompa What is the date you'd like to have the first meeting?

For those with particularly busy schedules, please highlight what times are most feasible. @dogphilosopher mentioned that they will be on vacation for 2 weeks starting Monday (11/11/2024)

Should I post a when2meet link for people to vote on for people to give input on when they would be consistently free?

Separately, there are some administrative clarifications that might be worth discussing in the first meeting
1) What is the cohesive vision for the WG? (e.g. does this comment capture some of the vision?)
2) Are there some already known shared problem domains / challenges that should be prioritized in terms of meeting agenda? (e.g. image deliverable migration to kiwi, shared development work for experience improvement, baseline quality scope for deliverables etc)
3) Are there any SIG-wide change systems that need to be created (e.g. voting systems, proposal systems)
4) Who is willing to chair the first meeting and who is willing to write up a brief agenda for it?

Metadata