April 3, 2019

[lenaorobei]

Please add your topic as a comment to the issue. Use following format:
Topic description and link to PR, if any (duration in min)

🎥 (Recording](https://youtu.be/UCNATY5ZIfU)

[lenaorobei]

• Magento Coding Standard Versioning Magento Coding Standard Versioning Strategy #136 (5 min)

• Discuss implementation and severity of new Magento Coding Standard rules (15 min)

  • Proxies and interceptors MUST never be explicitly requested in constructors Proxies and interceptors magento-coding-standard#59 by @maderlock

  • Slow array SHOULD NOT be used in loop #20 Impelement ArrayMerge sniff in foreach magento-coding-standard#72 by @larsroettig

  • No try block detected when processing system resources #21: Impelement rule magento-coding-standard#77 by @larsroettig

[joshuaadickerson]

• PSR 14 more generally, using PSRs to standardize https://magentocommeng.slack.com/archives/C4YS78WE6/p1553709474019800

[buskamuza]

@melnikovi : adding an optional argument in constructor.

• @akaplya : currently it's a MINOR change, we should not do such changes in Magento patch releases
• @buskamuza : we should distinguish classes that have to be extended (because there is not way around it) and classes that can use composition (as intended). See also Added a section about breaking changes that require approval devdocs#4156
  • @larsroettig : there are many extensions that inherit from Magento core classes
• @kandy : ext developers should follow best practices and write tests to validate against new Magento releases to be sure that the extension is not broken