#437: Python SIG memeber -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | 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're a member of the Python Special Interest Group
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?
Being member of https://fedoraproject.org/wiki/SIGs/Python https://admin.fedoraproject.org/accounts/group/view/python-sig
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)
Mostly packagers.
3) Why are they doing them (is this a means to a different end?)
Because tehy want to be part of the SIG.
4) When do they do them (every day? once a year?)
Once they join.
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)
In FAS.
Lastly, do you have any ideas for artwork concepts?
Yes, will attach.
#437: Python SIG memeber -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | Status: Type: New badge | new idea | Resolution: Priority: minor | Has a name: Keywords: | 1 Has a description: 0 | Concept approved (reviewers only): Artwork status: Proposed | 0 External requirements: | Badge definition status: Triaged (triagers only): 0 | Partial | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by churchyard):
* has_complete_yaml: None => Partial * has_name: 0 => 1 * has_artwork: None => Proposed
Comment:
[[Image(python-sig.png)]]
#437: Python SIG member -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | Status: Type: New badge | new idea | Resolution: Priority: minor | Has a name: Keywords: | 1 Has a description: 0 | Concept approved (reviewers only): Artwork status: Proposed | 0 External requirements: | Badge definition status: Triaged (triagers only): 0 | Partial | Manually awarded: | 0 -------------------------------------+-------------------------------------
#437: Python SIG member -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | Status: Type: New badge | new idea | Resolution: Priority: minor | Has a name: Keywords: | 1 Has a description: 0 | Concept approved (reviewers only): Artwork status: Approved | 0 (design team members only) | Badge definition status: External requirements: | Partial Triaged (triagers only): 0 | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by riecatnor):
* has_artwork: Proposed => Approved (design team members only)
Comment:
Looks good! Setting to approved
#437: Python SIG member -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | Status: Type: New badge | new idea | Resolution: Priority: minor | Has a name: Keywords: | 1 Has a description: 0 | Concept approved (reviewers only): Artwork status: Approved | 0 (design team members only) | Badge definition status: External requirements: | Full, needs review Triaged (triagers only): 0 | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by churchyard):
* has_complete_yaml: Partial => Full, needs review
#437: Python SIG member -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | churchyard Type: New badge | Status: idea | assigned Priority: major | Resolution: Keywords: | Has a name: Has a description: 1 | 1 Artwork status: Approved | Concept approved (reviewers only): (design team members only) | 1 External requirements: | Badge definition status: Triaged (triagers only): 1 | Full, needs review | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by jflory7):
* status: new => assigned * cc: nb, ralph (added) * triaged: 0 => 1 * concept_review_passed: 0 => 1 * priority: minor => major * owner: => churchyard * has_description: 0 => 1
Old description:
Badge description: You're a member of the Python Special Interest Group
Help the badges team understand what this idea is all about. If this badge is awarded for certain kinds of activities:
- What are those activities?
Being member of https://fedoraproject.org/wiki/SIGs/Python https://admin.fedoraproject.org/accounts/group/view/python-sig
- Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
Mostly packagers.
- Why are they doing them (is this a means to a different end?)
Because tehy want to be part of the SIG.
- When do they do them (every day? once a year?)
Once they join.
- How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
In FAS.
Lastly, do you have any ideas for artwork concepts?
Yes, will attach.
New description:
Badge description: You're a member of the Python Special Interest Group.
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?
Being member of https://fedoraproject.org/wiki/SIGs/Python https://admin.fedoraproject.org/accounts/group/view/python-sig
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)
Mostly packagers.
3) Why are they doing them (is this a means to a different end?)
Because tehy want to be part of the SIG.
4) When do they do them (every day? once a year?)
Once they join.
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)
In FAS.
Lastly, do you have any ideas for artwork concepts?
Yes, will attach.
--
Comment:
Badge looks like it's ready to push! I'm CCing some Badges sysadmins to push this out. :)
#437: Python SIG member -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | churchyard Type: New badge | Status: idea | assigned Priority: major | Resolution: Keywords: | Has a name: Has a description: 1 | 1 Artwork status: Approved | Concept approved (reviewers only): (design team members only) | 1 External requirements: | Badge definition status: Triaged (triagers only): 1 | Full, needs review | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by cydrobolt):
I pushed this out, but it doesn't look like I can view it on the badges website yet
#437: Python SIG member -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | churchyard Type: New badge | Status: idea | closed Priority: major | Resolution: Keywords: | pushed Has a description: 1 | Has a name: Artwork status: Approved | 1 (design team members only) | Concept approved (reviewers only): External requirements: | 1 Triaged (triagers only): 1 | Badge definition status: | Full, needs review | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by cydrobolt):
* status: assigned => closed * resolution: => pushed
#437: Python SIG member -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | churchyard Type: New badge | Status: idea | closed Priority: major | Resolution: Keywords: | pushed Has a description: 1 | Has a name: Artwork status: Approved | 1 (design team members only) | Concept approved (reviewers only): External requirements: | 1 Triaged (triagers only): 1 | Badge definition status: | Full, needs review | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by churchyard):
Thanks
badges@lists.fedoraproject.org