Despite what Fedocal thinks, there is no Fedora Council meeting tomorrow, as most Council members will be traveling to Budapest for Flock. On Tue, Aug 6, 2019 at 6:00 AM <bcotton@xxxxxxxxxx> wrote: > > Dear all, > > You are kindly invited to the meeting: > Council meeting on 2019-08-07 from 10:00:00 to 11:00:00 America/Indiana/Indianapolis > At fedora-meeting-1@xxxxxxxxxxxxxxxx > > The meeting will be about: > The Fedora Council will hold our regular meeting at 10:00am US/Eastern in #fedora-meeting-1 on irc.freenode.net. All are welcome! > > To convert to your local time, run: > > date -d 'TZ="US/Eastern" 10am tomorrow' > > We will begin with a review of open tickets and then have open floor time for discussion. > > The primary chair for this meeting (usually the FPgM, FPL, or FCAIC) should reply to this message with this week's agenda. > > > More information available at: > [https://fedoraproject.org/wiki/Council_Meetings](https://fedoraproject.org/wiki/Council_Meetings) > > > Source: https://apps.fedoraproject.org/calendar/meeting/9579/ > > _______________________________________________ > council-discuss mailing list -- council-discuss@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to council-discuss-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ council-discuss mailing list -- council-discuss@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to council-discuss-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx