#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: | Owner: jflory7 | Status: new Type: | Keywords: New badge idea | Has a description: 1 Priority: | Artwork status: Concept major | External requirements: Has a name: | Triaged (triagers only): 1 1 | Concept approved (reviewers only): | 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 | -------------------------------------+------------------------------------- = Badge Description =
* '''Name''': Bitcamp 2016 Attendee * '''Description''': * I: Congratulations, you were added as a contributor to your first repository on Fedora Pagure (pagure.io)! * II: You've been added as a contributor to 10 repositories on Fedora Pagure (pagure.io). * III: You've been added as a contributor to 25 repositories on Fedora Pagure (pagure.io). * IV: You've been added as a contributor to 100 repositories on Fedora Pagure (pagure.io). With great power comes great responsibility...
= Understanding badge =
1) What are those activities?
* '''Users are granted badge for attending the Bitcamp 2016 hackathon (badge is similar in scope to the [https://badges.fedoraproject.org/badge/brickhack-2016-attendee BrickHack 2016 badge])''
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)
* '''People attending Bitcamp 2016'''
3) Why are they doing them (is this a means to a different end?)
* '''They are interested in learning more about Fedora or getting involved!'''
4) When do they do them (every day? once a year?)
* '''April 8 - 10, 2016'''
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)
* '''Scanning QR code.'''
= Artwork concepts =
* Typical badge template replaced with the [http://bitca.mp Bitcamp logo]
Depending on how things go, I might design this badge if a design team member is not
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | Status: idea | new Priority: major | Resolution: Keywords: | Has a name: Has a description: 1 | 1 Artwork status: Concept | Concept approved (reviewers only): External requirements: | 1 Triaged (triagers only): 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 -------------------------------------+-------------------------------------
Old description:
= Badge Description =
- '''Name''': Bitcamp 2016 Attendee
- '''Description''':
- I: Congratulations, you were added as a contributor to your first
repository on Fedora Pagure (pagure.io)!
- II: You've been added as a contributor to 10 repositories on Fedora
Pagure (pagure.io).
- III: You've been added as a contributor to 25 repositories on Fedora
Pagure (pagure.io).
- IV: You've been added as a contributor to 100 repositories on Fedora
Pagure (pagure.io). With great power comes great responsibility...
= Understanding badge =
- What are those activities?
- '''Users are granted badge for attending the Bitcamp 2016 hackathon
(badge is similar in scope to the [https://badges.fedoraproject.org/badge/brickhack-2016-attendee BrickHack 2016 badge])''
- Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
- '''People attending Bitcamp 2016'''
- Why are they doing them (is this a means to a different end?)
- '''They are interested in learning more about Fedora or getting
involved!'''
- When do they do them (every day? once a year?)
- '''April 8 - 10, 2016'''
- How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
- '''Scanning QR code.'''
= Artwork concepts =
- Typical badge template replaced with the [http://bitca.mp Bitcamp logo]
Depending on how things go, I might design this badge if a design team member is not
New description:
= Badge Description =
* '''Name''': Bitcamp 2016 Attendee * '''Description''': ''You visited the Fedora table at Bitcamp 2016!''
= Understanding badge =
1) What are those activities?
* '''Users are granted badge for attending the Bitcamp 2016 hackathon (badge is similar in scope to the [https://badges.fedoraproject.org/badge/brickhack-2016-attendee BrickHack 2016 badge])''
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)
* '''People attending Bitcamp 2016'''
3) Why are they doing them (is this a means to a different end?)
* '''They are interested in learning more about Fedora or getting involved!'''
4) When do they do them (every day? once a year?)
* '''April 8 - 10, 2016'''
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)
* '''Scanning QR code.'''
= Artwork concepts =
* Typical badge template replaced with the [http://bitca.mp Bitcamp logo]
Depending on how things go, I might design this badge if a design team member is not
--
Comment (by jflory7):
Fixing the description…
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | Status: idea | new Priority: major | Resolution: Keywords: | Has a name: Has a description: 1 | 1 Artwork status: Concept | Concept approved (reviewers only): External requirements: | 1 Triaged (triagers only): 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 -------------------------------------+-------------------------------------
Comment (by pnemade):
The number of such requests are increasing which is really good but how can other people know that there really was Fedora table present at that conference?
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | Status: idea | new Priority: major | Resolution: Keywords: | Has a name: Has a description: 1 | 1 Artwork status: Concept | Concept approved (reviewers only): External requirements: | 1 Triaged (triagers only): 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 -------------------------------------+-------------------------------------
Comment (by jflory7):
Replying to [comment:2 pnemade]:
The number of such requests are increasing which is really good but how
can other people know that there really was Fedora table present at that conference?
The Fedora Ambassadors of North America approved this event as a sponsor in our [https://meetbot.fedoraproject.org/sresults?group_id=famna&type=team weekly meetings]. You can find the [https://fedorahosted.org/famna/ticket/139 ticket] in our Trac as well as the [https://fedoraproject.org/wiki/Bitcamp_Spring_2016 wiki page] documenting the event.
For future reference, any event that Fedora Ambassadors are attending ''should'' have this information present somewhere to verify that the event is happening and that Fedora has a role in the event. Categorizing wiki pages with the [https://fedoraproject.org/wiki/Category:Events Events] category helps with this.
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | jflory7 idea | Status: Priority: major | accepted Keywords: | Resolution: Has a description: 1 | Has a name: Artwork status: Proposed | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 -------------------------------------+------------------------------------- Changes (by jflory7):
* cc: mleonova, duffy, riecatnor, elioqoshi (added) * owner: => jflory7 * status: new => accepted * has_artwork: Concept => Proposed
Comment:
= Proposed artwork =
Here is my first proposed badge artwork of the Bitcamp 2016 Attendee badge. Marking the artwork status as proposed and CCing some members of the Design Team for feedback! The event is this weekend, so any quick review / help is appreciated on this one!
[[Image(https://fedorahosted.org/fedora-badges/raw-attachment/ticket/444 /events-brickhack-2016.png)]]
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | jflory7 idea | Status: Priority: major | accepted Keywords: | Resolution: Has a description: 1 | Has a name: Artwork status: Proposed | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 -------------------------------------+-------------------------------------
Comment (by jflory7):
As an afterthought, I would like to add some kind of distinguishment for the year (i.e. "2016"), but I'm not quite sure how to work that into this design…
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | jflory7 idea | Status: Priority: major | accepted Keywords: | Resolution: Has a description: 1 | Has a name: Artwork status: Proposed | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 -------------------------------------+-------------------------------------
Comment (by mleonova):
Hey! One thing right away - word bitcamp is hard to read, can we make it white? And try adding 2016 to different parts of badge, see if anything looks good. Crazy idea - maybe write bitcamp on one log and 2016 on the other.. or vice versa. or just 2016 on the log. something of sorts.
Hope this helps ;)
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | jflory7 idea | Status: Priority: major | accepted Keywords: | Resolution: Has a description: 1 | Has a name: Artwork status: Proposed | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 -------------------------------------+-------------------------------------
Comment (by corey84):
Justin,
Maybe Fedora on the long log and in the upper right section of the underside log 2016 ? or Just ''' '16 '''
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | jflory7 idea | Status: Priority: major | accepted Keywords: | Resolution: Has a description: 1 | Has a name: Artwork status: Proposed | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 -------------------------------------+-------------------------------------
Comment (by jflory7):
Replying to [comment:6 mleonova]:
Hey! One thing right away - word bitcamp is hard to read, can we make it
white?
And try adding 2016 to different parts of badge, see if anything looks
good. Crazy idea - maybe write bitcamp on one log and 2016 on the other.. or vice versa. or just 2016 on the log. something of sorts.
Replying to [comment:7 corey84]:
Maybe Fedora on the long log and in the upper right section of the
underside log 2016 ?
or Just ''' '16 '''
Okay, here's the latest revision of the badge that I have! How does this look for a revision?
[[Image(https://fedorahosted.org/fedora-badges/raw-attachment/ticket/444 /events-bitcamp-2016.png)]]
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | jflory7 idea | Status: Priority: major | accepted Keywords: | Resolution: Has a description: 1 | Has a name: Artwork status: Proposed | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 -------------------------------------+-------------------------------------
Comment (by mleonova):
Looks great! Just move the 6 a bit closer to 1 and the whole thing a tinsy bit to the left and we're good =)
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | jflory7 idea | Status: Priority: major | accepted Keywords: | Resolution: 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: | Not yet possible | Manually awarded: | 1 -------------------------------------+------------------------------------- Changes (by jflory7):
* cc: ralph, nb (added) * has_artwork: Proposed => Approved (design team members only)
Comment:
Okay, shifted it over a little bit! Going to CC some sysadmin members to push this badge so we can get it ready in time for Bitcamp.
[[Image(https://fedorahosted.org/fedora-badges/raw-attachment/ticket/444 /events-bitcamp-2016.png)]]
#444: Bitcamp 2016 -------------------------------------+------------------------------------- Reporter: jflory7 | Owner: Type: New badge | jflory7 idea | Status: Priority: major | closed Keywords: | Resolution: Has a description: 1 | pushed Artwork status: Approved | Has a name: (design team members only) | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Not yet possible | Manually awarded: | 1 -------------------------------------+------------------------------------- Changes (by nb):
* status: accepted => closed * resolution: => pushed
Comment:
Pushed.
badges@lists.fedoraproject.org
-
fedora-badges