CSS Chat Summary: 10 September 2020

See the full meeting transcript here on Slack. I (@notlaura) facilitated the meeting.

Housekeeping

Thanks to @ryelle for leading our second bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub before the meeting!

We still need a volunteer to facilitate the weekly chat on October 8.

Updates

CSSCSS Cascading Style Sheets. Audit

The next steps for the audit are to update the counts and to get the data out of the Google doc, and into the css-audit repo. I (@notlaura) started a PR to add to the CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. --format=report and --report=wp-admin that can write the audit data to an HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. file that can be deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. via GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ pages. Here is a work in progress PR.

Color Scheming

@ryelle has fixed up the PostCSS pluginPlugin 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 so that it works with color functions and rgb() and rgba(). Check out the PR here! The next step is to draft a post we can share in one of the design meetings.

I shared a link to work on color systems in GutenbergGutenberg 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/ from @itsjonq – we discussed that the PostCSS plugin will allow us to swap out any color palette easily, so even if the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. colors in the WP Core Color List now end up changing, it is not a problem to support, but what color list to use will be a key question for design (there are a few to choose from).

We discussed that, in the post for design, we want to:

  1. Make them aware of this project
  2. Check which color system should be used
  3. Let people know that we will be looking for volunteer testers to help with adjustments when we know what color system to use

That was all for this week!

#core-css, #summary

Dev Chat Summary: (5.6 Week 4)

Greetings! Here’s what happened in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Wednesday, September 9, 2020, 07:00 AM GMT+2 and Wednesday, September 9, 2020, 10:00 PM GMT+2 on the agenda.

0500 core devchat

@thewebprincess led the meeting and took notes. Find the full SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. archive here.

2000 core devchat

@laurora led the chat; @thelmachido took notes. Here’s the full archive.

Both groups followed this agenda: https://make.wordpress.org/core/2020/09/08/dev-chat-agenda-september-9th-2020/

Announcements

We started by celebrating WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Ogijima in Japan over the weekend! 

@thewebprincess also highlighted a post by Shinichi Nishikawa about how they set up the tech and will share the link when she finds it.

Highlighted blogblog (versus network, site) posts

Timezones and Daylight savings:

After some discussion across timezones, the two dev chats have agreed to pin meeting times to UTC and let people adjust calendars locally. If the changes mean fewer people at meetings or involved in the project, several folks noted we can also change back.

The version 5.5 release team is still looking for feedback

Please share your perspective on the process — especially what people and teams can do to make future releases smoother for everyone. Please comment by Saturday at 8:00 UTC.

What’s next in Gutenberg

@annezazu updates the community once a month on all things blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.. It’s a great way to stay informed (planning your pluginPlugin 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 or theme roadmap?) and get involved!

A comment on the agenda post:

 @pbearne asked for feedback this ticket. @peterwilsoncc answered and will give him  design feedback.

Component maintainers

Upgrade/Install 

Will explore adding some UIUI User interface elements to manage email notifications on plugin and theme auto-updates.

Privacy 

@carike reported in: “We have been receiving a lot of feedback, for which we are very grateful. Will update tickets over the next few days with more details on the proposed application design.” 

No updates of note this week from Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site, Options/MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., Roles, Menus & Widgets, Build/Test Tools or Customize.

What if a component maintainer can’t make devchat?

After some discussion, this request from the group: Please add your updates as a comments on the Agenda post. 

Open Floor

@thewebprincess asked the people represented to call out the areas they’re focusing on. 
That morphed into a conversation about people’s desire to dig into contributing to E2E testing. At first, it looked imperative to wait for progress from the working group mentioned here – but the group decided there’s no real block to diving in now.

  • Should there be a 5.5.2? 
  •  Ever thought about being a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.? Here’s how you get there.
  • How can we help someone new — or even just watching from the sidelines —  find their place, or is it trial and error? See what people said in the full discussion.
  • One of those quizzes you get on social media all the time, “find your WordPress spirit animal”  led us to this tool, which the WCEU team used for contributor days. How could people use this — or a version — inside teams?

Next Dev Chat meetings

The next meetings will take place on Wednesday, September 9, 2020, 07:00 AM GMT+2 and Wednesday, September 9, 2020, 10:00 PM GMT+2 on the agenda.

 in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

#5-5-1, #5-5-2, #5-6, #dev-chat, #summary

CSS Chat Summary: 3 September 2020

See the full meeting transcript here on Slack. I (@notlaura) facilitated the meeting.

Housekeeping

We need someone to lead the weekly meeting on October 8 – send a message on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. to @laras126, or comment on this post if you are able to do that!

@ryelle added @here privileges for herself and @kburgoine so they can lead the bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs. The bug scrubs / triages will be every other week one hour before the meeting (at 4pm EDT), and @ryelle will lead the next one this Thursday, the 10th.

Updates

CSSCSS Cascading Style Sheets. Audit (#49582)

I added an issue to the CSS audit repo and corresponding comment to the ticketticket Created for both bug reports and feature development on the bug tracker. about storing the audit data on GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ instead of in a Google doc. @ryelle agreed this sounded like a good idea, especially deployments via Github pages, and potentially using Github action to regularly re-build the report. Another idea we talked about is a method to download a specific version of WordPress to run the audits on, so that we don’t have to worry about environment-specific artifacts (e.g. the .orig files from SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. conflicts).

Color Scheming (#49999)

A big week for color scheme updates! @ryelle is close to finished with the PostCSS pluginPlugin 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 that will replace the rogue colors with the approved coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. colors – visualized here. She opened a PR to the WordPress-develop repo that includes screenshot comparisons of the color replacements, and indicated next steps to be:

  1. Finish the transparent color handling
  2. Start the manual work of cleaning up anything that looks awkward after the processing
  3. Maybe add some way of ignoring certain colors/selectors/files

Related to the second item – there will be small issues that require manual review, for example, there is no orange in the color palette, so they have been replaces with reds, and another area where a specific light blue background was removed. We will need input from designers to validate these changes. Rather than adding issues based on screen or color for the review, we discussed having a Make post and allowing people to comment before deciding on a specific review structure.

Open Floor + CSS Link Share

@ryelle shared an enticing Tweet from someone attending Clarity Conf:

I shared the @property syntax where, in CSS only, you can declare custom properties with more details:

@property --colorPrimary {
  syntax: "<color>";
  initial-value: magenta;
  inherits: false;
}

CSS! 🔥

#core-css, #summary

Dev Chat Summary: (5.6 Week 3)

This post summarizes this week’s meetings happening on Wednesday, September 2, 2020, 07:00 AM GMT+2 and Wednesday, September 2, 2020, 10:00 PM GMT+2 on the agenda.

0500 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devchat

0500 Full meeting transcript on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.: https://wordpress.slack.com/archives/C02RQBWTW/p1599022834165200

@thewebprincess facilitated the meeting and took notes.

2000 core devchat

The meeting was facilitated by @thewebprincess while @thelmachido took notes. Full meeting transcript on slack

Both groups followed the pre-prepared agenda and started the chat by acknowledging the adjustment to the new timing of the chat having moved it a day earlier.

Announcements

The group was excited about the release of version 5.5.1. @audrasjb thanked everyone who contributed to the release, specifically @winstina and @hauwaabashiya who hosted their first release parties.

Highlighted blogblog (versus network, site) posts

  • The discussion then turned to how best to accommodate Daylight Savings time changes – whether to shift the meeting or keep it at the UTC times which means time changes for participants.
    “ … how do we adjust for daylight savings?” see  @thewebprincess post. In recent years, the switch was made after all countries shifted to DST. What’s being proposed is that we switch that in favour of consistency with UTC. There’s a loosely described process on the matter in the handbook Daylight Saving Time (DST), however, given the more diverse geography attending dev chat, it may be time to reassess the process.
    We need to decide and document it in time for the first change due to take place on September 27 when NZ adjusts their clocks. The group agreed that the decision will be made next week in the meantime if you have something to add to help inform that decision, please leave comments on the post.

Then in the open time, two issues were discussed.

  • Then this issue https://make.wordpress.org/core/2020/06/29/updating-jquery-version-shipped-with-wordpress/ was raised by @markparnell, asking the question ” what’s the feeling about this given the volume of jQuery issues after 5.5? are we ready to take the next step, or should we take things a little more slowly?” After some discussion, the conclusion was made that it’s too early yet for a decision and that timing of that point would be best before the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. release (@pwcc) so the group will revisit in a couple of weeks. View slack archive.
    Afterwards, @timothyblynjacobs made a comment on the ticketticket Created for both bug reports and feature development on the bug tracker. “If we upgrade to jQuery 3.0 do we anticipate using any jQuery 3.0 features? Or if WordPress Core won’t be reliant on jQuery Migrate, … follow the conversation on Update jQuery step two ticket.
  • Awareness was raised on  Writing Developer Notes handbook for all contributors interested in writing dev-notes for future releases. Also, view the handbook on Leading Bug Scrubs that was based off a post during version 4.7 it was published recently.

Component maintainers

There is nothing of note from Build/Test Tools this week, but if anyone is interested in helping out with adding end to end / functional tests to the core then check out the post from a couple of weeks ago by @francina.

The Site Health team is assessing focuses for version 5.6 in their meeting next week.

@whyisjake – “While the release team is wrapping up the 5.5 processes, they want to reach out to the wider community for perspectives on the process and what could be done in the future to make releases smoother for everyone. Comments can be publicly shared directly on the post that is to come later, or as part of this form. All responses will be catalogued and then shared.”

Closing Remarks 

GutenbergGutenberg 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/ 8.9 was released yesterday by @jorgefilipecosta! Of note, the new widgets screen was moved out of experimental. There will be more to come in the “What’s New” post for the release. A call for testing will be published on WordPress.orgWordPress.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/ after some design changes are done.

@sergey This is for anyone working on unit tests in core, stricter type checking by using assertSame() should generally be preferred now to assertEquals() where appropriate, to make the tests more reliable. This is helpful in the ongoing work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 support. See ticket for more details.

Next Dev Chat meetings

The next meetings will take place on Wednesday, September 9, 2020, 07:00 AM GMT+2 and Wednesday, September 2, 2020, 10:00 PM GMT+2 in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

#5-5, #5-5-1, #5-6, #core, #dev-chat, #summary

CSS Chat Summary: 27 August 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1598562066114200

I (@notlaura) facilitated the meeting.

Housekeeping

Big thanks to @kburgoine for running the first CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.! We discussed getting @here privileges for those who are running the triages, and adding the bi-weekly triage to the Meetings calendar (which is done! Thanks ). The next triage will be Thursday, September 10 at 4pm EDT.

Updates

CSS audit (#49582)

We discussed the steps to update the counts to remove data from generated files (.css.orig and .rtl) – generally, all files that are .gitignored should be excluded. @justinahinon asked about how to do this, and we looked at updating this part of the css-audit repo to exclude additional file extensions, or perhaps get the excluded extensions from .gitignore. With that in mind, the steps for updating the counts can be summarized as:

  1. Ignore .rtl and .css.orig in the css-audit repo
  2. Re-run the commands for each data point
  3. Copy the data into the GDoc

With regards to the third point, I proposed the idea of storing the audit data in GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ instead of the Google doc. For starters, it could be as simple as pasting the data into a markdown or .htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. file that can be deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. on Github pages for viewing.

Color Scheming (#49999)

@kburgoine mentioned breaking up the current audit work into smaller pieces. The next step for the initiative is to replace the colors in the right-hand column of the core color matches with the color in the left-hand column, and to test the results. @ryelle is planning to create a PostCSS pluginPlugin 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 to automate this. I suggested that, in the mean time, we could manually do some find and replace with a piece of the adminadmin (and super admin) to see results. This might at least give some visibility into where problem areas are.

Open Floor + CSS Link Share

@isabel_brison mentioned that Firefox has a font inspector that shows variable font properties…. very cool! More info at this link.

I shared a link posted during the week from @jonoalderson about the Local Font Access API.

That was all for this (last) week!

#core-css, #summary

Dev Chat Summary: August 26 (5.6 Week 2)

This post summarizes the dev chat meeting from August 26th facilitated by @thewebprincess on this agenda.

Full meeting transcript on slack

General Announcements

See @audrasjb post for details on the scheduled maintenance release for WordPress 5.5.1 after a handful of bugs were identified on WordPress 5.5 “Eckstine”. The first Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). is planned to be on Thursday, August 27, 2020, and the Final release planned to be on Tuesday, September 1st, 2020 estimated time 20:00–21:00 UTC or later depending on work to be done on the remaining tickets.

Highlighted blogblog (versus network, site) posts

Components check-in and status updates

The first CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. is being hosted today at 4pm EDT in the #core-css channel. One hour before the weekly Core CSS chat.  

@carikee flagged milestone tickets for privacy initiatives that still open and need to be looked at #51092, #51110 & 51144.

There is nothing of note from the Build/Test Tools component at the moment other than the before mentioned post about PHP updates.

Open Floor

The meeting pivoted into a 5.5.1 pre-RC scrub run

Ticketticket Created for both bug reports and feature development on the bug tracker. #50910 has had some testing but could use some more tests.  It is hopefully going to land for 5.5.1-RC1, so the more eyes the better similarly for #51129.  

@carikee asked committers for their input on whether to use the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. to expose user consent on the front-end. Also, the need to add the extra 10KB or so to expose wp.data to the front end.

@audrasjb flagged  5.5.1 milestones that need to be cleared and @pbiron also flagged 5.5.1 tickets that are still open.  

The meeting continued as a 5.5.1 pre-RC scrub run by @desrosj.

Next Dev Chat meeting 

The next meeting will take place on Wednesday, September 3, 2020, 10:00 PM GMT+2 in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

#5-5, #5-5-1, #5-6, #core, #summary

CSS Chat Summary: 20 August 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1597957254000500

I (@notlaura) facilitated the meeting.

Updates

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.

We discussed doing a triage every two weeks one hour before the weekly meeting. @kburgoine will lead the first one this week, on August 27 at 4pm EDT!

CSS audit updates

@isabel_brison added the media query counts to the CSS audit doc, the last remaining item! She mentioned finding that the audits were running on .css.orig files which was bloating the counts. We discussed that these and .rtl files should not be included in the counts because they are not authored files.

@kburgoine asked if the audit counts are including blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor CSS. We discussed that for now, the audit only includes wp-admin and wp-includes, but the tooling we have can be used for other code-bases. @ryelle suggested documenting the steps for running audits similar to these steps for pulling color data.

The next step for the audit is to update the counts excluding the .css.orig files, and @isabel_brison volunteered to do that in the coming week.

Color scheming updates

@ryelle re-ran the core color extraction steps using the approach referenced above, and the list of unmatched colors is now much more concise. This is quite a useful tool! @ryelle identified that the excess colors were coming from GutenbergGutenberg 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/. Since the colors are much more manageable now, it will make sense to go to design for feedback a bit later in the process once the PostCSS piece is in place and we can see the reduced colors in wp-adminadmin (and super admin).

@kburgoine asked if there was any way to break down this task into smaller pieces – it is a lot of work for one person. @ryelle said that later in the process, once we have files with the reduced colors, there will be many smaller tasks such as manual cleanup and testing that will be fit for more contributors.

Open Floor / CSS Link Share

There were no open floor topics.

@kburgoine shared a very slick Codepen that changes the font weight of a menu item on hover, without causing a reflow/jump on following menu items!

That was all for this (well, last) week!

#core-css, #summary

Dev Chat – APAC Edition Meeting Summary – August 20 2020

@peterwilsoncc called us to order and introduced @thewebprincess as the release coordinator and handed the chat over to her facilitation. 

The chat started out loosely following the same agenda as the earlier chat celebrating the commencement of the new release and release squad.

This sparked an excited response about having an APAC based release coordinator and a cheeky question about whether or not the release party would now fall into APAC timezones as a result. (Let’s cross that bridge when we come to it).

We also highlighted the same two posts for review.

Open floor

As it was initially a fairly quiet gathering @thewebprincess took the opportunity to ask some probing questions about what it’s like to contribute to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. when you’re based in the APAC timezones; specifically “What are the biggest challenges to contributing from this part of the world? And what more could be done to help alleviate those challenges?” 

There were some great responses to arise out of this conversation, which you can read in detail here

There was agreement that the advent of dev chat and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. in APAC timezones have made the feeling of isolation from the core conversations has lessened somewhat which is great to hear.

The regional participants are also really hopeful that having release leadership based in this timezone will be a really positive step forward to increasing the cohort of participants in the region. 

We then discussed steps to help improve participation in the APAC region, these were the areas we covered:

  • @webcommsat advised that the marketing team have an initiative under way to help promote different meetings – so next steps is for a chat to happen to talk about what that might mean for APAC dev chat (and dev chat in general).
  • Making the APAC dev chat a bit more visible by taking and posting notes after the call (we have made a commitment to do this going forward, starting with these notes).
  • We then discussed the timing of the meeting and whether moving the APAC chat to before the Americas/EMEA one would help reduce barriers to entry for APAC participants (opening for discussion below).
  • Changing the language used to describe each dev chat in order to give them equal weight as a means to help increase participation/perceived value.

Requests for Comment

  1. The consensus for the members present was that there would be significant benefit in moving the APAC call forward (earlier) by 24 hours. This would mean:
  • The agenda notes would need to be posted 24 hours earlier than the APAC call to allow both discussions to follow similar agendas
  • There may be an increased need for maintainer teams to add their updates to the agenda post for discussion in the chats as most maintainers won’t be available for the earlier call
  1. Adjusting the language around how we describe the dev chats to give each equal weight – currently we have ‘dev chat’ and ‘APAC dev chat’ let’s discuss what a more equable format might look like… here are a couple of options that were thrown in to the call such as using UTC time to differentiate chats (2000UTC dev chat or 0500UTC dev chat), using regions – America/EMEA Dev Chat and APAC Dev Chat or something else…

What do you think?

Before making such changes it is important to open this up for discussion so that all interested/affected parties might add their thoughts to the conversation, we’d love to hear from you below if you have anything to contribute.

#5-6, #dev-chat, #summary

CSS Chat Summary: 13th August 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1597352455033300

I (@notlaura) facilitated the meeting.

Housekeeping

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.

We discussed having a triage for CSS tickets. A triage can be led by anyone at a time outside of the weekly meeting. Everyone at the meeting agreed this was a good idea, and @ryelle and @kburgoine volunteered to organize some in the future.

Here is a link to tickets with a CSS focus in Trac and this link is for the CSS Styling label for issues in Gutenberg. Some teams to separate triages for core and GutenbergGutenberg 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/, and this is something to consider. If there are any recurring triages, they would be listed here on the Make meetings page (thanks @justinahinon!).

Updates

CSS Audit

There was a permissions issue with the relocated Google doc, but that is resolved now – thanks @isabel_brison!

Color Scheming

@ryelle shared more progress on the color matching project from last week, so that now colors are grouped according to distance from an “approved” color. A next step would be turning this into a PostCSS pluginPlugin 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 or similar that would replace the colors that are within a certain distance of a core color with the core color.

We discussed some of the outlier colors in the project and that they are likely from vendor CSS, and that some of the colors that are slightly off (e.g. the purples) could be from the adminadmin (and super admin) themes.

Another next step, perhaps more immediate, would be to share this project with the design team to confirm the colors being used. @ryelle mentioned putting the project on GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ and adding some issues as well to foster collaboration.

Open Floor

CSS Link Share

I pointed out a couple of links @jonoalderson shared between meetings:

@kburgoine shared a very relevant article from Smashing Magazine highlighting using custom properties for configurable color schemes. Very cool!

That was all for last week!

#core-css, #summary

CSS Chat Summary: 6 August 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1596747640462000

I (@notlaura) facilitated the meeting.

Housekeeping

How can we help new meeting attendees get up to speed on initiatives?

We discussed that adding a note to the top of the agendas with the ticketticket Created for both bug reports and feature development on the bug tracker. links will be helpful, and in the future, we can make improvements to the CSS Coding Standards page in the handbook.

Structure for meeting agendas

This was a check-in to see if the current meeting structure was still working for everyone, and general response was yes, though we should ensure there is enough time for open floor each meeting.

CSSCSS Cascading Style Sheets. Audit Updates

We updated the location of the doc to (though there are some permissions with this one currently): https://docs.google.com/document/d/1S21GAVYLO9unCG8a16tqlZleB9UeMqEqYeX1MLNduHA/

@tellthemachines looked into the history of coding standards and stylelint, and found the CSS Coding Standards in the handbook (same as above reference) and the stylelint configuration which is only used in GutenbergGutenberg 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/ at the moment. She suggested that, once this piece is finished, we post a summary of the results and outline next steps, and perhaps take it to the dev chat for more visibility. Exciting!

Color Scheming Updates

I made a very quick visualization of the top 50 colors and counts based on the data from @ryelle‘s CSS Audit tool which can be viewed here. I also checked with the design channel about what they reference for color values, and that can be a few places:

  1. What is directly used in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  2. This color palette in the handbook (which is what @melchoyce uses for core designs)
  3. This color proposal from @davewhitley
  4. And the Gutenberg colors, which are a bit different

I mentioned the possibility of programmatically comparing the colors from the audit with a list of approved colors and very fittingly, @ryelle started on something along those lines! Based on this CodePen of the colors from the Handbook, @ryelle has a wonderful start at grouping and comparing colors in core against these colors. Check out the comparisons here!

We discussed the possibilities of automating the replacement of colors in a certain categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. with “approved” colors, and that it would be challenging given some blurry lines in the categorization and ensuring appropriate contrast.

CSS Link Share

@kburgoine shared a couple of amazing CodePens – this one animation, and this one a painting in CSS! And @tellthemachines posted a link to a talk by the artist / programmer who created the painting.

I shared a link about a potential option for grid-template-rows: masonry; that could be coming in CSS.

#core-css, #summary