Fedora Council meeting minutes for 2021-01-21

[mattdm (Matthew Miller)]

#fedora-meeting: Council (2021-01-21)

Meeting started by bcotton_ at 18:00:02 UTC. The full logs are available
at

council - Logs

.

Meeting summary

• Introductions, Welcomes (bcotton_, 18:00:07)

• Today’s agenda (bcotton_, 18:03:14)

• Logo adoption timeline (bcotton_, 18:03:16)

• Fedora annual survey (bcotton_, 18:03:17)

• Add the Fedora goal of having complete integrated system (bcotton_,
  18:03:19)

• Your topics here! (bcotton_, 18:03:20)

• Logo adoption timeline (bcotton_, 18:03:40)

  • LINK: Issue #249: Logo Adoption Timeline - tickets - Pagure.io
    (bcotton_, 18:03:42)
  • We have legal clearance to move forward with the new logo as
    designed by mizmo (bcotton_, 18:04:21)
  • LINK: https://koji.fedoraproject.org/koji-static/images/koji.png
    (mattdm, 18:21:19)
  • ACTION: mattdm to coordinate a plan for the logo rollout and come
    back to the Council with a proposal (bcotton_, 18:24:30)

• Fedora annual survey (bcotton_, 18:26:12)

  • LINK: Issue #327: Let's run a yearly Fedora survey - tickets - Pagure.io
    (bcotton_, 18:26:14)
  • Previously, bookwar said she’d draft a proposal for this (bcotton_,
    18:26:15)
  • ACTION: bookwar to review the content from the survey etherpad and
    repost into the ticket as a proposal (bcotton_, 18:38:22)

• Add the Fedora goal of having complete integrated system (bcotton_,
  18:39:08)

  • LINK: Issue #280: Add the Fedora goal of having complete integrated system - tickets - Pagure.io
    (bcotton_, 18:39:09)
  • From vF2F: mattdm and bookwar to find a place to fit “upstream
    first” and then add in the contents of
    Objectives - Fedora Project Wiki
    (bcotton_, 18:39:11)
  • We’ll come back to this next time (bcotton_, 18:40:56)

• Next meeting (bcotton_, 18:41:26)

• The next regular business meeting is Thursday 4 Feburary
  (bcotton_, 18:41:28)

• Do we have anything to announce? (bcotton_, 18:41:37)

• This is a regular check to make sure we’re communicating to the
  contributor (via CommBlog) and user (via Magazine) communities
  (bcotton_, 18:41:39)

• LINK:
  Community Outreach Revamp Objective – Fedora Community Blog
  (riecatnor, 18:43:40)

• LINK:
  Fedora Objective proposal: Community Outreach Revamp - #4 by mattdm
  (riecatnor, 18:44:05)

• LINK: Issue #248: FOSDEM 2021 - Stand submission - mindshare - Pagure.io (riecatnor, 18:45:50)

• Mindshare committee is organizing a presence at fosdem 2021
  (riecatnor, 18:45:58)

• Dashboard check (bcotton_, 18:46:52)

• LINK: Untitled :: Fedora Docs
  (bcotton_, 18:46:54)

• Open floor (bcotton_, 18:48:31)

  • LINK: Issue #102: Redirect "Board public IRC meetings" wiki page to "Council ticket queue" docs page? - council-docs - Pagure.io
    (jwf, 18:50:12)
  • LINK: Issue #103: Update references of mailing list to Discourse - council-docs - Pagure.io
    (jwf, 18:50:21)
  • LINK: Issue #189: D&I Team Virtual Meetup 2021 - fedora-diversity - Pagure.io (riecatnor,
    18:50:36)
  • LINK:
    Fedora Looks To Overhaul Its Community Outreach - Phoronix
    (jwf, 18:57:38)
  • LINK: Pets of Fedora!
    (mattdm, 18:58:12)

Meeting ended at 19:00:19 UTC.

Action Items

• mattdm to coordinate a plan for the logo rollout and come back to the
  Council with a proposal
• bookwar to review the content from the survey etherpad and repost into
  the ticket as a proposal

Action Items, by person

• bookwar
  • bookwar to review the content from the survey etherpad and repost
    into the ticket as a proposal
• mattdm
  • mattdm to coordinate a plan for the logo rollout and come back to
    the Council with a proposal
• UNASSIGNED
  • (none)

People Present (lines said)

• mattdm (64)
• bcotton_ (60)
• riecatnor (36)
• jwf (35)
• King_InuYasha (33)
• bookwar (19)
• zodbot (17)
• mizmo (11)
• x3mboy (8)
• spot (5)
• Conan_Kudo (1)
• dcantrell (1)
• bcotton (1)
• bookwar dcantrell jwf riecatnor spot mattdm bcotton asamalik x3mboy (0)

Generated by MeetBot_ 0.1.4

… _MeetBot: MeetBot - Debian Wiki

[jflory7 (Justin W. Wheeler (JWW))]

I think the automation still needs some tweaking.

[mattdm (Matthew Miller)]

Apparently.

[mattdm (Matthew Miller)]

I actually know what the problem is: the meeting minutes are formatted in ReStructured Text, which looks like Markdown but isn’t, and Discourse is interpreting the incoming mail badly as a result. I could munge it on the fly, but Meetbot is sending it with a base-64 encoded message body which means I can’t do a horrible on-the-fly hack and instead need to actually unpack the message.

[jflory7 (Justin W. Wheeler (JWW))]

@mattdm

the meeting minutes are formatted in ReStructured Text, which looks like Markdown but isn’t, and Discourse is interpreting the incoming mail badly

I also wonder if there is a ReStructuredText plugin for Discourse. Not saying a plug-in is an easier solution for sure, but might be one way to get the desired effect with less work

It’s something I can look into later this week if someone else doesn’t beat me to it.

[mattdm (Matthew Miller)]

@jflory7

I also wonder if there is a ReStructuredText plugin for Discourse. Not saying a plug-in is an easier solution for sure, but might be one way to get the desired effect with less work

It’s something I can look into later this week if someone else doesn’t beat me to it.

Without going to the Business plan (or self-hosting, of course) we’re limited in what plugins we can use. So I think figuring out how to get Meetbot to send Markdown is probably a lot easier