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.
Hi mythcat! Thank you for filing this ticket. This ticket is a little difficult to understand. I think it is because of the language barrier.
I want to understand this idea correctly. Do you "Fedora User of the Year" for the badge name? A lot of the qualifications you mentioned seem like milestones for contributors. Most of these things are done over time. They are important for making progress as a contributor. We might already have a badge request similar to this one. #409 seems similar. I think we should put ideas for this into that ticket. #409 is about giving credit for reaching milestones as a contributor. I think this is an important idea. Let's discuss and implement #409. :)
Thank you again for the ticket!
Metadata Update from @mythcat: - Issue assigned to mythcat
Login to comment on this ticket.