696756 - Mozilla Reps

Status: RESOLVED DUPLICATE of bug 639113

(mozilla.org Graveyard :: Webdev, task)

Description

[Pierros Papadeas [:pierros]]

Overview: Mozilla Reps web tools and portal is the next phase of tools for the Mozilla Reps program (wiki.mozilla.org/ReMo). Its purpose is to provide the required tools for the day to day operations of the hundreds of Reps signed up in the program

Project Scope: Provide a community platform to share common practices using already existing tools or pioneering in creating new ones.
Resolve scalability issues, like metrics overview, delegation of tasks, increase efficiency of mentors (+1)
Resolve tedious and repetitive tasks (+1)
Include community in planning and building
Provide easy to follow procedures for common representation tasks (swag requests, event requests, budget request) 

Dependencies: None

Assumptions: Usage
   Single sign-in on all tools
   Tight integration with mozillians.org platform providing added project-specifc functionality
   Modular approach and rollout 
Visual
   Uniformity
   Minimalism
   Reuse tools (modular) 
Developing
   Volunteer participation
   Modular
   Productize of the apps in mind
   Mobile Friendly 
Privacy
   Tiers per personal info
   Direct Visualization of Privacy settings
   Total User control

Deliverables: P1: Mentors are traversing too many (>50) wiki pages to find out if mentorees have filed reports. Build a reporting system.
P1: Mails are sent out in an unsustainable manner, manually, over regular intervals (monthly reminders, weekly warnings) to hundreds of Mozilla Reps. Build a warning system.
P2: Swag and budget requests are triaged manually (comparing 100s per month to past-defined guidelines) over different systems and swag ordering is also done manually (filling over and over again the same fields). Build integration with vendor's swag system.
P2: Wiki pages have an editing overhead that demotivates Reps from report and plan ahead their actions in Events. Build an event system or build on top of joint event system efforts in mozilla.
P3: The scalability of the current awards system (i.e. manually performed) is not scaling well with hundreds of Reps in the program. Build reward assessment system (on top of reporting)
P3: Meetings are fragmented with no ability to push agenda items top-down (from council to regional meetings) and logs are not kept in an efficient way (no meeting notes, and action items). Even when we have action items they are difficult to find. Build an automated meeting logs/action system (on top of dashboard)

More info on tools and P's in the wiki: https://wiki.mozilla.org/ReMo/Planning/Website