What the badge should be granted for: - for new members and contributors of Fedora Robotics Spin
Badge description (like "You added a co-maintainer to a package. BFF!"): - Now a proud member of the Fedora Robotics
Anything else we need to know:
attachment <img alt="badge-robotics-member.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/df69fad991a7511815462f4d171fa8efb1eaa6665d8cd64df3fcab8c9c21346c-badge-robotics-member.png" />
attachment <img alt="badge-robotics-member.png" src="//issue/raw/files/df69fad991a7511815462f4d171fa8efb1eaa6665d8cd64df3fcab8c9c21346c-badge-robotics-member.png" />
Wow. That badge art is really cool.
zdenek, can you recommend a good method for determining who should and shouldn't get the badge? I check in fas and there is no "robotics" group there that I could find.
Hello Ralph. Thanks a lot for your feedback. I created this request for Robotics spin (http://spins.fedoraproject.org/robotics/). I didn't check the award possibilities in detail before. The idea was to give it to each new member of this spin like in case of 'Involvement' badge (https://badges.fedoraproject.org/badge/involvement) But now, when I checked all related web pages, I'm not sure there is easy way to gain such a badge :-\ Then probably only manual award for spin members would be possible (please see members on http://fedoraproject.org/wiki/SIGs/Robotics)
If there is no automated award solution for spins possible then the same problem affects the other requests I submitted for spins: #132, #133, #134, #135, #136, #137, #138, #139, #140 & #141
Well, doing manual awards for this many badges will get tedious. Right now, that has to go through a member of sysadmin-badges every time we want to manually award a new one, and that doesn't scale.
We intend to build a system into the web interface that will allow delegation of powers to manually award things. So the "head" of the robotics team (or a group of designated people) can hand out only that badge to anyone them deem fit.
In the meantime, we could substitute a FAS group for this. If you request a new FAS group for the robotics-sig, we can key the badge off of membership in that group just like we do currently with the ambassadors badge.
I'm willing to move forward with creating a FAS group for the robotics sig, but can't find how to apply to create a new group. Do you have to file a bug on the fas tracker?
I think you can just create the group in FAS yourself. There should be a "New Group" button just under "My Account". Do you see it?
I do not, "Group List" is just under "My Account" for me when i log into admin.fedoraproject.org/accounts. I guess I don't have the credentials to make a group
Ah, I see. You have to be a member of the sysadmin group to create new groups. The normal procedure is to file a ticket with the fedora infrastructure team, but I can just create the group here.
https://admin.fedoraproject.org/accounts/group/view/robotics-sig
rmattes, you are the owner which should allow you to change it and set it up however you need.
In order to move forward with the badge I need:
After that, the code for this is pretty simple. We have lots of existing stuff that keys off of FAS groups, so it should be a copy/paste job.
robotics source robotics.svg
Hello, I attached the source file as requested by Ralph.
Hi! I think that your robot is rad! I would do a few things to make your design more Fedora Badge-y :)
Just pinging to see if there's any movement on this one.
attachment robotics_member.svg
attachment <img alt="robotics_member.png" src="//issue/raw/files/b2d4a055ac1da0afb729b737b96534d3e7e07fcc915ce4af2853bb6d1a74e310-robotics_member.png" />
attachment <img alt="robotics_member.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/b2d4a055ac1da0afb729b737b96534d3e7e07fcc915ce4af2853bb6d1a74e310-robotics_member.png" />
I took the original artwork by zdenek and worked it to fit the badge style guide. Commentary is welcome.
[[Image(robotics_member.png)]]
All pushed up and linked to the robotics-sig group: https://badges.fedoraproject.org/badge/domo-arigato
Log in to comment on this ticket.