The meeting took place here on Slack. @notlaura facilitated and @danfarrow (hello!) wrote up these notes.
@notlaura thanked @danfarrow for running last week’s meeting and hoped that US folks had a happy & socially distanced Thanksgiving.
CSS Cascading Style Sheets. Audit (#49582)
@ryelle reported having spent some time on the CSS audit repo, and asked @danfarrow what else he wanted to do before his PR was ready to commit. @danfarrow suggested it could be committed now and he would continue working in a new PR, so @ryelle merged it there and then.
@ryelle mentioned the config PR and posted a link to an npm package cosmiconf that might be useful. @notlaura reported having made some progress on the feature and will have a working version soon.
We had a short discussion about naming the reports in the repo’s
/public folder, agreeing that historical reports could include the relevant WordPress release number in the filename to form a useful archive.
@ryelle is working on a GitHub 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/ action to automate the report generation so the details can be worked out within that PR. She added that we will want to move the project over to the 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/ GitHub in the next few weeks, a prospect which was received with celebration.
@notlaura asked @danfarrow to update #26350 (the
!important audit ticket Created for both bug reports and feature development on the bug tracker.) with a link to the relevant section of the report and offered a brief roadmap of the next actions: once her config feature is complete we can update the CSS audit ticket and liaise with design to see if they want any additions to the report.
Color Scheming (#49999)
@danfarrow reported still struggling with
wp-env and the remainder of the meeting comprised of @ryelle helping him figure out what was going wrong with his setup (thank you!)
As we ran out of time there was no open-floor / link share, so with that the meeting ended. Thanks everybody!