Reintroductions, reflections, and so forth

Over the last few months on chat.fp.o and at conferences I have started joining into conversations- listening, asking questions, making assertions, telling bad jokes. All this activity has led to a recurring question by many people in the community, “uhh, who are you?”

Oops, it’s been a while since I was active in Fedora so reintroductions are overdue. In short, I am a people manager at Red Hat, responsible for Community Linux Engineering, everything from the system administrators to quality engineers to the FPL and many roles in-between: most of the people who work full time in a community-facing capacity are in my group. This is particularly true of Red Hatters who are responsible for the combined whole, as opposed to individual package maintainers.

But this isn’t just an introduction, this is a reintroduction. My first foray into the Fedora community, beyond just running Fedora, was in 2012 when my team at Red Hat started to explore the potential for ARM servers. We, with many of you, bootstrapped armv7hl, then aarch64. We started with a Seneca College partnership, we gave away hardware, we made ugly uboot hacks, ported hundreds of packages, helped establish the Linaro Enterprise Group to do more ports & standardization, and solved seemingly thousands of circular dependencies- and hired a bunch of great contributors along the way, folks like Marcin Juszkiewicz and Paul Whalen. Several of us took what we learned from the experience and replicated the work inside Red Hat with RHEL 7, first for ppc64le, then aarch64- two architectures that are mainstream in RHEL today, but scarcely existed a decade ago. For me that evolved into driving general RHEL development as an individual, then management, then last year I had the opportunity to come back to support Red Hat’s Linux communities in general and Fedora in particular.

I think it’s fair to say that most of the RHEL management team has, as a whole, tended to be hands-off in Fedora’s affairs. There are some notable exceptions of course, but on average, most people working as managers are less involved in Fedora. There’s no written rule about this, so for my part I’ve inferred that most managers don’t think they have a lot of value to contribute compared to the people who they manage who are engaged in Fedora. Even in writing this blog I feel apprehensive: do I have anything to say people want to hear? Maybe just one thing…

Having come full circle, starting a project in the Fedora community, maturing it in RHEL, learning deeply how RHEL works and shaping it, and now back in a community space, I believe I have one valuable thing to offer: insider perspective. In the coming weeks I will be sharing insights and ideas. I’m not sure where it will lead, but that’s part of the fun of sharing with others, the feedback alters the course. I’d love to hear from you.

(Dup-posting this to devel since the audience may vary).

26 Likes

Welcome back to Fedora! :slight_smile:

Are you saying you’re the new FPL?

1 Like

re-welcome :classic_smiley:

That’s a great project. I look forward to your thoughts. You might put it to the Project Discussion category to increase the outreach and potential for feedback compared to the water cooler.

“Unfortunately, that is a useful approach” :grin:

Just in case you’re not joking: No! As somebody who hasn’t been involved in the community for many years I couldn’t credibly serve as in that role. The FPL is in my organization though and indeed Matthew and I are interviewing new FPL candidates together. Part of my job is to help the FPL be successful.

2 Likes

Hey, thanks!

That’s a good point - I’m trying to follow conventions here, so the introduction is where introductions go, but an ongoing series belongs… elsewhere. This was originally going to go to the community blog, but after looking at content there it didn’t seem like it merited to that kind of significance. I’ll look at project discussion and see if it’s a good fit- seems likely.

Yeah :-/ Some day I hope somebody has a brilliant idea to solve this one. Redundancy can be a wonderful thing, ask any storage admin… but for information distribution, accidentally missing 50% of your desired audience is rough.

Very cool to see you back around Fedora! We should chat about ARM servers sometime :slight_smile:

I’m available! What’s really interesting to me is how RISC-V is following such a similar pattern. Heck, we’re even trying to hire a RISC-V QE for Fedora :slight_smile:

1 Like

Ah, I interpreted your initial post that you wanted to do your projects here in the Discourse, so I just wanted to suggest changing category within Discourse. My bad. But yes, Discourse might be the best place anyway: @mattdm already experimented with blog-like topics → Where's Matthew this week (an experiment in Fedora Project Leader visibilty...) (you cannot see the answers and subsequent posts because the topic was set to hide them after 6 months)

If you seek to reach the active contributors from different areas (of our very diverse community with its widespread upstream integrations) and to get “serious feedback and foster discussions & exchange” from/with them, Project Discussion might be the best place. You might note that many people from the devel mailing list are also following here (but much less vice versa).

What I did in the past: when discussions here are interesting also for devel, while it was not useful to separate the discussion (or if a discussion came up here that lacked the perspective of devel people), I just posted in devel a short elaboration, the link to the topic here and asked to keep the discussion here.

Feel free to let me know if I can help with anything around our Discourse. I think what you have planned could have a positive impact (I remember many discussions over the years in which members were worried about RH internals’ affecting the community in change proposals or more generally on the long term, or limited legitimacy in the community of RH decisions/actions, because the reasoning was not known/understood) → maybe that can add some new perspectives for that or so. In any case, it’s will be interesting to see how that project will evolve.

I guess this “problem”/“issue” has become an integral part of the agency of our community. We are so deeply integrated with diverse upstreams and different fields and AoE/SIGs that a “one size fits all” is hardly to achieve. But the issue also keeps a discussion ongoing and reappearing, which regularly creates new incentives and interactions between different parts of the community, who otherwise might not interact with each other → so it also has something good :classic_smiley:

1 Like