Cold numbers
22 issues have been successfully integrated with 7 rejected and 30 delayed. That's 75% success rate this week!
Notes
- Have you ever heard about the "ready_for_integration" label? It can be used for devs missing "pull-request" permissions to indicate that an issue is, after their review, ready. It has been added to the "Tracker issue labels" doc page. You can use this filter is to check which issues have that label. Important: the correct label is "ready_for_integration" (to match every other label). For now, we've kept in the filter the old using "-" just in case somebody reintroduces it
- There are still 64 issues awaiting peer-review
... Will this number be under 50 any day?
- MDL-45227 landed this week. It includes some RTL improvements to Atto but, for now, it has been only applied to master. In order to consider to backport it to stables safely (3.7 and 3.8), we would like to ask you to test it intensively: different operating systems, browsers, languages... TIA!
- Four weeks for Moodle 3.9 LTS code freeze : Monday, 4th of May.
- This week we've started the "Moodle Party Daily ONLINE", a 30 minutes session open to all Moodlers around the world. You'll find more information here.
Hot topics
- MDL-45227: Add text direction to default ATTO generated markup
- MDL-67734: Create basic skeleton for a global xAPI library
- MDL-64494: Contrast of colours for success, info, error and warnings text is not accessible
- MDL-68116: Prepare Moodle to be ready when h5p.org down completely so that only the author can see the test content
- MDL-58964: Add existing class attributes to Boost flat navigation nodes
- MDL-67995: Single activity format dropdown from types of activity empty
- MDL-52319: Failed environment.xml check does not prevent plugin from being installed
- And lots more in areas like questions, LTI, H5P, accessibility...
One at a time
This (non-regular) new initiative in the integration posts aims to get various policy issues communicated and, with your collaboration, decided and applied in an organised way.- This week we have achieved an agreement about MDLSITE-5667 (Coding style ruling about function/method return types and nullables), matching the PSR-12:
1) No whitespace between the nullable character (question mark -?) and params or return types.
2) No whitespace between the function closing brackets and the colon.
With an image speaking a thousand words. Correct:
public function foo(string $bar, ?int $baz): ?bool {}
(you can find the complete version already @ Moodle Docs / Coding style)
- For the next week, we would like to propose the following issue, granting you the opportunity of commenting there over the next 4 days: MDLSITE-6096: One webservice per class. We'll be waiting for your comments there!
Remember you can find all the policies issues reviewed in the "One at a time" section in the following epic: MDLSITE-6092
Warm thanks
- To Nadav Kavalerchik, Shamim Rezaie and all the people helping to make Moodle more RTL languages friendly 😘
