FYI. As Pingou shared in Wednesday's meeting, here's the timeline for Q3
Reminder, we're tracking our ideas on a Taiga board:
---------- Forwarded message ---------
From: Aoife Moloney <amoloney(a)redhat.com>
Date: Fri, May 29, 2020 at 6:48 AM
Subject: CPE Project Bi-Weekly Report - High Level
To: Brian Exelbierd <bexelbie(a)redhat.com>, Ben Cotton <bcotton(a)redhat.com>,
Karsten Wade <kwade(a)redhat.com>, Matthew Miller <mattdm(a)redhat.com>, Marie
Nordin <mnordin(a)redhat.com>, Rich Bowen <rbowen(a)redhat.com>, Leigh Griffin <
lgriffin(a)redhat.com>, Ant Carroll <ancarrol(a)redhat.com>, Paul Frields <
pfrields(a)redhat.com>, Sarah Finn <sfinn(a)redhat.com>, Pierre-Yves Chibon <
pingou(a)redhat.com>, Brian Stinson <bstinson(a)redhat.com>, Eliska Slobodova <
eslobodo(a)redhat.com>, Dominik Perpeet <dperpeet(a)redhat.com>
As part of improving our communication to stakeholders who represent
community and business needs, I will be sending this high level project
report to stakeholders who are invited to our quarterly planning in advance
of the internal CPE teams upcoming project review sessions as a preview of
what we are looking ar for Q3, and as an opportunity for you to reach out
to me should you have a project you would like to prioritize, and why.
This is at a very high level, so I would encourage you to read the bullet
points below, and then review our project kanban board available here,
which has pdfs of the project briefs attached per card with more granular
detail in advance of our quarterly planning meeting on June 18th
Please note that projects listed as scoped/scoping are not guaranteed to be
worked on in Q3. However, they are projects that have been scoped in enough
detail to make an informed decision on and thus will be considered.
*CPE Review Team Meeting & Members*
- *When: *Thursday 4th June
- *Management:* pfrields, lgriffin, acarroll
- *Product Owner:* amoloney
- *Team Leads:* pchibon, bstinson
- *Agile Practitioner:* sfinn
*CPE Team Q3 Quarterly Planning Session*
- *When:* Thursday 18th June, 1330 UTC
- *Who: *People on this email
*Current Projects in Flux in Q2:*
- AAA replacement - In Progress
- CentOS Stream - In Progress
- Colo Move - In Progress
- Mbbox Upgrade - In Progress
- DNF Backend Counting - Near Completion
- CI Infra - Near Completion
*Guaranteed Projects in Q3*
- CentOS Stream - Scoping
- AAA Replacement - Scoped
- Colo Move - Scoped: IAD2 completion + Needs Scoping: RDU Network remap
*Potential Projects Scoped/Being Scoped for Consideration in Q3*
- Datanomer/Datagrepper - Scoped
- FMN Replacement - Scoped
- Fedora messaging schemas - Scoped
- Image Builder Compose - Scoped with requestor, requires technical
review from team
- Docs CI/CD - Scoped with requestor, requires technical review from team
I hope you find this preview useful and please reach out to me should you
have any questions/concerns/requests you would like to discuss before our
team meets on June 4th.
Kindest regards & have a lovely weekend,
Community Platform Engineering Team
Red Hat EMEA <https://www.redhat.com>
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
You are kindly invited to the meeting:
Council meeting on 2020-05-27 from 10:00:00 to 11:00:00 America/Indiana/Indianapolis
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:
On 5/26/20 12:57 AM, Leigh Griffin wrote:
> A general open tracker with backlog ideas would be helpful especially
> for those wanting to get involved and become an Ambassador. It could add
> help and easily become part of the onboarding process. It would also be
> a strong means to share what's working at local levels and inspire others.
Just curious, is this a different idea from the Fedora Join SIG
on-boarding ticket tracker?
It feels like this might already be the envisioned system but not sure
if there is overlap there.
On 5/26/20 5:33 AM, Joerg Simon wrote:
> So, as long as there is no one willing and able to step up as FAmA to do
> the slogger work and revive this dead patient, give freedom to those who
> invest their time trying to move this to a new
> place(joingroup/advocates) unbiased from the old battlegrounds - the
> time is long overdue to retire the Ambassador Group this will not
> diminish the work and the achievements done in this group in the past.
On 5/25/20 2:35 PM, S.Kemter wrote:
> As you did very well read the ambassador requirements, you can explain
> me surly why your personal wiki page doesnt fullfill the requirements?
Oh, wiki pages are requirements? I don't ever remember this coming up
when I became an Ambassador. How long was that a requirement?
Also, is this before or after we disabled non-CLA+1 wiki account
registrations because of wiki spam?
On 5/25/20 2:35 PM, S.Kemter wrote:
> We have there ambassador who count as highly active but they are just
> active during meetings, the job of the ambassador there is no activity.
Oh, I did not know Ambassadors in any region were meeting regularly. Do
you have links to any recent meetings? I must have missed them!
On 5/25/20 3:59 PM, S.Kemter wrote:
> This isnt bullying, this is exactly marking out how some of this strange
> decisions been made. There been some who had experiences it was never
> looked where the trouble came from and it was just declared a general
The Fedora Code of Conduct asks others to be considerate and to be
respectful. Multiple times in this thread, you make bad-faith
assumptions about the intentions and experiences of others. You are not
being considerate or respectful.
On 5/25/20 10:04 PM, S.Kemter wrote:
> Newcomers dont belong to the Ambassadors, there was long time the idea
> to restrict it even more and make another group mandatory before you
> even can request to become Ambassador
The gate-keeping of the "Ambassador" title has always disturbed me. Now
I better remember why I avoid using the Ambassador title, because some
specific people come and tell me I am not using it right and that it is
for "experienced community members" only.
Whatever being an "experienced community member" means anyways. :-)
Justin W. Flory (he/him)
Hi Mindshare, Stephen, and Fedora Council,
Stephen Snow is working on creating a set of Fedora Moderation
Guidelines for community moderators:
I want to give this community work a call-out because it is
strategically important work to standardize moderation best practices in
a large, decentralized community like Fedora.
Stephen is leading good work here and it is an opportunity to
collaborate instead of starting from scratch. There is great potential
for Fedora to innovate on a new kind of First in open source community
management best practices, aligning with the Friends Foundation.
I'm resharing this conversation from #fedora-mindshare in IRC to the
Mindshare mailing list for context:
> Hello all, I would like to introduce myself. My name is Stephen Snow and I am involved with Fed Magazine, Silverblue, and generally in the community
> I have begun the start of a guidelines document on proper moderator actions
> Originally this document was intended for the ask.fedoraproject.org and discussion.fedoraproject.org sites to be a guide for moderators in difficult topics'
> the link is here https://pagure.io/ModeratorGuidelines/tree/master
> I would invite other Fedora groups to get involved so the document can become a good well rounded GP guide to moderation and community involvement
> @jwf suggested I introduce myself and this doc here
> jakfrost: Is there anything specific you would like feedback on? Or is there a specific topic about the guidelines it might help to discuss?
> It might be a good thing to bring it up in a Mindshare meeting next Wednesday.
> Well, really I was hoping the collective community would be able to grow the documentation around guidelines, especially for new moderators
> I wasn't familiar with Fedora Mindshare meetings
> I started it as a result of difficult moderation situations that arise around Fedora at times, and the problem is compounded when the moderators are new
> These are specific details though, the idea was to create a document that encompasses the core concepts of Fedora and expresses the application of moderation tasks through that lense
> If that helps?
> So to extend the reasoning, the core concepts of Fedora (First, Friends, Freedom, Features) combined with the CoC and the actual tasks of moderation would indicate the need of establishing procedures to follow
> With the intent of having a consistent user experience on our forums, WRT how the moderators handle topics
Justin W. Flory (he/him)