ParticipationSystems/discourse evolution

This page contains all of the important details for the Discourse Evolution project.

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

🌍 Project Information

📎 Summary

Involving core contributors across the full lifecycle of projects around Mozilla remains a challenge. Part of this challenge is the lack of an accessible and secure place for staff and volunteers to discuss sensitive information. To address this we're building access control and permissions functionality into Discourse and establishing a development roadmap to improve the functionality and UX of Discourse so it meets the collaborative needs of mozillians.

This project is part of the larger Participation Systems initiative.

For details, see our project brief (draft in progress).

🚩 Goals

Phase 1 - Initialize ✅ Complete

1. Project conception
2. Alignment of resources
3. Putting the pedal to the metal

Phase 2 - Research ⏳ In Progress

1. 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
2. Define functional requirements for access control and permissioning features
3. Build a product roadmap for future development
   • Prioritize features
   • Identify preliminary requirements
   • Define resources necessary to begin work on roadmap

Phase 3 - Implementation

1. Create project implementation plan
2. Begin development work

👥 Get Involved

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
• Join us on our communications channel(s)
  • Discourse
  • #ParSoL

📝 Project Management

Key People (RASCI)

Responsible	Accountable	Support	Consulted	Informed
Lyre Calliope	George Roter	Hermina Condei	Community Ops REPS Council	David Ascher

Smartsheet (link + What is this and how to use it)

Notes & Meetings Hub