ParticipationSystems/discourse evolution: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Edits)
m (β†’β€ŽπŸ‘₯ Get Involved: minor edit, because ocd)
Β 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{draft}}
This page contains all of the important details for the Discourse Evolution project.
This page contains all of the important details for the Discourse Evolution project.
{{draft}}


= 🌍 Project Information =
= 🌍 Project Information =
Line 10: Line 9:
This project is part of the larger [[ParticipationSystems|Participation Systems]] initiative.
This project is part of the larger [[ParticipationSystems|Participation Systems]] initiative.


For details, see our [https://docs.google.com/document/d/1kglYhUvNkVQgLRhyhOjaDHfcaKR6B6KOchU_ymAkJLI project brief (draft in progress)].
More details will come at the end of Phase 2 - Research. Β 


== πŸ—£Status ==
== πŸ—£Status ==
== 🚩 Goals ==
===As of May 26th 2016 ===
Research Phase underway. First round of interviews taking place.


==== Phase 1 βœ… Complete====
=== Planned work for week May 30th 2016 === Β 
Project conception
Continue Research Phase with goal of 50% of planned interviews conducted and preliminary analysis of findings.


Alignment of resources
== 🚩 Goals ==
Β 
Putting the pedal to the metal
Β 
==== 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
==== Phase 1 - Initialize βœ… Complete====
* Prioritize features
# Project conception
* Identify preliminary requirements
# Alignment of resources
* Define resources necessary to begin work on roadmap
# Putting the pedal to the metal


==== Phase 2 - Research ⏳ In Progress ====
# 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 ====
==== Phase 3 - Implementation ====
Begin development work
# Create project implementation plan
* Create project implementation plan
# Begin development work
* Begin development work


= πŸ‘₯ Get Involved =
= πŸ‘₯ 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 the first round of stakeholders. If you believe you might be stakeholder and we haven't reached out to you yet, please reach out to Lyre Calliope.


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 someone:
Β 
The definition of a stakeholder is:
* Actively involved in the project.
* 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’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.
* Who may exert influence over the project or its deliverables.


Additionally, you can follow our work and something something through our comms channels
Additionally, you can connect with us through Participation Systems communications channels:
* Specific action
* IRC channel: [irc://irc.mozilla.org/%23participationsystems #participationsystems] ([http://chat.mibbit.com/?channel=%23participationsystems&server=irc.mozilla.org Mibbit])
* Specific action
* Forum: [https://discourse.mozilla-community.org/c/participationsystems Participation Systems Discourse Category]
* Join us on our communications channel(s)
** Discourse
** [irc://irc.mozilla.org/%23ParSoL #ParSoL]


= πŸ“ Project Management =
= πŸ“ Project Management =
Line 68: Line 63:
|-
|-
| style="height:100px; text-align:center;" |Lyre Calliope Β 
| style="height:100px; text-align:center;" |Lyre Calliope Β 
Hermina Condei
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Leo McArdle
| style="height:100px; text-align:center;" |Hermina Condei
(Who else?)
| style="height:100px; text-align:center;" |Community Ops
| style="height:100px; text-align:center;" |Ruben Martin
REPS Council
Pierros Papadeas
| style="height:100px; text-align:center;" |David Ascher
Β 
David Ascher
Β 
Simon Wex
| style="height:100px; width:100px; text-align:center;" |Name
name
name
Β 
Β 
|}
|}


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


Notes & Meetings Hub
Notes & Meetings Hub

Latest revision as of 19:25, 31 May 2016

Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
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.

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

🌍 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.

More details will come at the end of Phase 2 - Research.

πŸ—£Status

As of May 26th 2016

Research Phase underway. First round of interviews taking place.

Planned work for week May 30th 2016

Continue Research Phase with goal of 50% of planned interviews conducted and preliminary analysis of findings.

🚩 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 project is beginning to define and reach out to the first round of 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 someone:

  • 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 connect with us through Participation Systems communications channels:

πŸ“ Project Management

Key People (RASCI)

Responsible Accountable Support Consulted Informed
Lyre Calliope George Roter Hermina Condei Community Ops

REPS Council

David Ascher

Smartsheet (Project Plan) Forthcoming

Notes & Meetings Hub