DevHeads.net

Schedule for Friday's FESCo Meeting (2019-05-24)

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 15:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/UTCHowto" title="http://fedoraproject.org/wiki/UTCHowto">http://fedoraproject.org/wiki/UTCHowto</a>

or run:
date -d '2019-05-24 15:00 UTC'

Links to all issues to be discussed can be found at:
<a href="https://pagure.io/fesco/report/meeting_agenda" title="https://pagure.io/fesco/report/meeting_agenda">https://pagure.io/fesco/report/meeting_agenda</a>

= Discussed and Voted in the Ticket =
knot / knot-resolver package rebase exception request
<a href="https://pagure.io/fesco/issue/2129" title="https://pagure.io/fesco/issue/2129">https://pagure.io/fesco/issue/2129</a>
DECISION (+3, 0, -1)

= Followups =
No open tickets

= New business =
No open tickets

= Open Floor =
Meeting will be held for Open Floor

For more complete details, please visit each individual
issue. The report of the agenda items can be found at
<a href="https://pagure.io/fesco/report/meeting_agenda" title="https://pagure.io/fesco/report/meeting_agenda">https://pagure.io/fesco/report/meeting_agenda</a>

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
<a href="https://pagure.io/fesco" title="https://pagure.io/fesco">https://pagure.io/fesco</a>, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.

Comments

Re: Schedule for Friday's FESCo Meeting (2019-05-24)

By Zbigniew =?utf-... at 05/24/2019 - 09:13

On Fri, May 24, 2019 at 08:33:06AM -0400, Stephen Gallagher wrote:
I think this is a typo, nobody voted against.

Zbyszek

Re: Schedule for Friday's FESCo Meeting (2019-05-24)

By Stephen Gallagher at 05/24/2019 - 09:23

On Fri, May 24, 2019 at 9:15 AM Zbigniew Jędrzejewski-Szmek
< ... at in dot waw.pl> wrote:

Yup, definitely a typo, sorry about that.