Closed
Bug 766680
Opened 12 years ago
Closed 12 years ago
Allow registrants to add curated groups and skills
Categories
(Participation Infrastructure :: Phonebook, defect)
Participation Infrastructure
Phonebook
Tracking
(Not tracked)
VERIFIED
FIXED
2012-09-12
People
(Reporter: aakashd, Assigned: aakashd)
References
Details
Attachments
(2 files)
We need to be funneling users more towards groups those with Stewards. Also, in general, we should be asking for more information to help them get vouched for and found faster. No better place to do that then the registration form! Includes: * Users can add curated groups (groups w/ Stewards) onto their profiles * Users can add skills to their profiles
Hey all: I'm pretty confused here. The discussion we've been having is to get current contributors [those in the Phonebook and vouched already, and those that aren't yet] to classify themselves according to skillset + area of contribution. Not funneling in new contributors - we discussed holding off on that and directing new people to the Get Involved page. Are we on the same page here? It might be that the copy on the mockup is just misleading.
Assignee | ||
Comment 2•12 years ago
|
||
This is just a part of a set of bugs, Mary. I'm in the process of cc'ing all ya'll to the others. Also, getting new contributors to the right groups before they've even become vouched will help with getting a correct number of contributors per functional area.
Comment 3•12 years ago
|
||
(In reply to Mary from comment #1) > Not funneling in new contributors - we discussed holding off on that and > directing new people to the Get Involved page. To give potential contributors who come to mozillians.org a path forward, I agree that directing people to Get Involved makes more sense than creating a second system for connecting people to Stewards. > It might be that the copy on the mockup is just misleading. In terms of copy on the mockup, is the list of areas a placeholder or not? I'd prefer to stay in sync with the areas on the Get Involved page instead of creating a second different set of functional areas. Staying in sync will avoid duplicating efforts in providing contribution pathways for people.
There are two things at play here in this bug: * Where new contributors are funneled. * Getting current contributors classified into recognized functional areas so we can do targeted communications and get accurate accounts. I'd like to see a proposed flow for tackling these issues in a coherent wireframe or document somewhere vs. piece it together over a series of bugs. It would save time and ensure that we're on the same page. Please do this, Aakash.
Assignee | ||
Comment 5•12 years ago
|
||
Hey Mary and David, I'm not sure what ya'll are talking about, but this bug is strictly about streamlining registration flow so that contributors get found easily within the app. We're trying to get them into the right groups (i.e. functional areas that have Stewards), so part of the strategy is to get them into the right groups right from the registration flow (which they're already on at that point). How they get to Mozillians.org's registration flow (if at all) is up to David since he's tackling conversion and funneling. I can follow up with him about that later.
Comment 6•12 years ago
|
||
(In reply to Aakash Desai [:aakashd] from comment #5) > How they get to Mozillians.org's registration flow (if at all) is up to > David since he's tackling conversion and funneling. I can follow up with him > about that later. Sure, happy to talk more about that. My current thinking is that we could identify a specific threshold (such as when people go from casual to active contributor) and then automatically send out invites to register. We can document that point at https://wiki.mozilla.org/Contribute/Conversion_points Would be great to talk through that more with you.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → mozaakash
Assignee | ||
Comment 7•12 years ago
|
||
Fixed by bug 785944.
Assignee | ||
Updated•12 years ago
|
Target Milestone: --- → 2012-09-05
Assignee | ||
Updated•12 years ago
|
Target Milestone: 2012-09-05 → 2012-09-12
Comment 8•12 years ago
|
||
Updated•12 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•