Closed Bug 966331 Opened 12 years ago Closed 11 years ago

Create prospect lists for engagement outreach

Categories

(Webmaker Graveyard :: Engagement Ladder, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: matt, Assigned: erikad)

Details

(Whiteboard: [workweek][workweek-engagement][engagement])

* Create prospect lists for engagement outreach. Work out system(s) to flag up potential contributors for individual outreach. * e.g. list of all GitHub users who have forked a webmaker project, but haven't contributed yet.
Component: Community → General
Putting this on Erika, and you can decide who should own this.
Assignee: nobody → erikad
Status: NEW → ASSIGNED
Component: General → Engagement Ladder
So Matt, I'm not 100% clear on what you mean here, but we've identified both actions and "buckets of work" in the ever-evolving Contributor Pathways spreadsheet. Certain actions warrant personal individual outreach, and we're in the process of assigning owners for those tasks. I think it should be up to the individual owners to work out systems. https://docs.google.com/a/mozillafoundation.org/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=5 Marking this as resolved for now. Feel free to re-open if you still have questions.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
+Andrea and Adam Both: There are solid insights into comms planning and contributor definitions in here. Have you both gone through this / integrated it into your thinking?
Flags: needinfo?(andrea)
Flags: needinfo?(adam)
Yes, this document is the canonical source of the data points we need to get into the contributor dashboard for webmaker. We're working from a simplified copy of this to track progress: https://docs.google.com/a/mozillafoundation.org/spreadsheet/ccc?key=0AnUkMzboH_XAdFF5RWdYSjh2Nld1ZVNDVmx5LU8wUWc&usp=drive_web#gid=0 (will also be useful when we look at conversion rates from user>supporter>contributor)
Flags: needinfo?(adam)
Flags: needinfo?(andrea)
You need to log in before you can comment on or make changes to this bug.