Hi all,
I got to thinking about how to actually use this list (it has seen
zero real usage since its creation) and here's what I came up with:
what if we directed the trac instance at
https://fedorahosted.org/fedora-badges/ to send emails here everytime
there was a new ticket or an update on an existing ticket?
Currently, I'm the only one that is notified of activity there and
keeping me as a bottleneck there is a bad idea longer-term. On the
other hand, this would generate a lot of traffic here (maybe too much).
I'm leaning towards doing it. Does anyone want to weigh in? Any
objections?
#298: Badges (graphics) have no license
-------------------------------------+-------------------------------------
Reporter: | Owner:
churchyard | Status: new
Type: | Keywords:
Bug report | Has a description: 0
Priority: | Artwork status: None
minor | External requirements:
Has a name: | Triaged (triagers only): 0
0 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
When I visit badges.fedoraproject.org, there is no clear information about
the content license, such as, but not limited to, badge designs.
From my POV that means badges are CC BY-SA 3.0 Unported, because of FPCA.
If that being true, I would suggest adding this information to the footer
of the page and also tracking the author of the graphics in YAML and
displaying it on badge details page.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/298>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#303: Speak up series continued
-------------------------------------+-------------------------------------
Reporter: | Owner:
gnokii | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: Proposed
minor | External requirements:
Has a name: | Triaged (triagers only): 0
0 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
continue the Speak Up! IRC meeting series
25 participations
50 participations
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/303>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#307: Badge Artist
-------------------------------------+-------------------------------------
Reporter: | Owner:
riecatnor | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: Concept
minor | External requirements:
Has a name: | Triaged (triagers only): 0
0 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
What the badge should be granted for:
Creating badge artwork
Gnokii came up with the idea of using Italian Renaissance painters Tizian,
Botticelli, Raffael, da Vinci and Michelangelo's greatest and well known
works.
Tizian: venus of urbino with an badger
Botticelli: the birth of the venus done with an badger
Raffael: the angels from his sixtinian madonna, done with badger and panda
da Vinci: the vitruvian badger
Michelangelo: the creation of adam from the sixtin chapel done with panda
bears
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/307>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#296: Get ready!
-------------------------------------+-------------------------------------
Reporter: | Owner:
jreznik | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: None
minor | External requirements:
Has a name: | Triaged (triagers only): 0
0 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
What the badge should be granted for: attending Fedora release readiness
meeting as an active participant (Alpha, Beta, Final)
Badge description (like "You added a co-maintainer to a package. BFF!"):
Something like "Ship it! We're ready for the another awesome release."
Anything else we need to know: could be granted manually, I can prepare
the list or automatically if possible when someone writes 1+ lines during
the meeting (Meetbot is present)/chair (I'll make sure participant get
chair).
Credits for the idea: robyduck
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/296>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#319: A badge for FAD attendees
-------------------------------------+-------------------------------------
Reporter: | Owner:
pjp | Status: new
Type: | Keywords: FAD
New badge idea | Has a description: 0
Priority: | Artwork status: None
major | External requirements:
Has a name: | Triaged (triagers only): 0
0 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
What the badge should be granted for:
We plan to host a Fedora Activity Day(FAD) on 1 Nov 2014. Could we have a
badge for the attendees as a token for their participation?
-> https://fedoraproject.org/wiki/FAD_Pune_Security_1
Badge description (like "You added a co-maintainer to a package. BFF!"):
Ummn -> "FAD Pune, 01 Nov 2014."
Anything else we need to know:
The theme for this FAD is Security. It would be great if the badge design
could show that security aspect somehow.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/319>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#311: Badget for multiple security updates via bodhi
-------------------------------------+-------------------------------------
Reporter: | Owner:
robert | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: None
minor | External requirements:
Has a name: | Triaged (triagers only): 0
0 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
What the badge should be granted for: If somebody submits a single
security update (s)he receives "white hat". But what if somebody submits
10, 50 or 100 security updates?
Badge description (like "You added a co-maintainer to a package. BFF!"):
(sorry, I do not have any good idea)
Anything else we need to know: The basic idea behind is outlined, there is
likely enough people in Fedora who submitted more than just one security
update.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/311>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#318: Badge for Fedora 21 Release Party Owners: "Let's have a party"
-------------------------------------+-------------------------------------
Reporter: | Owner:
robyduck | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: None
minor | External requirements:
Has a name: | Triaged (triagers only): 0
1 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
1 |
-------------------------------------+-------------------------------------
This badges continues existing badge #189 for Release Party Owners. This
time for Fedora 21!
What the badge should be granted for:
FAmSCo want to give all Release Party organizers a release specific badge.
Badge description (like "You added a co-maintainer to a package. BFF!"):
Everyone who organizes a Release Party should get a release specific
badge. Release Parties take place immediately after a new version of
Fedora gets released.
Anything else we need to know:
Although the owners will be known about 1-2 months afte GA release, it
will not be possible to assign the badge automatically, IMHO. Therefore
they have to be assigned manually, following a list FAmSCo will be able to
pass at some point to the Infra team.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/318>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#308: shellshocked
-------------------------------------+-------------------------------------
Reporter: | Owner:
mattdm | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: None
major | External requirements:
Has a name: | Triaged (triagers only): 0
0 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
What the badge should be granted for:
Helping build, test, document, or push the fix for CVE-2014-6271 (and
followups).
Badge description: "You helped us bash the shellshocked bug."
Anything else we need to know:
Like: https://badges.fedoraproject.org/badge/heartbleed-buster
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/308>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#293: Badge for sending patch to a list
-------------------------------------+-------------------------------------
Reporter: | Owner:
elad | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: None
minor | External requirements:
Has a name: | Triaged (triagers only): 0
0 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
What the badge should be granted for: Sending a patch to a fedora mailing
list
Badge description: You sent a patch to a Fedora mailing list!
Anything else we need to know: It's considered a rare event in Fedora to
have patches sent to (most) public lists. We usually use bugzilla and
such, and mailing lists are full of people arguing minor details. Today, a
rare event happened and stickster sent a patch to the desktop list. I feel
this rare event should be awarded with a special badge :)
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/293>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app