HQ component teams

As of Dec 2017, at Moodle HQ each core developer is assigned a list of components to lead. They are responsible for triaging the issues in those components, planning the roadmap of issues to be worked on and should be consulted as part of the peer review process for all issues relating to their components.

The current list of component leads is:

Adrian (abgreeve), Mihail (Geshoski)

Blocks, Blog, Book, Filepicker, Glossary, Lesson, Ratings, Reports, Repositories, Resource

Andrew (dobedobedoh), Mick Hawkins (michaelh)

Email, Forum, HTML Editor (Atto), HTML Editor (TinyMCE), Installation, JavaScript, Logging, RSS, Unit tests, User Tours

Bas Brands (basbrands), Ryan (ryanwyllie)

Themes, Dashboard (My home), Accessibility, HTML and CSS, Navigation, Usability, Javascript (Ryan)

Damyon (damyon), Zig (zig)

Assignment, Assignment (2.2), Competencies, Database activity module, Backup, Backup: IMS-CC

David (dmonllao), Víctor Deniz (victor)

Analytics, Caching, Global search, Gradebook, Grading methods, Libraries, Performance, Tasks

David (mudrd8mz), Sara (sarjona), Amaia Anabitarte (amaia)

Badges, Cohorts, Enrolments, Feedback, Hub, Language, Maths filters, MNet, Plagiarism, Roles / Access, SCORM, Survey, Tags, Translation, User management, Wiki(2.x), Workshop

Jake (jaked), Jun (jpataleta )

Automated functional tests (behat), Choice, Comments, Conditional activities, Database SQL/XMLDB, Events API, Files API, Filters, Forms Library, Portfolio, Web Services

Mark (markn), Carlos Escobedo (carlos)

Activity completion, Authentication, Chat, Course completion, External Tool (IMS-LTI), IMS-CP resource type, LTI provider, Media, Messages

Simey (lameze), Shamim (rezaie9)

Calendar, Groups, Questions, Quiz