Dear all,
You are kindly invited to the meeting:
Council (Subproject Report) on 2018-05-30 from 15:00:00 to 16:00:00 US/Eastern
At fedora-meeting(a)irc.freenode.net
The meeting will be about:
The Fedora Council will hold our regular Subproject Report meeting this week
at 3:00pm US/Eastern in #fedora-meeting on irc.freenode.net. All are welcome!
To convert to your local time, run:
date -d 'TZ="US/Eastern" 3pm tomorrow'
This is not an IRC meeting; it will be conducted via video chat.
(We use meet.jit.si, an open source videoconferencing tool.)
This week's primary meeting chair (usually the FPL or FCAIC) will
reply to this message with specific information.
Source: https://apps.fedoraproject.org/calendar/meeting/5237/

Dear all,
You are kindly invited to the meeting:
Council (Open Floor) EARLY MEETING on 2018-05-23 from 12:00:00 to 13:00:00 US/Eastern
At fedora-meeting(a)irc.freenode.net
The meeting will be about:
The Fedora Council will hold our regular Open Floor meeting at 12:00pm
US/Eastern in #fedora-meeting on irc.freenode.net. All are welcome!
To convert to your local time, run:
date -d 'TZ="US/Eastern" 12pm tomorrow'
Open Floor meetings happen every four weeks. They do not have a
preset agenda. Instead, we spend the first few minutes of the
meeting deciding what topics will be discussed. If attendees —
Council members and otherwise — have several topics of general
interest, the primary meeting chair (usually the FPL or FCAIC)
will put them in order, and after a certain amount of time
discussing the first, ask if it's time to move on.
https://fedoraproject.org/wiki/Council_Meetings#Open_Floor_Meetings
Source: https://apps.fedoraproject.org/calendar/meeting/5229/

Dear all,
You are kindly invited to the meeting:
Council (Tickets and Ongoing) on 2018-05-16 from 15:00:00 to 16:00:00 US/Eastern
At fedora-meeting(a)irc.freenode.net
The meeting will be about:
The Fedora Council will hold our regular Tickets and Ongoing meeting
at 3:00pm US/Eastern in #fedora-meeting on irc.freenode.net. All are
welcome!
To convert to your local time, run:
date -d 'TZ="US/Eastern" 3pm tomorrow'
Tickets and Ongoing meetings happen every four weeks. We don't want
to be entirely ticket-driven (since that's a reactive process), but
this helps keep important issues from slipping through the cracks.
https://fedoraproject.org/wiki/Council_Meetings#Tickets_and_Ongoing_Meetings
The primary chair for this meeting (usually the FPL or FCAIC) should
reply to this message with this week's agenda.
Source: https://apps.fedoraproject.org/calendar/meeting/5247/

I'd like to talk about adding an randomized, rotating UUID to DNF and
rpm-ostree updates which we could use to better count installed
systems. The IP-based counting we currently use is deeply flawed, and
we'd really benefit from getting more accurate numbers.
This would
* let us make better strategic decisions based on our actual base of
installed systems, and
* help us demostrate growth and impact to various sponsors.
To be completely candid: this would be incredibly useful as I advocate
for Fedora within Red Hat, but no one @redhat has directed me to ask
for it. And its *not* just Red Hat — this would be useful in talking to
our various hardware partners too and other potential sponsors.
Long ago, we had Smolt, but this was opt-in and didn't present a very
complete picture. I'd like to propose we do something similar to what
openSUSE describes here: https://en.opensuse.org/openSUSE:Statistics.
That is: A completely random UUID used only for this purpose, and used
for counting rather than tracking.
We could refresh the UUID periodically (like monthly) to ensure that
long-term tracking wouldn't even be an option (while still
distinguishing between short-lived cloud or test instances). And of
course there would be some way to opt out.
Recently Canonical has implemented a much greater amount of data
collection
https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040139.html,
and while maybe we might want to look at reviving an opt-in system, I
don't think we need that right now. (Historically, we've had a lot of
resistance to similar proposals as opt-out, and the value of opt-in is
low.)
Basically, all I want is that UUID plus CPU arch plus ID, VERSION_ID,
and VARIANT_ID from /etc/os-release. (And, I'd also like to start using
VARIANT_ID for labs, spins, docker images, etc.)
What do you think? Does the suggested plan make sense?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader

Hi,
as part of the preparation for community elections in May 2018, I
would like to ask people to populate Election Questionnaire [1] with
questions people might have for nominees. The Questionnaire already
contains questions from the last elections, however you might add your
own, if you have any. In May 2018 we are going to elect members for
these teams:
* FESCo (4 seats)
* Fedora Council (1 seat)
* Mindshare (1 seat)
You have a time till 2018-May-07 23:59:59 UTC [2] to populate the
Questionnaire with your questions. Then collected questions will go to
the teams when 3 top questions will be selected and will be given to
each candidate to answer before voting period begins as part of
campaign.
[1] https://fedoraproject.org/wiki/Elections/Questionnaire
[2] https://fedoraproject.org/wiki/Elections#Elections_Schedule
Thanks in advance for you contribution,
Jan
--
Jan Kuřík
JBoss EAP Program Manager
Red Hat Czech s.r.o., Purkyňova 99/71, 612 45 Brno, Czech Republic