Create a Shortlist of Communication Tools, Prioritizing Open Source Options

Proposal by @Ali Hugo on behalf of OpenCraft

Topic

Indicate which topic your proposal falls under:

Overview

Given the strong agreement in favor of reducing the number of communication tools we use vs streamlining them (80-15%!), we should consider merging some of these tools. While this approach may pose challenges—since removing tools can be inconvenient for some—it would ultimately benefit us by consolidating and simplifying our communication channels.

Solution

With the list of communication tools compiled as part of the proposal: Evaluate the Communication Tools We Use and How We Use Them, we can identify tools that overlap in features, helping us to decide which tools to keep and which to lose. This could also be a good opportunity to shift away from synchronous and proprietary tools in favor of async and/or open source alternatives, especially since the survey showed that most CC’s prefer open source tools to proprietary ones.

The goal of the proposal is to create a list of the communication tools we should use, along with clear guidelines on when to use each one. 

Impact

We will measure the impact by following up with survey respondents six months after the guidelines are published, assessing whether there is any remaining confusion about which tool to use and when, or any challenges or inconveniences in using the tools.

Timeline & Team

This effort will follow the steps below. Feel free to add any steps/information you think may be missing, or assign yourself to any of the tasks:

• Create a Tool Shortlist: Take the list of tools resulting from the Evaluate the Communication Tools We Use and How We Use Them proposal, and shorten it by eliminating any tools that overlap in features (prioritizing open source over proprietary tools)

  • 1 week, @Ali Hugo + __

• Gather Feedback: Share the shortlist with CC’s and gather feedback. Refine the list accordingly

  • 2 weeks, @Ali Hugo + __

• Get Shortlist Approved: Share the list with CC’s and refine it until the tool selection is approved

  • 2 weeks, @Ali Hugo + __

• Write Guidelines: Create a set of guidelines on when to use each tool

  • 3 weeks, @Ali Hugo + __

• Get Guidelines Reviewed: Ask CC’s to review the guidelines and suggest any improvements or corrections

  • 2 weeks, @Ali Hugo + __

• Add Guidelines to Open edX Handbook: Should the proposal to create an “Open edX Handbook” be approved, we will add these guidelines to it

  • 1 week, @Ali Hugo + __

• Measure Impact: Check in with CC’s 6 months after guidelines are published to determine whether any changes should be made

  • 4 weeks, @Ali Hugo + __