Slides from my talk about the Mozilla Universe project at the Mozilla All-Hands on April 23, 2009. Gave an overview of the CRM project and how we are trying to build an open community directory for Mozilla community members.

1. Mozilla Universe
The Mozilla CRM Project
h6ps://wiki.mozilla.org/Mozilla_CRM
Jay Patel
Mozilla Corpora0on
2Q2009 All‐Hands

2. Background
• Project started by Seth Bindernagel and Rishi
Mallik in 2007
• Revived in late 2008 with ChicagoTech signed
on to work on it, but didn’t get far
• Currently working with Trellon (trellon.com)
and making good progress

3. What is the Mozilla CRM?
• Public community directory
of Mozilla contributors and
fans (poten0al contributors)
• CollaboraEon tool for groups
and individuals looking to
work together

4. What it isn’t…
• A tradi0onal “Customer RelaEonship
Management” system.
• A replacement for legacy
communicaEon channels like IRC,
mailman lists, newsgroups, etc.

5. Why do we need it?
• Our current tools make it difficult to:
– Find community members
– Contact select groups of contributors
– Create and manage dynamic groups
– Help new people connect with others
– Discover community ac0vi0es and events
– Capture the size and diversity of Mozilla in one
place to share with the world

6. 1st Step: Centralize Contact Info
CRM

7. Key Stakeholders (iniEally)
• Chofmann – Security
• David Boswell – FoundaEon
• David Tenser – SUMO
• Deb Richardson – Evangelism
• Jay Patel – Campus Reps
• Kev Needham – Partners
• Marcia Knous – QMO
• Mary Colvig – Events
• Rafael Ebron – Messaging
• Rey Bango – AMO
• Rhian Gracey – Labs
• Seth Bindernagel – L10N

8. CRM Components
• Community Dashboard
– Snapshot of current ac0vity, map, feeds (integrate Lizard Feeder?)
• Group pages
– Updates, forum, mailing lists, manager/lead contact info
• Member profiles
– Photo, bio, contact info, skills & ac0vi0es, languages, projects
• People search
– Simple or advanced forms to lookup/filter by any profile fields
• Events calendar
– Dates and info for any Mozilla related events, meetups, speakers, par0es
• Mailing lists
– Newsleaers, marke0ng campaigns, on‐the‐fly group emails

9. Use Cases
• Campus Reps
– Students can update their profile each year during the registra0on
period without having to resubmit all their info.
• L10N
– Localizers and their community leaders can manage their teams from a
central loca0on.
• Events
– Mozilla can reach out to community members in specific ci0es or
countries to invite them to events or recruit help.
• Labs
– Designers and developers can find each other through people search
to collaborate on their projects.

10. Home

11. User Dashboard

12. Groups

13. Profiles

14. Roadmap
• Requirements & Architecture (March – April)
– Drupal + CiviCRM UI decisions
– Data, privacy, profile fields, page layouts
• Development (April – May)
– Dashboards, profiles, groups, events
– People search, mailing lists, member invites
• Early Alpha (May 25)
– Legal and security review; QA tes0ng, bug fixing, code tweaking
– Community leads can import data and try it out
• Internal Beta (June 15)
– Invita0ons can go out to select community members
– QA verifica0on, gather feedback, more code tweaking
• Public Beta (TBD: June – July?)
– Integrate mozilla.org redesign
– Watch the Mozilla Universe expand!

15. Q & A + Discussion
• Open QuesEons Today
– Data
• How much do we want to know about each other?
• What data should we enable members to share publicly?
• Who plans to use the data and how?
– Social Structure
• Who should have manager/lead or admin rights?
• When do we promote community members to higher levels of access?
• What do we think about a “Mozilla Guides” system?
– Security
• What things do we need to think about to make it safe and secure?
• How do we go about doing a security audit for a tool like this?
• Future ConsideraEons
– Localiza0on
– Single Sign‐on?
– Social networking?

16. Thanks!
• Images
– Chris Messina for the Mozilla Universe diagram
– Happy Cog for the Dino header image
– Dan Kultz for the CRM mockups
• Support
– Seth Bindernagel, David Boswell, Mark Surman,
and many others for helping get this project
started up again.