Forwarding this on to the Mindshare list since Ambassadors is a
moderated/closed mailing list.
-------- Forwarded Message --------
Subject: [Ambassadors] Paris Open Source Summit 2019
Date: Wed, 25 Mar 2020 15:11:24 +0100
From: Emmanuel Seyman <emmanuel(a)seyman.fr>
Reply-To: ambassadors(a)lists.fedoraproject.org
To: ambassadors(a)lists.fedoraproject.org
Sorry about the delay in sending you this report. I forgot (several
times!) to
send this to the list.
I manned a booth at the Paris Open Source Summit (which has always had a NPO
area) back in December promoting Fedora (and Open Source in general).
The transport strike in the Paris region that was going on at the time had a
heavy influence on POSS 2019's attendance. The main problem was that some
organisations were absent but visitors could still meet a good 20 or so,
two of them linked to distributions other than Fedora.
Borsalinux-Fr representatives also paid a price: one of us had more than
two hours of transport (cable car, bus, cable car then a lot of walking) to
arrive at the Docks while carrying the belongings of two
organisations, a good hour of walking
for the other.
The first day was very painful. As a joke, we said that there were more
exhibitors than visitors but I suspect that this was actually true. Some
people came to the booth but, in the end, it was very calm. Given the lack
of visitors, we decided to chat with people from Debian-France, the Mongers
of Perl and OpenFoodFacts. We came across some foreign users including
someone
from India and an Italian. Two people also came to see us and the discussion
turned to LemonLDAP-NG and its availability for RHEL and CentOS 8.x.
It prompted Emmanuel to go to the Worteks stand where he found Clément
Oudot,
the main developer of LemonLDAP-NG. The discussion centered on the various
Perl modules used by the application.
The next day saw more visitors than the first, even if the difficulties in
going from point A to point B in Paris were still huge and the number of
associations was the same as for the first day. The public seemed younger
to us than what we expected but that didn't stop them from asking very
interesting questions.
At the end of the day, Emmanuel went to the Red Hat stand where the stand
organizers were kind enough to give him the Grail: the last red Red Hat
hat they had left: D
Emmanuel
_______________________________________________
ambassadors mailing list -- ambassadors(a)lists.fedoraproject.org
To unsubscribe send an email to ambassadors-leave(a)lists.fedoraproject.org
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/ambassadors@lists.fedoraproje…
Hi,
I will not be able to attend the Tomorrow meeting because I have an
illegible appointment at the same time of the event, but I would like
to make some contributions...
1. It was taking a long time what is happening that will affect the
events where fedora participates and the release parties.. so bad :(
2. Mind-share has some ticket waiting for "needs event report" since
2019... ->
https://pagure.io/mindshare/issues?status=Open&tags=needs+event+report&clos…
3. Talking About the Script., This will help TEAM Group to track
Activity of they users, useful for follow newcomer work-flow in Fedora
Join SIG... and cleaning Inactive Member...
So Sorry and Regards.,
@hhlp
(Posting to many mailing lists for visibility. I apologize if you see
this more times than you'd like.)
You may have already seen my Community Blog post[1] about changing the
Release Readiness meeting process. The meeting has questionable value
in the current state, so I want to make it more useful. We'll do this
by having teams self-report readiness issues on a dedicated wiki
page[2] beginning now. This gives the community time to chip in and
help with areas that need help without waiting until days before the
release.
I invite teams to identify a representative to keep the wiki page up
to date. Update it as your status changes and I'll post help requests
in my weekly CommBlog posts[3] and the FPgM office hours[4] IRC
meeting. The Release Readiness meeting will be shortened to one hour
and will review open concerns instead of polling for teams that may or
may not be there. We will use the logistics mailing list[5] to discuss
issues and make announcements, so I encourage representatives to join
this list.
[1] https://communityblog.fedoraproject.org/fedora-program-update-2020-08/
[2] https://fedoraproject.org/wiki/Release_Readiness
[3] https://communityblog.fedoraproject.org/category/program-management/
[4] https://apps.fedoraproject.org/calendar/council/#m9570
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis