Reps

ReMo is the code name for the Mozilla Representatatives Program, a program that aims to recruit and support volunteer Mozillians who want to be “official” Mozilla representatives in their region/locale.

Purpose

In our general efforts to scale and leverage the power of community, ReMo will provide a simple, systematic and structured commmunity-driven framework to inform, empower, assist and support Mozilla volunteers who want to become official representatives of Mozilla in their region.

Anti-Purpose

Here are some things ReMo specificly aims NOT to do :

• replace or undermine efforts by existing communities of Mozilla volunteers around the world to recruit new contributors
• become a top-down ambassador program run exclusively by Mozilla staff

Use Cases

An initial (and likely incomplete) list of possible use cases for this system:

• Answer the question "who is that?" in various systems.
• Identify a community member by searching for their first name and scanning through photos in the search results.
• Compile a list of people to invite to a Leadership Summit (all currently-active trusted contributors who are team/project leaders or above).
• Find everyone working on a particular project.
• Find all our contributors who live within 50km of Ottawa, Canada.
• Generate a world map of all our contributors.

User Tasks

• Accept invitation
• Log in/out
• Create profile
• Edit profile
• Delete profile
• Reset password

Administrator Tasks

Everything a User does plus...

• Delete profile (at user request only)

Implementation

• Python and Django, because that's what webdev are most familiar with and I want to be able to ask for their help :-)
• Profile and search outputs (via templates) as HTML (with HCard), JSON (perhaps using PortableContacts schema), VCard, XRD (for WebFinger)
• LDAP vs. SQL - tricky. A directory back end means that perhaps it could one day run on top of Mozilla's LDAP authorization infrastructure, using the same database. But I know SQL much better. To be investigated.
  • The Mozilla LDAP also contains lots of sensitive corporate IT details that might be best to keep isolated from a public directory, for what it's worth
• I plan to rip the HTML UI off from the current intranet Phonebook.
• Making it actually happen is more important than the use of any one particular technology.

Resources

• Gerv :-) I'll be writing the code.
• Contributor Engagement are very interested in the project, and are offering help.
• L10n are interested in the project, and can offer help.
• David Boswell has offered to help.
• Design Needs
  • We'll need someone to help design form pages, maybe just the main profile page that allows you to adjust your privacy settings as seen in the Privacy UI Demo.