fedora-commops

Community Operations, a.k.a. CommOps, addresss community infrastructure by providing tools, resources, and utilities for different sub-projects to improve communication across Fedora  |  https://fedoraproject.org/wiki/CommOps

#138 "Top Badgers" of 2017

Created 6 months ago by jflory7
Modified 4 months ago

Summary

Interview the top five badge earners of 2017 about their work in Fedora, publish Community Blog series with their interviews

(This is also a great task for someone to get started with and also get to know some of the Fedora community!)

Background

There are two benefits to this:

  1. Recognizing contributors for hard work and featuring them on the Community Blog
  2. Share motivation and advice for newcomers / other community members to earn more badges (thus, participate in the community)

We ran this before in the past. See the 2015 discussion on the idea. There are also three example articles:

  1. “Top Badgers” of 2015: William Moreno (williamjmorenor)
  2. “Top Badgers” of 2015: Major Hayden (mhayden)
  3. “Top Badgers” of 2015: Piotr Popieluch (piotrp)

Details

This task includes some research and interviews. First, reach out to the top five badge earners of 2017 to ask them if they would like to be interviewed and featured on the Community Blog. In 2015, we used these questions:

  1. You earned a lot of badges this year. For you, what was the most memorable badge and why?
  2. Of the badges you earned this year, which one did you think was easiest? Hardest?
  3. What is your advice to either new or recent contributors who want to earn more badges? Any tips to success?

After collecting interviews, each interviewee gets their own article. These articles are scheduled and spread out over a few weeks.

Action

  1. Interview the top five badge earners of 2017 (using the questions above or new questions too!)
  2. Create Community Blog articles in the style listed from past examples
  3. Schedule articles over one month time period
6 months ago

Metadata Update from @jflory7:
- Issue tagged with: help wanted

Raising my hand to help out here as discussed on the mailing list. I can put together an email draft of the questions working from the Details section above.

5 months ago

Metadata Update from @jflory7:
- Issue tagged with: meeting

Email Draft for 2017 Top Badgers

Hello my name is Luis Roca and I'm a new member of the Fedora Project CommOps team.

We're reaching out to the top five badge earners of 2017 collecting interviews. Each interview will then become a featured article on the Fedora Community Blog, spread out over several weeks .[1]

To participate simply reply with your responses to the questions below:

  1. You earned a lot of badges this year. For you, what was the most memorable badge and why?
  2. Of the badges you earned this year, which one did you think was easiest?
    • Hardest?
  3. What is your advice to either new or recent contributors who want to earn more badges?
    • Any tips to success?
  4. What are you currently working on in the Fedora Project?
    • What can the community look forward to from you in 2018?

Thank you for your time and consideration

Luis Roca
Fedora Project member: CommOps, QA
https://pagure.io/user/roca
https://fedoraproject.org/wiki/User:Roca

Footnote
[1] Example Top Badgers feature published in 2016

Edited 5 months ago by roca

@roca +1, this looks awesome! :thumbsup: Feel free to send this out to the top five badgers. If you need help finding email addresses, please ping us in IRC.

5 months ago

Metadata Update from @jflory7:
- Issue untagged with: help wanted
- Issue assigned to roca
- Issue priority set to: normal (1-2 weeks) (was: minor (3-4 weeks))

Have responses from two of five so far. Considering sending out an email nudge to the others with a deadline if they would like to participate. (Should have placed that in the original)

Would Monday the 26th of March be reasonable? Essentially giving the others the weekend to respond to the interview questions.

Luis

Discussed in 2018-03-26 meeting.


We gave this a quick passover in the meeting, so some folks should take a peek in here to read.

@roca, once you are all finished, we usually request others to ask for review on the CommOps mailing list. Please write to the mailing list when you're finished and ready for final review too.

Thanks for all your time working on these already. :grin:

@roca @jflory7 i want to improve my answers. is this possible??

I answered @bt0dotninja's question in IRC – we can change the answers out any time before publishing. @bt0dotninja, you can email them in private to me and @roca and one of us can update your answers.

Posts reviewed and edited

Thanks @roca for the hard work on these! :raised_hands: I took an editing pass through all the articles and added an introduction block text to all of them. I also added some hyperlinks or fixed a few typos from the interviewees.

Publishing schedule

I think it would be cool to run this series one article a week for all of April. Tuesday is (generally) the best day of the week to publish, so I am spreading out all the articles from Tuesday, April 3 until Tuesday, April 24. Since we are still waiting for one more article (hopefully) from @haghighi, if we get that interview, we can add it to the schedule with no problem.

5 months ago

Metadata Update from @jflory7:
- Issue untagged with: meeting

Howdy everyone! Just looked at my preview, and I noticed an error.

As of the writing of this article, Alessio is the #267 all-time badge earner in Fedora.

Badge count is right, name is wrong. :grin:

@carlwgeorge said…
Badge count is right, name is wrong. 😁

Nice catch! Just edited and fixed it. :100:

The first article goes live tomorrow morning. Since all the posts we have so far are scheduled and done, I closing this ticket as complete.

If any changes or revisions need to be made for scheduled posts, add a comment here or get our attention in IRC to make an edit.

Nice work again, @roca!

4 months ago

Metadata Update from @jflory7:
- Issue close_status updated to: Complete
- Issue status updated to: Closed (was: Open)

Login to comment on this ticket.