Closed
Bug 1035839
Opened 10 years ago
Closed 10 years ago
Hive Community Member Badge Soft Launch Final Steps
Categories
(Webmaker Graveyard :: Badges, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: robert, Unassigned)
References
Details
(Whiteboard: [badges][july11])
Lainie and I would like to finally get to DONE on the soft launch plan noted in this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1028417. I have four critical questions/concerns/requests that need to be resolved first! Can you or someone else please help us with the items below? Please let me know if not so I can adjust our timeline for this launch. 1. Can you please confirm that: * IF an email address for a badge earner through bulk issue is NOT already associated with a Webmaker profile... * THEN a Webmaker account and profile is NOT automatically created for them... * BUT a badge is STILL issued to that email address AND they will see if on their profile IF/WHEN then create an account. 2. Can you update the "congratulations" email to badge earners to the following copy: https://docs.google.com/document/d/1glUi-d0yTaEM1f_PZzm8bQ9guamBqCAKWgzagSBA_9U/edit?usp=sharing 3. Can you *please* review the email copy in this etherpad from lines 100 to 150 and make sure the instructions are accurate and make sense? https://hive.etherpad.mozilla.org/badgecoms 4. Can you *please* review the UI/UX Form I put together: https://bugzilla.mozilla.org/show_bug.cgi?id=1016749 Once Lainie sends out the email copy in that etherpad, we'd like to immediately issue badges to all Hive staff listed in this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1027269 I'll send a confirmation about Item #4 when we are ready. Hope that isn't too much and makes sense.
Reporter | ||
Comment 1•10 years ago
|
||
* whoops, I meant to say I'll send a confirmation about issuing badges to Hive Staff when we are ready!!!
Updated•10 years ago
|
Updated•10 years ago
|
Updated•10 years ago
|
Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•