Full meeting transcript here on Slack. @notlaura facilitated the meeting.
If anybody is interested in being a note-taker for these meetings we would love to have your help!
CSS Cascading Style Sheets. Audit (#49582)
@notlaura recapped last week’s discussion of her PR to add report generation to @ryelle‘s nifty CSS Audit tool. A git rebase was required for @notlaura‘s PR which she reported is mostly done.
@ryelle reported that the PR is nearly ready to merge. @notlaura sought clarification from @danfarrow (me!) about whether it’s important to have a separate template partial for each section of the report. I was able to (eventually) respond that I believe it is indeed important because the data structure can differ between different report sections.
@ryelle reported having sketched out a promising 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 which would commit the generated report back to the repo, bringing us closer to the goal of automated reports with a version history.
Color Scheming (#49999)
@notlaura recapped last week’s progress where we had design team confirmation of the color list, plus a possible volunteer to help.
@ryelle reported an exciting update – she has set up a demo site on Pantheon for the reduced-colors test. The access details are here in Slack.
@ryelle added that anyone who would like to help or who needs admin (and super admin) access can DM her with their email and she will create an individual admin account for them. She suggested that the wp-core-color-list repo would be a good place to track issues.
@notlaura questioned if we could make it clearer to testers where they can post issues by adding a dashboard widget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. to the demo site with some instructions about how to contribute.
@ryelle agreed to add this, but also suggested that it would also be helpful for testers to run the branch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". under their own setups to get a broader view of compatibility with various plugins, and in particular multisite 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 setups.
There was a short discussion about the value of testing admin schemes at this stage, the outcome of which was “it wouldn’t hurt to check just in case”.
@notlaura pondered the best way to announce this to testers, and suggested notes in #design and #accessibility. @ryelle agreed to add notices to those channels.
CSS link share / Open floor
I (@danfarrow) shared a link to an app I found which is an interactive glossary of CSS vocabulary & terminology http://apps.workflower.fi/vocabs/css/en
It seems like a really useful learning tool, and was received with enthusiasm! There’s also an HTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. glossary http://apps.workflower.fi/vocabs/html/en
And with that the meeting was concluded. Thanks everyone!