Closed Bug 823278 Opened 12 years ago Closed 11 years ago

Create designs for Webdev Badge pilot

Categories

(Marketing :: Design, task)

Product:
Marketing
Component:
Design
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: davidwboswell, Assigned: jslater)

References

(
URL
)

Details

(Whiteboard: tbd: community designer) 

The Webdev team wants to roll out a badge pilot to recognize contributors.  They've identified the following badges they'd like to issue:

* Fork a site repo
* Submit a pull request
* 1 pull request merged
* 10 pull requests merged
* 25 pull requests merged
* 50 pull requests merged
* 100 pull requests merged

I'd like to have this effort fit in with badges that contributors can earn from other parts of Mozilla.  It seems like there is already a Mozilla badge template that may be in place.  mrz shared these designs with me about IT badges:

http://cl.ly/image/1e3t0h1F093t
http://cl.ly/image/403E170C3t0J

Would it be possible to have designs for these Webdev badges completed in early Q1?  If there is a template hopefully it would be easy to pull these together. 

Also if we could reuse Github icons for the relevant Github activities, we could use those instead of needing to create new images (not sure the licensing around Github images like the icon for pull requests).

https://github.com/styleguide/css/7.0
David, would you be up for pushing back the deadline a bit if it meant potentially finding some community designers to help with this?
Sure, I'm definitely open to that.
Whiteboard: tbd: community designer
In the 1/7 stewards meeting we discussed creating a template that community designers might work within. John Slater, how long do you think it might take to a) create the template, and b) solicit and review submissions? 

We are considering a March 1 go-live date for the pilot and look forward to your thoughts.
FYI, I just talked with John over email and he's pulling things together to announce this to volunteer designers.  Here are the open issues he needs to sort out first:

- a few bullets providing design direction on our current style [Sean]

- can we reuse github icons as noted in the bug? Who can find out?

- need details on what the final deliverables are…file types, sizes ,etc. Who can supply those?

If anyone has thoughts on the above, please feel free to comment.
Badge image specifications:
URL for image representing the badge. Should fit in a square (90 x 90) and in PNG format. Maximum size of 256kb.
And to clarify: the size it appears in the Mozilla backpack is 90 x 90 pixels; however, it can appear larger and smaller than this in other iterations. Consequently, the badge should be considered a type of logo, with particular attention paid to small details that might disappear at reduced sizes and colors that might shift at small sizes.
You'd need to define more clearly specifically what you meant by "github icons", but this GitHub issue: https://github.com/github/gollum/issues/394 suggests that their icons are generally not available for reuse. So, at least temporarily and possibly permanently, we need to use something else. If it's not a GitHub trademark (which the Octocat probably is, but things like a little book icon are not), it would be fine to recreate from scratch something which looked similar to the GitHub version.

Gerv
Thanks Gerv. I reached out to John Britton at GitHub who shared the following:

"We've had some requests for the use of Octicons in the past and from what I know, we haven't approved their use for anyone. That's not to say it's impossible but I think it's unlikely."

I'll stay on him but we should plan to move forward with alternate versions. 

David Boswell, John Slater and I have time on the calendar to discuss the design competition tomorrow. More to come. Thanks all.
We've discussed working with the following schedule:

1/22: Post announcing design competition goes live (including design requirements); David Boswell and I promote
1/22-2/11: Submissions accepted
2/4-2/28: API integration
2/11-2/15: Submissions reviewed; contact winner(s)
3/1: Badges go live; available for issuing
The schedule and badge names are now available on this pad: https://openbadges.etherpad.mozilla.org/web-dev-badges
Blog post is up at https://blog.mozilla.org/creative/2013/01/23/community-design-mozilla-contributor-badges. Let me know if you think it needs any further edits before we start publicizing.
Thanks John. This is great to see.

A few thoughts include:

+ I wonder if it's worth mentioning that their work will directly benefit other volunteers up front. i.e. "If so, read on because we’re looking for help with a very cool new project [that will help contributors like yourself be recognized for their great work]."

+ It's important to clarify that these will be Open Badges (that are part of a wider network of badges that are interoperable and shareable: https://wiki.mozilla.org/Badges), not just digital, image-based badges. They will include metadata that makes them information-rich and that will make it possible for people who view contributors' Mozilla badges to learn more about the criteria behind earning them. 

+ Do the badges have to be hexagonal? The Webmaker badges were designed that way, but badges can be any shape within the size constraints. I say this because a) I don't want other issuers to get the impression that badges must be one shape only; and b) I wonder if we might solicit a more diverse set of designs by making contributors feel less constrained. 

+ What time on February 11 do you intend to close the competition?

Thanks again, and look forward to promoting.
Looks good.  I just have one additional small edit to suggest.

We should mention that this activity is around action on Github.  Maybe by adding to the end of the second paragraph something like:

"earned by the following actions on Github."
Thanks Emily & David - I appreciate the feedback. More comments below: 

> + I wonder if it's worth mentioning that their work will directly benefit
> other volunteers up front. i.e. "If so, read on because we’re looking for
> help with a very cool new project [that will help contributors like yourself
> be recognized for their great work]."

I haven't added this yet b/c my suspicion is that most participants in this project aren't currently contributors, so that won't really resonate with them.
 
> + It's important to clarify that these will be Open Badges (that are part of
> a wider network of badges that are interoperable and shareable:
> https://wiki.mozilla.org/Badges), not just digital, image-based badges. They
> will include metadata that makes them information-rich and that will make it
> possible for people who view contributors' Mozilla badges to learn more
> about the criteria behind earning them.

I added this...let me know if it looks correct. 
 
> + Do the badges have to be hexagonal? The Webmaker badges were designed that
> way, but badges can be any shape within the size constraints. I say this
> because a) I don't want other issuers to get the impression that badges must
> be one shape only; and b) I wonder if we might solicit a more diverse set of
> designs by making contributors feel less constrained. 

I can see the pros & cons here, but I do like the idea of a consistent visual style across all Mozilla badges. I'm not really sure what is & isn't connected to Webmaker specifically, but my sense is that all Mozilla badges up til now have been horizontal. Am happy to discuss further though.
 
> + What time on February 11 do you intend to close the competition?
I guess EOD...I didn't mention a time b/c I don't think it needs to be that rigid (if someone submits a great design in the early morning hours of the 12th, for example, I wouldn't reject it.)

> We should mention that this activity is around action on Github.  Maybe by
> adding to the end of the second paragraph something like: 
> "earned by the following actions on Github."
Added this, thanks.

What are the next steps? If you're going to do a lot of Twitter promotion, could you start by RT'ing a tweet from the @mozcreative account? That might direct some interest our way for future projects like this. I haven't done that tweet yet, so just let me know what you're thinking about timing, etc.
Thanks for making those edits John.

For next steps, I will reach out to some people who would be interested in this, will share and ask people to promote at the Grow Mozilla meeting tomorrow, can post to the Mozillians and Webdev mailing lists and will ask people to participate at the All Hands meeting on Monday.

I don't really tweet, so I'm not much help with retweeting :)
Sounds great, thanks!

Re: tweeting, I wasn't thinking of you individually so much as us reaching out to folks with key Twitter accounts. For example, could @mozilla or @firefox RT something?
@John, we can ask Ben Simon to RT on @mozilla. Thanks!
That would be great. Do you have contacts with the Hacks blog as well? Might be relevant.

Here's the tweet for anyone who wants to RT: 
https://twitter.com/MozCreative/status/294227005925376002
Thanks John and David! (Apologies for the slow response as we're meeting with badge issuers in Irvine this week.) We will repost on the Open Badges blog and tweet.
Hey, I tweeted the following: 
Hey designers! It's your chance to design visuals for new Mozilla contributor #OpenBadges, due by 2/11: https://blog.mozilla.org/creative/2013/01/23/community-design-mozilla-contributor-badges/
i retweeted Carla's tweet. The url of her tweet so others can retweet is:
https://twitter.com/carlacasilli/status/294495388671541249

Watching this design competition with interest. Hopefully we can do something soon like this for SUMO badges.
assigning to Slater so he can follow up wrt the community designers and re-assign as needed.
Assignee: tshahian → jslater
Status: NEW → ASSIGNED
Closing as fixed.  The webdev badges are designed and live.

https://badges.mozilla.org/en-US/profiles/profile/webdev
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.