Confirmed users
46
edits
ParticipationSystems/RepsPortal: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (Added emoji) |
No edit summary |
||
| Line 6: | Line 6: | ||
Update the Reps Platform to provide an easier and more streamlined tool for the Reps to facilitate their work. Look at opportunities to expand current or upgraded technology to other parts the Mozilla. Before any new work can be prioritized, the current Reps Portal needs a large lift update to continuing operation as is. After that, new work that addresses some known ‘work arounds’ from current technological limitations can start. | Update the Reps Platform to provide an easier and more streamlined tool for the Reps to facilitate their work. Look at opportunities to expand current or upgraded technology to other parts the Mozilla. Before any new work can be prioritized, the current Reps Portal needs a large lift update to continuing operation as is. After that, new work that addresses some known ‘work arounds’ from current technological limitations can start. | ||
This project is part of the larger [[ParticipationSystems|Participation Systems]] initiative. | |||
More details will come at the end of Phase 2 - Research. | More details will come at the end of Phase 2 - Research. | ||
| Line 18: | Line 20: | ||
Continue Research Phase with goal of completed all first round interviews, pending availability. | Continue Research Phase with goal of completed all first round interviews, pending availability. | ||
== 🚩 Goals == | |||
==== Phase 1 ✅ Complete==== | |||
Project conception | |||
Alignment of resources | |||
Putting the pedal to the metal | |||
Phase | ==== Phase 2 ==== | ||
Interview stakeholders to gain an understanding of how Discourse is used across Mozilla | |||
* Identify pain points | |||
* Identify opportunities for improving the platform | |||
* Document the current status of its administration and infrastructure. | |||
* Find and compile existing metrics being collected | |||
Define functional requirements for access control and permissioning features | |||
Build a product roadmap for future development | |||
* Prioritize features | |||
* Identify preliminary requirements | |||
* Define resources necessary to begin work on roadmap | |||
==== Phase 3 ==== | |||
Begin development work | |||
* Create project implementation plan | |||
* Begin development work | |||
= 👥 Get Involved = | = 👥 Get Involved = | ||
This is a great project to get get involved with if blurby blurb | This is a great project to get get involved with if blurby blurb | ||
This project is beginning to define and reach out to stakeholders. If you believe you might be stakeholder and we haven't reached out to you yet, please reach out to Lyre Calliope. | |||
The definition of a stakeholder is: | |||
* Actively involved in the project. | |||
* Who’s interests may be positively or negatively affected either by the work of the project or the outputs from the project. | |||
* Who may exert influence over the project or its deliverables. | |||
Additionally, you can follow our work and something something through our comms channels | |||
* Specific action | * Specific action | ||
* Specific action | * Specific action | ||