Participants: @abdullahramzan, @adamsilverstein, @aduth, @afercia, @atimmer, @bpayton, @euthelup, @gziolo, @herregroen, @lonelyvegan, Jorge Costa, @omarreiss, @nerrad, @netweb, @pento, @sharaz, @schlessera.
Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.
(Continued from last week’s discussion)
Problem: How can we introduce breaking changes necessary for user benefit without sacrificing a commitment to backward compatibility?
A deprecation strategy proposal has been discussed. Some highlights:
- Console logging turns out to be not entirely successful on its own based on the experience from Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/.
- Feedback collected should be integrated into the UI User interface, ex. Admin (and super admin) bar, Updates screen.
- For those plugins that are using a recommended set of core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. build tools, issues could be surfaced there.
- Chat to #meta about logging all deprecations.
- Discuss Admin bar notifications integration with @johnbillion, who authored Query Monitor plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
- Logging to wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ is also something that should be discussed with the #core-privacy team to make sure we start out in a compliant fashion.
Discussion is going to be continued next week.
Sunsetting the Packages Repository
Last week it was decided in our meeting to merge WordPress/packages repository to the WordPress/gutenberg repository. There is an open pull request at https://github.com/WordPress/gutenberg/pull/7556 which is almost ready to land. We are waiting for Gutenberg 3.2 release to ensure it doesn’t interfere with the development cycle.
- Fix the problematic test suite which started to fail on Travis after it was moved to Gutenberg.
- Merge in the latest changes added in Gutenberg.
- Test, review and deploy Launching code from a local development environment to the production web server, so that it's available to visitors.!
- Ensure all opened issues, PRs , and missing docs are moved over to Gutenberg repository. @netweb started it already.
Core CSS Cascading Style Sheets.
a `src/styles` directory with a ` css` and a `sass` directory. We discussed the following:
- Is Sass the right path forward or should we move closer to native CSS with something like PostCSS?
- There were previous discussions with @helen in the past on further refactoring CSS to use native CSS with PostCSS rather than Sass/SCSS.
- How do we deal with styles reuse in a components era? There are similar ongoing efforts in Gutenberg started by @youknowriad in https://github.com/WordPress/gutenberg/pull/7640.
There have been new proposals with regards to code styling:
- Let’s move forward with quotes exception following the related PHP standards.
- @aduth is going to add more explicit rules around acronyms at start of variable name and leave the rest as initially proposed.
It’s been requested that two core Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets receive approval:
- Make sure all JS globals are explicitly assigned to the window: https://core.trac.wordpress.org/ticket/44371.
- Move all JS build config to Webpack: https://core.trac.wordpress.org/ticket/43731.
@netweb volunteered to review item (2). It was also noted that (2) depends on (1).