fedora-council-meeting
MINUTES

#meeting:fedoraproject.org: Fedora Council Meeting

Meeting started by @amoloney:fedora.im at 14:02:58 UTC

Meeting summary

  1. TOPIC:#499: Request for Trademark Approval for "Fedora Ready" (@jflory7:fedora.im, 14:08:45)
    1. INFO: Fedora Ready is a program to support vendors who ship or support Fedora on their computers. It is not a certification program or a legal partnership with hardware vendors. (@jflory7:fedora.im, 14:08:45)
    2. LINK: https://pagure.io/Fedora-Council/tickets/issue/499 (@jflory7:fedora.im, 14:08:45)
    3. ACTION: @t0xic0der @bookwar @dcantrell @bt0dotninja @mattdm @smeragoel @ffmancera @rwright Review #499 (Fedora Ready request) and add a vote or ask a question. (@jflory7:fedora.im, 14:10:59)
    4. LINK: https://pagure.io/fedora-logos/pull-request/24 (@jflory7:fedora.im, 14:12:07)
    5. LINK: https://pagure.io/Fedora-Council/tickets/issue/460 (@jflory7:fedora.im, 14:12:07)
    6. INFO: "As part of transition to SPDX identifiers in Fedora [1] we found that fedora-logos uses proprietary and non-free license [2]. There are several options [3]. And most appealing is to publish a the files under public license. I submitted the pull-request with this change." (@jflory7:fedora.im, 14:12:07)
  2. TOPIC:#460: Relicense Fedora-logos (@jflory7:fedora.im, 14:12:07)
    1. AGREED: Deferred for further input by Fedora Legal / Richard Fontana on pros/cons to using an open license for our trademark. Still not clear on what an open license might mean for our trademark policy. There are examples of both out there (openSUSE uses Creative Commons, Canonical/Ubuntu uses its own policy). Once we better understand the pros/cons, we can make a final decision for what license to use or to draft ourselves an exception to use the logos in Fedora. (@jflory7:fedora.im, 14:27:49)
    2. INFO: Ticket last updated in June 2023. (@jflory7:fedora.im, 14:29:18)
  3. TOPIC:#435: Rework the SIG documentation (@jflory7:fedora.im, 14:29:18)
    1. LINK: https://pagure.io/Fedora-Council/tickets/issue/435 (@jflory7:fedora.im, 14:29:18)
    2. INFO: The idea is that we also need to collect resources for SIGs into a single place so that people have a good entry point to all the tools available for them. (@jflory7:fedora.im, 14:29:18)
    3. AGREED: Unsure whether the Fedora Council is the right group to drive this, even though the idea is great. Our capacity to do this work is limited. We will leave the next two weeks for final comments, and if we are unable to staff the ticket by the next Council meeting, we will close this ticket as `declined`. (@jflory7:fedora.im, 14:36:13)
    4. INFO: "But the first part "If it is proprietary, it cannot be included in Fedora. (Binary firmware is the only exception to this" is not a legal requirement. We could (but, um, clearly will not) choose to start shipping proprietary software which is licensed in a way that lets us redistribute it. It's our policy choice that informs the license rules." (@jflory7:fedora.im, 14:38:50)
  4. TOPIC:#411: Policy proposal: formalizing Fedora's open source requirements (@jflory7:fedora.im, 14:38:50)
    1. INFO: Related to discussion about abolishing the Fedora Project Contributor Agreement (FPCA). (@jflory7:fedora.im, 14:38:50)
    2. LINK: https://pagure.io/Fedora-Council/tickets/issue/411 (@jflory7:fedora.im, 14:38:50)
    3. AGREED: To move this forward, the Council will start work at the Flock 2024 Council hackfest on determining principles of what the Fedora open source policy should do and not do. After Flock, we will continue to workshop this with other Council members not at Flock. Once we are happy with the principles, we will share them with Richard Fontana for collaborating on turning the principles until an actual policy that covers our Freedom Foundation and also supersedes the FPCA. (@jflory7:fedora.im, 14:45:53)
    4. ACTION: @amoloney Add a "Fedora open source policy values" topic to the Flock 2024 Council hackfest agenda (@jflory7:fedora.im, 14:46:10)
    5. LINK: https://pagure.io/Fedora-Council/tickets/issue/391 (@jflory7:fedora.im, 14:49:42)
  5. TOPIC:#391: Fedora Code of Conduct Supplemental Documentation - CoC (@jflory7:fedora.im, 14:49:42)
    1. LINK: https://docs.fedoraproject.org/en-US/council/policy/coc-response-policy/ (@jflory7:fedora.im, 14:50:29)
    2. AGREED: Likely revisit after Flock. We have supplementary documentation in the Code of Conduct now and this was published following the February 2023 Council hackfest. However, the contradicting Council policy about the Code of Conduct from 2018 needs to be retired, since our current CoC Committee structure supersedes the old policy. After Flock, we can conduct the policy change policy to retire the old CoC policy. (@jflory7:fedora.im, 14:54:34)
  6. TOPIC:Open floor (@jflory7:fedora.im, 14:55:53)
    1. IDEA: Save time at our Flock 2024 Council hackfest to review the ticket queue and empower non-Initiative Council members to own a ticket and advance our backlog of needed work. (@jflory7:fedora.im, 14:58:56)


Meeting ended at 15:00:03 UTC

Action items

  1. @t0xic0der @bookwar @dcantrell @bt0dotninja @mattdm @smeragoel @ffmancera @rwright Review #499 (Fedora Ready request) and add a vote or ask a question.
  2. @amoloney Add a "Fedora open source policy values" topic to the Flock 2024 Council hackfest agenda


People present (lines said)

  1. @jflory7:fedora.im (129)
  2. @amoloney:fedora.im (32)
  3. @msuchy:matrix.org (11)
  4. @zodbot:fedora.im (4)
  5. @jonatoni:fedora.im (4)
  6. @t0xic0der:fedora.im (3)
  7. @bt0dotninja:fedora.im (3)
  8. @meetbot:fedora.im (2)