25 docs tagged with "Processes"

This document proposes a checklist for accessibility reviews. Not all aspects of accessibility can be checked automatically, so this checklist is intended to guide reviewers when doing an accessibility check to a patch.

Whilst we'd all like all Moodle users to be using our latest and greatest code, there is a balance to strike between improving our software and maintaining stability (both in terms of regressions, but also training and documentation materials). Large amounts of change on the stable branches make the lives difficult for institutions to manage upgrades between point releases.

Triage is a medical term referring to the process of prioritising patients based on the severity of their condition so as to maximise benefit (help as many as possible) when resources are limited.

This document summarises the intent, purpose, and process surrounding component lead reviews (CLR).

The Component Library is a tool designed for developers to identify frequently used user interface (UI) components and encourage their reuse within Moodle. It includes both components from Twitter Bootstrap and Moodle itself. The library provides an organized display of these components, showcasing them with your current Moodle theme.

If you want to contribute to Moodle, you can start looking at the following:

Deprecation, in its programming sense, is the process of taking older code and marking it as no longer being useful within the codebase, usually because it has been superseded by newer code. The deprecated code is not immediately removed from the codebase because doing so may cause regression errors.

A summary of the various development processes used in Moodle development.

Issue labelling

- Set up your development environment

Since Moodle 4.5, it's possible to safely deprecate and remove icons.

All the information related to the integration review process during the Moodle development.

The development of new features and improvements in the Moodle App is organised in the following six phases:

This page describes the procedures for creating a new Moodle user docs version wiki.

This page gives an overview of the process of developing Moodle and outlines some of the basic concepts to better understand this Developer documentation.

All the information related to the peer-reviewing process during the Moodle development.

This is information for people who want to performing a penetration test of their Moodle instance as well as information for pen testers.

All the information related to the Qualify Assurance tests during the Moodle development.

8 weeks prior

Since Moodle 4.4, it's possible to deprecate SCSS styles and classes. This allows us to safely remove SCSS and will help us keep the code cleaner and more organized.

In the Moodle software, security issues are treated very seriously. Even though a lot of time is dedicated designing the code to avoid such problems, it is inevitable in a project of this size that new vulnerabilities will occasionally be discovered.

All the information related to testing during the Moodle development.

This page has suggestions for developers on how to write good testing instructions for the weekly testing of integrated issues.

All the information related to the integration review process during the Moodle development.

A summary of the most common actions in Moodle tracker.