Closed
Bug 721178
Opened 12 years ago
Closed 12 years ago
contacts per topic
Categories
(Participation Infrastructure :: Phonebook, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: groovecoder, Unassigned)
Details
Just saw this wiki page that DevEngage has to show contacts per topic. https://intranet.mozilla.org/Engagement/Developer_Engagement/ProjectsAndContacts Basically it provides the answer to "If you want to know about Paladin, talk to Dan Mosedale - the definitive source. If you want to know about Paladin from the DevEngage perspective, talk to Rob Hawkes." Seems like Mozillians.org could do something similar using topics or interests and groups?
Comment 1•12 years ago
|
||
Thanks for the bug filed, Luke! We're planning on making the "Stewards" have more privileges on the app. For example, folks who want to get involved in a certain group (or with a specific skill or set of skills) can contact one of the Stewards who have grouped themselves to other places without having to create an account. We could change the copy here to also include contacting a Steward or set of Stewards to get involved over a specific topic. Have you talked to Boswell or William Q about the projects and contacts work? It seems like they have a lot of overlap with what we're currently running in Contributor Engagement.
Updated•12 years ago
|
Component: mozillians.org → Phonebook
Product: Websites → Community Tools
QA Contact: mozillians-org → phonebook
Version: unspecified → other
Comment 2•12 years ago
|
||
Groups now have Stewards attached to them. Take a look at https://mozillians.org/en-US/group/25-support as an example.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 3•11 years ago
|
||
Bumping to verified due to the passage of time - we have a UX overhaul in process that will likely make it to production in ~1 month. If you have ideas or suggestions feel encouraged to discuss them with the group. The site is live at mozillians-dev.allizom.org while we iterate on the dev work.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•