#433: Fedora Developer Portal badges
-------------------------------------+-------------------------------------
Reporter: | Owner: phracek@…
phracek | 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 |
-------------------------------------+-------------------------------------
Badge description (like "You added a co-maintainer to a package. BFF!"):
We would like to create a badge or badges for folks who help us with
Fedora Developer Portal.
Help the badges team understand what this idea is all about. If this
badge is awarded for certain kinds of activities:
1) What are those activities?
Everybody who create a content should receive a badge for helping with
community and developers.
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
The folks who create a content can be packagers, newcomers, veterans,
users or everybody who can help other folks for developing on Fedora
3) Why are they doing them (is this a means to a different end?)
4) When do they do them (every day? once a year?)
Folks who creates contents do it once a year, I guess.
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
A content can be created via GitHub interface, or editor which is able to
write a MarkDown structure.
Lastly, do you have any ideas for artwork concepts?
Fedora Developer Portal is available here: developer.fedoraproject.org
Fedora Developer Portal team is reachable on freenode #developer-portal
May I did not understand some questions.
Do not hesitate to contact us on IRC.
Greetings
Petr
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/433>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#416: FAD Python 3 Porting 2015
-------------------------------------+-------------------------------------
Reporter: | Owner:
williamjmorenor | 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: |
1 |
-------------------------------------+-------------------------------------
Badge description: You attended the Fedora Python 3 Porting FAD 2015!
https://fedoraproject.org/wiki/FAD_Python_3_Porting_2015
I think there is not much to say about this badge, the python3 porting is
a big effort and the porting FAD was a great event in this line.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/416>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#414: Badges for Community Blog authors
-------------------------------------+-------------------------------------
Reporter: | Owner:
bee2502 | Status: new
Type: | Keywords: Community
New badge idea | Blog
Priority: | Has a description: 0
minor | Artwork status: None
Has a name: | External requirements:
0 | Triaged (triagers only): 0
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
Badge description (like "You added a co-maintainer to a package. BFF!"):
Badge Series for Community Blog authors
https://communityblog.fedoraproject.org/
Help the badges team understand what this idea is all about. If this
badge is awarded for certain kinds of activities:
1) What are those activities?
Like Fedora Magazine Badge Series, but for Community Blog.
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
Fedora contributors
3) Why are they doing them (is this a means to a different end?)
Unlike Fedora Magazine which is for general news about Fedora OS,
Community Blog is for News and updates for about the Fedora Project
community that develops supports and promotes Fedora.
-Posts would lead to information spread about what is happening in every
nook and corner of Fedora Developer Community.
-Badge would signify high community participation and would encourage
community engagement amongst other contributors.
- Promote Community Blog amongst Fedora contributors
4) When do they do them (every day? once a year?)
anytime. more the better.
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
Authoring posts to be published on Community Blog
Lastly, do you have any ideas for artwork concepts?
Community Bonding. Sort of like friends meeting and talking. Something to
show information spread too.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/414>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#452: Lets have a party - Fedora 24
-------------------------------------+-------------------------------------
Reporter: | Owner:
gnokii | 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: |
0 |
-------------------------------------+-------------------------------------
This badges continues existing badge #189 and #318 and #410 for Release
Party Participants. This time for Fedora 24!
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/452>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#446: Badge for Fedora 24 internationalization test day participants
-------------------------------------+-------------------------------------
Reporter: | Owner:
pravins | 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 |
-------------------------------------+-------------------------------------
Badge description (like "You added a co-maintainer to a package. BFF!"):
"You helped to test Fedora 24 i18n features"
Help the badges team understand what this idea is all about. If this
badge is awarded for certain kinds of activities:
1) What are those activities?
Testing Fedora 24 before Beta.
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
It can be anyone but mostly i18n developers + translators + Fedora QA
3) Why are they doing them (is this a means to a different end?)
Making Fedora 24 stable release.
4) When do they do them (every day? once a year?)
Once each Fedora release. This activity mostly happen whole week.
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
We communicated on #fedora-test-day and #fedora-g11n
Lastly, do you have any ideas for artwork concepts?
Earlier badge for similar activity for other Fedora release.
https://fedorahosted.org/fedora-badges/ticket/360
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/446>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#438: 3D Printing SIG Member
-------------------------------------+-------------------------------------
Reporter: | Owner:
churchyard | 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
1 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
Partial |
Manually awarded: |
1 |
-------------------------------------+-------------------------------------
Badge description: You're a member of the 3D Printing Special Interest
Group
For the members of https://fedoraproject.org/wiki/SIGs/3DPrinting (would
be manually awarded by me)
Lastly, do you have any ideas for artwork concepts?
Yes, attached.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/438>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#363: Holiday Maker
-------------------------------------+-------------------------------------
Reporter: | Owner:
isimluk | Status: new
Type: | Keywords: relax
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 |
-------------------------------------+-------------------------------------
Alternative name: Camper Badge.
Criteria: Did not receive any badge in 2 months.
Rationale: Firstly, it is beneficial for one's mental health to relax for
a while. Secondly, it is also good for Fedora to remind its contributors,
that it has already been a while since their last contribution.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/363>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#451: Kernel Tester VI and more
-------------------------------------+-------------------------------------
Reporter: | Owner:
cialu | Status: new
Type: | Keywords: kernel
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: Completed run of the kernel
regression test suite
Badge description: You have regression tested your kernel
Anything else we need to know:
Why did Kernel Tester Badge stop at level V aka 50 runs of the kernel
regression test suite?
Maybe we could do more badges of this series, about 100, 200, 500 runs?
Original discussion:
https://fedorahosted.org/fedora-badges/ticket/155
Actual badges:
https://badges.fedoraproject.org/explore
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/451>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#378: Bit from the core
-------------------------------------+-------------------------------------
Reporter: | Owner:
mattdm | 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:
Any change which either
a) reduces the number of packages installed in Fedora Cloud base
(generally, by reducing dependencies), or
b) otherwise shrinks the total compressed image size by at least 1MB
(subpackaging, better compression, just removing stuff, etc.)
Badge description (like "You added a co-maintainer to a package. BFF!"):
"You reduced the size of the Fedora Cloud image"
Anything else we need to know:
I think Kushal can track this semi-automatically (possibly using tunir).
At least, can track the size and package set, and award manually when
deserved.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/378>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#348: Badge for release engineering members
-------------------------------------+-------------------------------------
Reporter: | Owner:
till | 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: Membership of sysadmin-releng
Badge description (like "You added a co-maintainer to a package. BFF!"):
You keep Fedora rolling as part of the release engineering team.
Anything else we need to know:
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/348>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app