Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Charter

The Documentation Working Group focuses on:

Comprehensive Documentation: Assist in developing detailed guides and references for all user roles (educators, course operators, site operators, and developers).

Improved Discoverability: Implement strategies to make documentation accessible, easy to find, and navigate (with a clear structure, table of contents, indexing, and search functionalities).

Enhanced Reliability: Ensure that documentation is always up-to-date and easily accessible.


Notes (replace with 1?)

Improved Docs Ecosystem: Maintain a broad perspective of Open edX ecosystem tools / docs meant for long term reference, transient projects, group conversations, etc. (Breadth)

Source of Truth: Cultivate central sources for community documentation fit to their purpose or need

Community Engagement: Encourage a collaborative environment where community members can contribute and find support.

By concentrating on these areas, we aim to provide a robust and user-friendly documentation ecosystem on Read the Docs that supports the Open edX stakeholders.

How to join us

All public Working Group meetings follow the Recording Policy for Open edX Meetings

  1. Join our Slack Channel, #documentation (may be updated)

  2. Join our monthly meetings (to be linked)

How we make decisions

By default, decisions are made by lazy consensus:

Lazy consensus means that when you are convinced that you know what the community would like to see happen, you can assume that you have consensus in favor of the proposed work and and get on with it. You don’t have to insist people discuss and/or approve your plan, and you certainly don’t need to call a vote to get approval. You just assume you have the community’s support unless someone says otherwise.

Lazy consensus works only if you communicate with enough advance notice, and with enough details that people who would object have the time and the necessary information to do so. Generally speaking, it’s better to over-communicate.

How to work on issues

We can organize an internal sprint to focus on 2 or 3 key documentation issues to ensure that important and urgent updates are promptly addressed and have other issues to allow contributors to select and work on topics relevant to their expertise.

We can prioritize by accuracy, clarity, relevance, and discoverability.

https://github.com/orgs/openedx/projects/32/views/2

Members

Leadership

Contributors


  • No labels