1006687 - Demo, test and get feedback for Hive contributor badge on mofostaging

Status: RESOLVED WORKSFORME

(Webmaker Graveyard :: Hive, defect)

Description

[Robert Friedman [:omnignorant]]

Brett & Kate, here's the question: can we override or hack badgekit to allow for badge edits after publishing the badge or is it easier to just play around in the mofostaging sandbox and publish final badges on Webmaker.org?

Here's my thinking RE: mofostaging demo in May. Please comment if I am wrong.

Ideally we'd shoot straight from Webmaker.org for demo in May, but the need for a mofostaging-level demo before a soft launch on Webmaker.org is not just driven by the tech constraints. There are content and community level reasons why we wouldn't want the first badges issued to be the finalized versions. 

It would be good to have the freedom to make some mistakes first.

My understanding of how badgekit and/or the OBI work implies that once a badge is in the wild, it cannot be reigned in. All the criteria of that badge are writ in stone for evermore. To make changes you make new badges. Therefore, making a mistake with our first badge, in my opinion, will lead to greater confusion down the line than issuing "fake" demo badges first.

Making all our mistakes upfront on mofostaging means the badges we eventually issue on Webmaker will persist for a greater duration. I don't mind issuing v2 badges, but I'd like that to be a year or two down the line, not a month later.

Comment 1

[Matt Thompson (@OpenMatt :OpenMatt)]

* Robert: can we get this done by Friday? IF not, can you tag it for the [June13] train?

Comment 2

[Robert Friedman [:omnignorant]]

Matt, I definitely don't think we can complete testing and get feedback by May 30 at this point. However, I am going to send an email out to folks today or tomorrow (working through things now). I guess we re-tag for [June13] then.

Comment 3

[clawrence]

June 13th is fine

I started another bug to follow up on a 1-2-3 on the process and a feedback form to best gather the best data we should use to ask via Hives. I will also sprinkle some Amazon gift card incentives.

Matt, should be an easy way to get some good feedback, but need the right mechanism/form

Goal: 25 Hive pan Hive beta testers who complete process

Comment 4

[Robert Friedman [:omnignorant]]

Chris, can you CC me to that new bug? I'm working through some of this now and I can make progress there.

Comment 5

[Matt Thompson (@OpenMatt :OpenMatt)]

* status of this one?

Comment 6

[Robert Friedman [:omnignorant]]

In progress. That was the subject of the email I just sent out yesterday (and now awaiting action from the recipients) AND this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1016749

Comment 7

[Matt Thompson (@OpenMatt :OpenMatt)]

* Robert: status? can we we mark resolved?

* Can you write about the results?

Comment 8

[Brett Gaylor [:brett]]

Agreed - Robert since this bug is for the feedback, let's not block it on changes we want to make down the line.  if you can give a link to some written feedback we can mark this as resolved and will file bugs against it.  Bonus points if you can file dem bugs.

Comment 9

[Robert Friedman [:omnignorant]]

Here is a link to the feedback I've collected so far:
https://docs.google.com/a/mozilla.com/spreadsheets/d/1EU-M2ULQtVNeni5_i6mOzO-egpvmOC8BCtsaPS5nRNQ/edit?usp=sharing

I am going to transform these into new bugs for jun13 and jul15.

Warm feedback:
- the breadth of the criteria
– Clear, not verbose
– Easy to use

Cool feedback: 
- sharing contact info is too basic to earn a badge 
– It doesn't highlight the power of badges and why people may want a Hive badge.
– Great badge, tho

Suggested Changes:
- I think there should be separate input fields for badge evidence under each criteria section 
- there is a lot of scrolling required to review the criteria and input your evidence
- additional language is needed to clarify how many criteria someone needs to meet to get the badge.  I'd suggest 2/3 of the current criteria
– Making your personal contact and affiliation accessible to Hive members and respond to a request for assistance; 
– Under Peer Observation, give examples of "member programs" to help define. Is this observing other members' programs at their org? Or is it attending Hive meetups, calls, etc. I say let's make it all of the above.

Suggested Additions:
- Under Peer Observation add a criteria along the lines of - Run a station at a collaborative event like a pop-up or run a program in another organization's facility;
- Under Resource sharing make the criteria a little more robust as suggested below
- Tags to add: Hive, Hive Global, Hive Learning Network 
- Ask which Hive they are associated with. This may lead us to learn about emerging Hives and will help with tracking.
- Add something about why badges are important and how users can use them. Not everyone may be converted...yet.
- What's the confirmation email going to say? It could reiterate how they can use and display this badge.