Fedora Community Blog: Top Badgers of 2017: Carl George

What is “Top Badgers”?

“Top Badgers” is a special series on the Community Blog. In this series, Luis Roca interviewed the top badge earners of 2017 in the Fedora Project. Not familiar with Fedora Badges? No worries, you can read more about them on the Badges website.

This article features Carl George (carlwgeorge), who clocked in at the #1 spot of badges earned in 2017, with 37 badges! As of the writing of this article, Carl is the #267 all-time badge earner in Fedora.

“You earned a lot of badges this year. For you, what was the most memorable badge and why?”

Flock 2017 Attendee“. This was my first Flock and I had a great time. It was wonderful to put faces with many of the usernames I had come to know.

“Of the badges you earned this year, which one did you think was easiest?”

The easiest was “Baby Badger“. It doesn’t get much easier than logging into the Badges app.

“Hardest?”

The hardest was “Building the Outer Ring (Copr Build V)“. Completing 150 Copr builds wasn’t something I was aiming for, but certainly took a considerable amount of work.

“What is your advice to either new or recent contributors who want to earn more badges?”

Conferences like Flock and Red Hat Summit are great ways to get badges and get to know people in the community.

“What are you currently working on in the Fedora Project?”

Lately I have been submitting new packages and doing pull requests to existing packages to expand the EPEL Python3 stack to help make that an appealing option for RHEL/CentOS users. In 2018 I will continue to do those things and also help with the transition from python34 to python36.

The post Top Badgers of 2017: Carl George appeared first on Fedora Community Blog.


Source From: fedoraplanet.org.
Original article title: Fedora Community Blog: Top Badgers of 2017: Carl George.
This full article can be read at: Fedora Community Blog: Top Badgers of 2017: Carl George.

Advertisement


Random Article You May Like

Leave a Reply

Your email address will not be published. Required fields are marked *

*
*