#107 Beats Writer
Closed None Opened 10 years ago by sparks.

What the badge should be granted for:
Writing a beat for the Fedora Release Notes.

Badge description (like "You added a co-maintainer to a package. BFF!"):
You helped keep everyone up to date by being a Beat Writer!

Anything else we need to know:
This would be a manual award given by the Docs Project lead (currently randomuser).


Idea: How about a cute name like "Workin' a Beat".

Idea: How about a cute name like "Workin' a Beat".

To provided continued incentive for participation in beat writing, this should either be a series badges unique to each release. A series would be easier for artwork and such, but a unique, limited window of availability badge for contributing to the Beats for a specific release provides more incentive. I'd really prefer the latter, if we can pull it off.

To provided continued incentive for participation in beat writing, this should either be a series badges unique to each release. A series would be easier for artwork and such, but a unique, limited window of availability badge for contributing to the Beats for a specific release provides more incentive. I'd really prefer the latter, if we can pull it off.

Maybe someone from the design-team could comment on how difficult or not it would be to produce a template for this badge that could be easily updated for each new release.

Some image with a big "F21" on it somewhere. In inkscape can you just textually update that to "F22" without any pains?

Maybe someone from the design-team could comment on how difficult or not it would be to produce a template for this badge that could be easily updated for each new release.

Some image with a big "F21" on it somewhere. In inkscape can you just textually update that to "F22" without any pains?

I understand the intent, but I'm concerned that per-release badges will start an avalanche of badge creation: Why not make ''all'' the badges release-specific?

I'd rather see multiplier badges. Either based on number of beats (if you write 5 beats for Fedora N you get the 5x Beat Writer Badge), number of releases (if you write a beat for Fedora N through Fedora N+5 you get the 5x Beat Writer Badge), or both (if you write 3 beats for Fedora N and 2 beats for Fedora N+1 you get the 5x Beat Writer Badge).

My way is a little more complicated, but since it's a manual process anyway, it's not too much more difficult to just plop it into a spreadsheet and award at the appropriate time.

I understand the intent, but I'm concerned that per-release badges will start an avalanche of badge creation: Why not make ''all'' the badges release-specific?

I'd rather see multiplier badges. Either based on number of beats (if you write 5 beats for Fedora N you get the 5x Beat Writer Badge), number of releases (if you write a beat for Fedora N through Fedora N+5 you get the 5x Beat Writer Badge), or both (if you write 3 beats for Fedora N and 2 beats for Fedora N+1 you get the 5x Beat Writer Badge).

My way is a little more complicated, but since it's a manual process anyway, it's not too much more difficult to just plop it into a spreadsheet and award at the appropriate time.

ralph, not too hard, i'd say we just use the same process we did for the supplemental wallpaper ones.

As for the artwork for this one, i initially thought of a hat with the press tag out of it. But those hats are typically fedoras, and we try to avoid actaully picturing a fedora on artwork...

does anyone else have an other ideas?

ralph, not too hard, i'd say we just use the same process we did for the supplemental wallpaper ones.

As for the artwork for this one, i initially thought of a hat with the press tag out of it. But those hats are typically fedoras, and we try to avoid actaully picturing a fedora on artwork...

does anyone else have an other ideas?

Maybe a panda scribbling in a notebook with his tongue sticking out the side of his mouth as if he's concentrating on something. I'm imagining a white-house correspondent panda here listening to a speech and taking notes for the beat she's writing.

Maybe a panda scribbling in a notebook with his tongue sticking out the side of his mouth as if he's concentrating on something. I'm imagining a white-house correspondent panda here listening to a speech and taking notes for the beat she's writing.

The writing panda sounds like a good concept for any docs related badge. The press tag in the hat led me to an image search for "press badge" - would there be room in the template for an actual badge-style graphic, complete with awkward badge-style panda mugshot?

It would be nice to see some movement here. Are we only waiting on art, or is a consensus needed on serial vs release-ly awarding? Despite the attraction of unique badges, I realize that a cumulative one would be much easier to implement and would not object to it.

The writing panda sounds like a good concept for any docs related badge. The press tag in the hat led me to an image search for "press badge" - would there be room in the template for an actual badge-style graphic, complete with awkward badge-style panda mugshot?

It would be nice to see some movement here. Are we only waiting on art, or is a consensus needed on serial vs release-ly awarding? Despite the attraction of unique badges, I realize that a cumulative one would be much easier to implement and would not object to it.

FYI, we can grant authorization to users now to award select badges themselves which removes the technical block to this one. immanetize can hand it out as he sees fit.

FYI, we can grant authorization to users now to award select badges themselves which removes the technical block to this one. immanetize can hand it out as he sees fit.

[[Image(workin'-a-beat.svg)]]

[[Image(workin'-a-beat.svg)]]

[[Image(workin'-a-beat-5.svg)]]

[[Image(workin'-a-beat-5.svg)]]

[[Image(workin'-a-beat-10.svg)]]

[[Image(workin'-a-beat-10.svg)]]

[[Image(workin'-a-beat-25.svg)]]

[[Image(workin'-a-beat-25.svg)]]

What a cute, hard-working panda! :) Setting to design approved!

What a cute, hard-working panda! :) Setting to design approved!

Replying to [comment:4 bcotton]:

I'd rather see multiplier badges. Either based on number of beats (if you write 5 beats for Fedora N you get the 5x Beat Writer Badge), number of releases (if you write a beat for Fedora N through Fedora N+5 you get the 5x Beat Writer Badge), or both (if you write 3 beats for Fedora N and 2 beats for Fedora N+1 you get the 5x Beat Writer Badge).

We had some out-of-band discussion about this badge and agreed on a cumulative award, total carried across releases.

Replying to [comment:4 bcotton]:

I'd rather see multiplier badges. Either based on number of beats (if you write 5 beats for Fedora N you get the 5x Beat Writer Badge), number of releases (if you write a beat for Fedora N through Fedora N+5 you get the 5x Beat Writer Badge), or both (if you write 3 beats for Fedora N and 2 beats for Fedora N+1 you get the 5x Beat Writer Badge).

We had some out-of-band discussion about this badge and agreed on a cumulative award, total carried across releases.

Hi folks, I apologize for a comment on this very old ticket. Could someone please explain what writing a beat for the Release Notes meant? I am not sure whether this is still in practice anywhere with the Fedora Docs Team.

I ask because I was curious about reviving this badge series, with a focus on the recent workshops that folks like @hankuoffroad and @pboy organized for the team. I am wondering if we can use these classic badges as an incentive for participating in writing "beats" as a shared general team activity or if that is disingenuous to the original purpose of this badge, i.e. writing a specific deliverable for the Release Notes.

Metadata Update from @jflory7:
- Custom field artwork adjusted to None
- Custom field concept_review_passed adjusted to None (was: 0)
- Custom field has_complete_yaml reset (from None)
- Custom field has_description adjusted to on (was: 1)
- Custom field has_name adjusted to on (was: 1)
- Custom field needs_manual_award adjusted to on (was: 1)
- Custom field triaged adjusted to on (was: 1)
- Issue close_status updated to: None (was: Pushed)

4 months ago

Login to comment on this ticket.

Metadata
Attachments 10
Attached 10 years ago View Comment
Attached 10 years ago View Comment
Attached 10 years ago View Comment
Attached 10 years ago View Comment
Attached 10 years ago View Comment
Attached 10 years ago View Comment
Attached 10 years ago View Comment
Attached 10 years ago View Comment
Attached 10 years ago View Comment
Attached 10 years ago View Comment