#473: Badger Padawan
-------------------------------------+-------------------------------------
Reporter: | Owner:
riecatnor | 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): |
1 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
Badge description (like "You added a co-maintainer to a package. BFF!"):
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?
Attending a Fedora Badges Workshop
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
Anyone who attends a Fedora Badges Workshop
3) Why are they doing them (is this a means to a different end?)
To learn about creating Fedora Badges
4) When do they do them (every day? once a year?)
Whenever a Fedora Badges workshop is held (usually by riecatnor or
mleonova, who should have permissions on this badge)
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
In person at events such as Flock, Open Houses, or Design FADs
Lastly, do you have any ideas for artwork concepts?
Badger in a jedi costume holding a paintbrush or pencil instead of a
lightsaber. Also include padawan braid
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/473>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#478: Voted Fedora user on this year / years .
-------------------------------------+-------------------------------------
Reporter: | Owner: mythcat
mythcat | Status: new
Type: | Keywords: Credits
New badge idea | by Fedora teams
Priority: | Has a description: 0
minor | Artwork status: Proposed
Has a name: | External requirements:
0 | Triaged (triagers only): 0
Concept approved (reviewers only): |
0 |
Badge definition status: |
Partial |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
Badge description (like "Fedora users credits"):
- for activity performed by a Fedora user over time - no leader team just
Fedora users;
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?
- will fulfill part of all badges but into sum of activity into Fedora
team/s.
- objective is to increase activity levels - both by implication and self-
motivated user into team activity present in Fedora teams;
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
Fedora users activity over Fedora team without lead
3) Why are they doing them (is this a means to a different end?)
credits by activity over team
4) When do they do them (every day? once a year?)
will highlight the involvement with or without planning users;
This badge is not achieved by team leaders;
-user will need to have two years into Fedora team (user must have
experience in at least two releases of Fedora distro);
-translation and planning activity (both components g11 and L10n);
-activity on fedora lists.fedoraproject.org;
-activity and time spent in space Fedora (without IRC);
-activity in IRC meeting (meeting voted team leader);
-working between teams involved in solving solution (voted by both teams
leaders);
This badge is obtained only for a period of time specified in it;
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
- once of year and also will be sum over years with levels
- team leaders will consolidate user activity through a badged anniversary
as involvement in Fedora project with a number of credits result by
problem / solution / time into a final meeting before Fedora released.
Lastly, do you have any ideas for artwork concepts?
- we don't use "award" text/equivalent;
- we don't include the Fedora distro;
- this is a sum of work over Fedora distro into that year;
- can be also reward by user when the user is the user has died -post-
mortem (for activity);
- this badge can be issued as a material object created and produced by
Fedora.
- this badge can be handed over to family in case of death by Fedora team;
- we can used "Credits by Fedora teams" text;
- based proposed by the team leader with the most pronounced activity into
the team;
- based proposed by the team leader with the most pronounced activity;
- it can be claimed or contested by the user by sending a team leaders
meeting for its voting;
- with levels and credits / year;
the voted users will need to get this badge info:
- text: "User voted by Fedora teams leaders"
- credits:"number" ( number of credits from 0 to 9 vote by Fedora teams -
leader);
- level (depend of voting can we have 4 (four) badges / distro - year):
"platinum" - redhat user/ fedora team over years with implication into
Fedora team
"gold" - years on fedora team with argent badge
"argent" - the size of work into period of time (years / credits by fedora
teams leaders)
"bronze" - the size of work into period of time versus similar fedora
badge (argent badge, gold, platinum) by follow the working path on Fedora
team.
design:
- icon of Fedora;
- fedora icon on badge with ledge and text with colors(
platinum/gold/argent/bronze);
- text used: level/credit/year;
- design will be voting by most of the Fedora team leaders into the
votting meeting.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/478>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#481: You created a QA test case for a package!
-------------------------------------+-------------------------------------
Reporter: | Owner:
mildew | 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: You created a QA test case for a package!
QA test cases are created by packagers as well as package testers. Anyone
with permissions to create and edit pages on the fedoraproject.org wiki
can create a QA test case.
As their name suggest, they server for quality assurance purposes -- use
case testing, regression testing, etc. As an example, here's a Firefox
package test case:
https://fedoraproject.org/wiki/QA:Testcase_firefox_media
The test case are automatically linked to package updates in Bodhi
([https://bodhi.fedoraproject.org/updates/FEDORA-2016-0af3ff40a7 example])
where package testers can indicate whether the package passes a test case
or not.
Because the test case page names have to follow specific naming
conventions, it should be easy to create criteria for awarding the badge.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/481>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#483: Badge for 389-Directory Server
-------------------------------------+-------------------------------------
Reporter: | Owner: kamlesh
komcy | Status: new
Type: | Keywords:
New badge idea | 389-Directory Server
Priority: | Has a description: 0
minor | Artwork status: Concept
Has a name: | External requirements:
1 | Triaged (triagers only): 0
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
1 |
-------------------------------------+-------------------------------------
Badge description (like "You added a co-maintainer to a package. BFF!"):
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?
Patch submit in 389
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
Anyone
3) Why are they doing them (is this a means to a different end?)
to grow the Community
4) When do they do them (every day? once a year?)
every day
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
Lastly, do you have any ideas for artwork concepts?
Nop
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/483>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#484: Badge for FreeIPA project
-------------------------------------+-------------------------------------
Reporter: | Owner:
akasurde | 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!"):
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?
Submit a patch in FreeIPA project
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
Anyone
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?)
Everytime someone post a patch in FreeIPA repo, they get badge
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
by using a web interface
Lastly, do you have any ideas for artwork concepts?
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/484>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#492: Keep the badges rollin
-------------------------------------+-------------------------------------
Reporter: | Owner:
gnokii | 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 |
-------------------------------------+-------------------------------------
Manual badge awarding is a time consuming job, especially some ¨features"
that tahrir has like redirecting you to the badges feed after an award or
give you error pages, if the person doesnt exist in badges or has the
badge already. I know what I am speaking of, I award all nuancier badges,
since several releases by hand. And some other badges I also award by
hand, like the release party badges and some others.
Idea is to reward this work on awarding with some badges. Think a good
starting point would be
100 badges awarded
250 badges awarded
500 badges awarded
1000 badges awarded
Artwork idea could be a badger, who rolls badges uphill or to an pyramid
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/492>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#267: SVGs in git are a bit of mess
-------------------------------------+-------------------------------------
Reporter: | Owner:
churchyard | Status:
Type: Bug | closed
report | Resolution:
Priority: minor | rejected
Keywords: svg | Has a name:
Has a description: 0 | 0
Artwork status: None | Concept approved (reviewers only):
External requirements: | 0
Triaged (triagers only): 1 | Badge definition status:
| None
| Manually awarded:
| 0
-------------------------------------+-------------------------------------
Changes (by jflory7):
* status: new => closed
* triaged: 0 => 1
* resolution: => rejected
Comment:
Ticket is two years old and the same thing that Ralph mentioned above is
still relevant to today. For any missing SVGs, we should probably tackle
those on a 1x1 basis in the original ticket for the badge since most of
them are present.
I'm going to go ahead and close this ticket.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/267#comment:2>
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
#272: AppStream Data Contributor Badge
-------------------------------------+-------------------------------------
Reporter: duffy | Owner:
Type: New badge | Status:
idea | closed
Priority: minor | Resolution:
Keywords: | pushed
Has a description: 0 | Has a name:
Artwork status: Approved | 0
(design team members only) | Concept approved (reviewers only):
External requirements: | 0
Triaged (triagers only): 0 | Badge definition status:
| None
| Manually awarded:
| 0
-------------------------------------+-------------------------------------
Comment (by zdenek):
I guess, this is still ongoing activity - is there any way to get this
badge yet? Or was is linked to one time event only?
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/272#comment:10>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app