CSS Chat Summary: 07 January 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes. Happy New Year!

Housekeeping

@notlaura asked if the recurrant format of the meetings is still working and there was general agreement that yes, it is.

CSSCSS Cascading Style Sheets. Audit (#49582)

@ryelle commented that @notlaura‘s config file PR is looking good and that she has started a new PR using GitHub actions to auto-generate the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS audit report.

@notlaura shared a screengrab of an issue with the report’s in-page navigation when used with config files. The full text of each property-value query is being used in the nav making it look quite unwieldy.

This led to a discussion about how property-value audit queries should be formed in order to provide useful results, and then to a recap of the end goals of the audit. The consensus was that one of the main goals is to improve consistency of CSS values, and to identify repeatable patterns which could be abstracted into design-system type naming.

@ryelle clarified that this was the thinking behind audits reporting the top 10 most & least used values.

Color Scheming (#49999) & Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)

@ryelle expressed some doubts over the benefits of the reduced colors branch. The group was quick to dispel these doubts, pointing out several ongoing benefits of the project and assuring her that it’s well worth continuing with.

Bolstered by the positivity, @ryelle said she would refresh the branchbranch 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". and bring it up at the next dev chat.

Open floor & CSS link share

@ryelle put a call out for testers for patches she has contributed to these three CSS related trac tickets.

@notlaura shared a link to @q‘s 2020 proposal about a global style system, suggesting it would be cool to apply to apply such a system to WordPress adminadmin (and super admin).

And with that inspiring thought the meeting drew to a close. Thanks everyone!

#core-css, #summary

CSS Chat Summary: 17 December 2020

The meeting took place here on Slack. @notlaura facilitated and @danfarrow (me!) wrote up these notes.

Housekeeping

We discussed the meeting schedule over the next two weeks. There was general agreement that we should take the next two weeks off, so the next meeting will be 07 January 2021. Happy holidays!

CSSCSS Cascading Style Sheets. Audit (#49582)

@danfarrow reported that we can now add a note to the !important audit ticketticket Created for both bug reports and feature development on the bug tracker. #26350 with a link to the !important audit section of the report (update: this note has now been added here).

Thanks to @sabernhardt‘s comprehensive audit spreadsheet we can see that the number of !important declarations has dropped from 142 at the start of this year to the current 106.

@ryelle reported an issue with the colour counts which means they are slightly off, however in order to fix it would require a major overhaul of the audit process. However, the discrepancy is minor.

@ryelle also noted that colours defined in colour schemes are not currently included in the numbers and suggested that they should be included.

Color Scheming (#49999) & Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)

@ryelle has pushed a PR for reduced colours in core which is one step in her plan outlined in this comment.

She also shared her excellent before & after comparison page built to enable comparison between current & reduced colours.

We agreed that the next step is to bring this up in the first dev chat in January.

For visual regression testing, @isabel_brison suggested that the next step would be to separate the test config from the e2e config to enable them to be run independently.

Open floor & CSS link share

@danfarrow shared an enlightening article on The Surprising Things That CSS Can Animate, from the UI Animation newsletter.

@notlaura shared an excellent CSS Tricks article from Jeremy Keith on “the enjoyment of building a website with plain ol’ HTML, CSS, and JavaScript” which inspired an exchange of thoughts & feelings about web tools.

The conclusion was that our favourite web tool platform is of course ❤️ WordPress ❤️, and on that note the meeting concluded.

Thanks everybody and see you in 2021!

#core-css, #summary

Dev Chat Summary Dec 16th 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, December 16, 2020, 05:00 UTC, and Wednesday, December 16, 2020, 20:00 UTC. Both chats followed this agenda.

05:00 UTC core dev chat
@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.

20:00 UTC core dev chat

@laurora facilitated the meeting and @thelmachido took notes. Find the full Slack archive here.

Announcements

Reminder – State of the Word is today. Set your alarm for the time Thursday, Dec 17th, 2020 at 1600 UTC so you don’t miss it!!

The 5.6 retrospective has started! We’d love as many of you as possible to share your feedback with us via the form linked in this post

The Full Site Editing Outreach program is officially underway. It will start with the release of 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/ 9.6 around December 23rd with plenty of time to be involved. If interested in joining the fun, please head on over to #fse-outreach-experiment. There is a comprehensive status update on Site Editing, view the post from Matias.

@abhanonstopnewsuk would like to inform us that the questions and answers on the release have had some updates thanks to a number of comments from user experience, to further help non-technical users. These updates will be posted 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/.

Highlighted Posts

Component maintainers and focus leads

Build/Test Tools
Work has continued on GitHub Actions in this ticketticket Created for both bug reports and feature development on the bug tracker. #50401. There are also 3 relevant commits to take note of. r49781 Disable GitHub Action workflow runs triggered on push for forks and mirrors. r49782  Use NodeJS 14 in GitHub Action workflows. r49783  Enable reporting of results to WordPress.org

Site Health
A small ticket for 5.6.1 came in today, so it’s looking manageable

@clorith pointed out that jQuery updates got flagged early

Comments Component
@imath updated the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. on this ticket #33717, feedbacks welcome

@flixos90 is planning to commit iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. lazy-loading today #50756

Upgrade and Install
There is a plan to have error stats for 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/theme updates failures sent to dotorg #51928 in 5.7

Open Floor

  • @iandunn would like to get some broader feedback on #51966 – please review and leave comments on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
  • A question was raised during chat, does a theme upgrade require being tied to a core upgrade?. The issue was raised because of this ticket #52040 @audrasjb said that this issue can be fixed in a TT1 release because a theme upgrade doesn’t need to be tied to a core upgrade. You can follow the full conversation here.
  • Learn WordPress was launched yesterday and a big cross teams effort including contributors from community, training, marketing, polyglots, design, 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., core and more. There are some more fun promotions in store too. Social videos have been produced for the promotion of Learn WordPress. Here is an example, the team would like to encourage contributions in other languages.  They’re also exploring how to support older audiences to use WordPress through the resources on Learn WordPress. Any hands to help with this? pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @nalini 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/..
  • @annezazu worked to redo the core feature projects page. Project owners where contacted for the latest status, description/intro paragraphs where updated, core editor items where added, and inactive projects where hidden to make the page more focused.

Next Dev Chat Meeting

The next meetings will take place on Wednesday, December 23rd 2020, 05:00 UTC and Wednesday, December 23rd 2020, 20:00UTC 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. 

#props to @thelmachido for consolidating both sets of notes together prior to publishing.

#5-7, #summary

CSS Chat Summary: 10 December 2020

The meeting took place here on Slack. @notlaura facilitated and @danfarrow (me!) wrote up these notes.

Housekeeping

@notlaura congratulated everyone who worked on the 5.6 release.

CSSCSS Cascading Style Sheets. Audit (#49582)

@danfarrow shared his updated version of the audit report (featuring sticky headers & dark mode!)

@notlaura reported having the style property values audit working, and making progress on her config PR which is nearly ready.

@ryelle reported a new PR to tweak report generation in order to decouple audits from specific templates, which would reduce the number of templates required.

Some great progress happening!

Color Scheming (#49999)

@danfarrow reported having fixed his wp-env problems and generated visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. diffs based on the initial PR from @tellthemachines.

We discussed how this feature could be incorporated into wordpress-develop, and agreed that the tests would be best run manually. The discussion concluded with a positive sense that this tool could meet one of the goals of the CSS audit project.

@ryelle reported that her public demo site for reduced adminadmin (and super admin) colours shouldn’t be used at the moment as it needs updating.

Open floor / CSS link share

@notlaura shared a link to Houdini.how, a community-driven resource library to learn about CSS Houdini.

And with that the meeting concluded. Thanks everybody!

#core-css, #summary

Dev Chat Summary: December 9 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, December 9, 2020, 05:00 UTC and Wednesday, December 9, 2020, 20:00 UTC.

05:00 UTC core dev chat

@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.

20:00 UTC core dev chat

@francina & @johnbillion facilitated the meeting and @laurora took notes. The full Slack archive can be viewed here.

Announcements

WordPress 5.6 aka “Simone” was released yesterday (8 December 2020). The release squad was entirely made of people identifying as women and non-binary folx. You can read more about the release in this blog post. At the time of the meeting, @helen shared that it’s already exceeded 3 million downloads.

The annual State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. will be taking place Thursday 17 December at 1600 UTC. If you’d like to submit a question, the deadline is Friday 11 December! This post has more information.

Updates from Component Maintainers/Focus Leads

Build/Test Tools:

@desrosj is continuing to work on the 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/ Action workflows and backporting the local Docker environment to the remaining older branches.

@desrosj has been working one repo at a time to convert the Travis configurations to workflows. If you maintain any repositories under the WordPress GitHub organization and want to help with the transition, feel free to DM him.

Open Floor

@afragen requested some extra eyes on #51976. If you’re able to help out, please add your comments to the ticketticket Created for both bug reports and feature development on the bug tracker.. And also added that if you’re after a larger challenge to take a look at #51928, noting that patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. might need to be moved to #51857.

Next Dev Chat meetings

The next meetings will take place on Wednesday, December 16, 2020, 05:00 UTC and Wednesday, December 16, 2020, 20:00 UTC 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.

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

CSS Chat Summary: 03 December 2020

The meeting took place here on Slack. @notlaura facilitated and @danfarrow (hello!) wrote up these notes.

Housekeeping

@notlaura thanked @danfarrow for running last week’s meeting and hoped that US folks had a happy & socially distanced Thanksgiving.

CSSCSS 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 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/ 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.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/ GitHub in the next few weeks, a prospect which was received with celebration.

@notlaura asked @danfarrow to update #26350 (the !important audit ticketticket 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!

#core-css, #summary

Dev Chat Summary – 2 December 2020

The meeting was facilitated by @peterwilsoncc and @thewebprincess while @mikeschroder and @johnbillion took notes. Full meeting transcript on Slack. Both groups followed this pre-prepared agenda.

Announcements

Highlighted Posts

  • A Week in Core – November 23, 2020
  • What’s next in Gutenberg? The monthly report is out
  • Discussion: Update the updater
  • Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are continue to be updated ready for final release, here’s the latest dev-notes.
  • Release cycle discussion post – we need your feedback!
  • WP Notify project review

Component maintainers and focus leads

@peterwilsoncc reminded everyone that these components are in need of maintainers:

If you’re wondering what being a maintainer involves, @markparnell linked this guide from @francina.

Open Floor

@noisysocks requested review on #51612, which aims to make the  render_block_data, pre_render_block and render_block_context filters run on nested blocks. The PR with the latest approach can be found here.

The 2000 UTC group discussed #51913 and #51918 which led into a general discussion about the level of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support in 5.6 and how to communicate it. @marybaum asked for clarity to ensure all the marketing messaging is accurate.

The current consensus is that coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is “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.-compatible”, which means 5.6 works on its own with PHP 8, but that any given site may not work due to the plugins and themes in use and that more defensive programming is needed in core.

Next Dev Chat Meeting

The next meetings will take place on December 9, 2020 at 0500UTC and December 9, 2020 at 2000UTC 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. 

Apologies

Apologies from @johnbillion for the late posting of this summary. The post sat in draft until today when I was reminded of it.

Onwards!

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

Media Meeting Recap – December 03, 2020

The following is a summary of the weekly Media component meeting that occurred on Thursday, November 3, 2020 at 15:00 UTC. Weekly media meetings are held every Thursday at 15:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @antpb, @sergeybiryukov, @joedolson, @hellofromtonya, @joel-yoder, @mista-flo, @aristath, @alexdeborba

Media Focus for 5.7

The focus for 5.7 was discussed and it was mentioned that there were many outstanding accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issues that should be considered. It was agreed these should be moved into the scope of the release.

#50105: Remove infinite scrolling behavior from the Media grid

#50273: Media modal uses incorrect ‘checkbox’ role for list items

#47120: Media modals: Upload errors and field information are not associated with their control

#39004: Alt attributes should be searchable in media library

There has been a bit of buzz in the Media 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 around a desire for more modern media formats to be considered as a focus. @azaozz recommended prior to the meeting that the following is considered when modern image formats are considered for 5.7.

A Media Focus Lead for 5.7 would be good if everybody here thinks we’ll manage to add support for (at least) .webp . Currently this is still at the “exploratory” stage. Main questions that needs solid answers:

How to resize WebP images?

How to detect browsers that don’t support WebP and serve fallback images?

Would WP expect the users to upload WebP images or would it convert JPEGs, PNGs and GIFs to WebP?

Seems that ideally WP will convert uploaded images to WebP and serve them when the site visitor’s browser supports them. The originally uploaded images would serve as fallback. Determining browser support would be best by “Server-side content negotiation via Accept headers”. Replacing <img> with <picture> on the fly would bring a lot of side effects/compat problems. Frankly not sure if that would be ready by the cut-off time of early to mid February, even if work starts right now  On the other hand, this needs to be done, 5.7 or not.

@azaozz

After a bit of discussion from attendees, it was generally agreed that for modern media formats there is still discovery work that needs to happen, a proposal to scope the work, and an outline of risks and blockers. The questions asked by @azaozz above are a good starting point in thinking this through.

@joedolson asked “Is there any reason modern image types can’t be staged across multiple releases? E.g., add support for uploading & inserting modern image types, and expand usage later? There’s nothing about adding WebP and SVG that requires them to be globally used; just made available. The bigger problems seem to be in what happens if you start auto-switching existing images between img/picture, etc.”

We’ll leave these these notes on 5.7 with an invitation to comment below about further considerations.

Time of Meeting

For frequent attendees it was determined that the current time of 15:00 UTC is currently working for most people’s schedules. If there are any thoughts on this time, feel free to comment below!

Props @antpb for proofreading and final review.

#core, #media, #summary

Editor chat summary: 2nd December 2020

This post summarizes the weekly editor chat meeting (agenda here) held on 2020-12-02 14:00 UTC in Slack. Moderated by @andraganescu

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/ 9.5 Recap

  • Full details on the release are available in the release post.
  • Full Site Editing and Global styles were the main focus of this release and as always many bugs were fixed and some nice features were introduced.
  • @youknowriad mentioned that during the release process an “undefined” tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) was temporarily temporarily created. It should be fixed now.

Preparation for WordPress 5.6

  • Release candidate #2 (RC2) has been released.
  • Make sure to take this 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). for spin and if you find any pesky bugs add them to Github
  • The current editor must haves board is, as always in the 5.6 Project board

Monthly Plan & Key Project updates

Global Styles & Editor focused APIs

Continued fixing the flows (tracking issue, label) and this week’s highlights are:

Full Site Editing

  • Just in case that if you were previously following this project board for Full Site Editing, it has now been closed in order to use the milestones issues more consistently and to prevent people from needing to follow the progress in two places.
  • The “template mode” in the post editor is close to landing. This is just a first iteration but I believe this might become an important way in which a lot of users might start interacting with FSE templates (PR: 26355)

Widgets screen, Navigation screen and CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.

For Widgets and the Customizer the updates are in the form of a renewed focus and also the current blocks in the customizer exploration phase.

Task Coordination

  • @nosolosw
    • Main focus still is GlobalStyles: reviews, move forward my own PRs, triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. issues.
    • Started digging into FSE to add support for child themes.
  • @ntsekouras
    • Add vertical layout to Buttons 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. with block variations (https://github.com/WordPress/gutenberg/pull/27297).
    • I’m working on block variations and a way to display the variation’s info in needed places, such as BlockCard, Navigation List view etc..
  • @q
    • I’ve been focusing on the next iteration of the Gutenberg UIUI User interface (WordPress Components) – codenamed “G2 Components”.
    • I’ve been continuing my (almost) daily live streams covering design, development, architecture, and planning for this project :).
    • I recently published a blog post with progress updates and thoughts/details on how we’re planning the delivery of the project:
  • @paaljoachim
  • @aristath
    • I continue working on splitting the block assets and only load them when a block is rendered (PR 25220)
    • Exploring how to remove auto-drafts for unedited templates and instead use the files directly (PR 27321)
    • Focusing on FSE & global-styles
  • @annezazu

Open Floor

PR for move post/page title to the top bar needs discussion (PR 27093)

  • @paaljoachim brought the issue up into the open again as it would be great to move the post/page title to the top bar so that we can get used to adding the post/page title block into the layout.

Thanks to everyone who attended!

#core-editor, #core-editor-summary, #meeting, #meeting-notes, #summary

WP Notify Project Review

It has been approximately 5 months since the WP Notify team wrapped up the Requirements gathering process, and kicked off the next phase of the project. This post aims to summarise the work done so far and to start looking at how the project will evolve in the new year.

Call for office hours hosts

Our weekly office hours are held every Monday at 2pm UTC. Originally I was the sole host of these meetings/office hours, but due to the yearly daylight savings time change, that meeting now conflicts with a work-related meeting I have every week.

Fortunately, @raaaahman has stepped in to help host these office hours, but I would like to make an open call for a second office hours host, to help share the load. Another option would be to move it to a different time slot, but I don’t want the meeting time to be specific to my availability.

The requirements to host are very little, we provide you with a script you can follow, and all the relevant details of the project, and all you merely need to do is ensure that the office hours are opened, and closed, and be available to take any relevant notes that may come up during office hours.

If you are interested to assist, please comment on this post, or reach out to myself or @raaaahman.

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/ repository

It was agreed that the project would be designed/developed publicly through GitHub, and a repository was created for this purpose. At the present time, the project trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. is empty, but the develop branchbranch 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". contains the initial work done by @schlessera, which we will be using as a base for development.

Design

It was also agreed that our first steps would be to start iterating on the design of the new WordPress notification system, and much work has been done by @folletto, @ibdz, @hedgefield, and others, to visualize the requirements of the project. Much of the design work has been detailed in issue #23 and issue #26, and we invite other designers to challenge the direction, or just suggest different approaches. While we’re starting to get close to a final agreed-upon design, suggestions are still welcome.

Development

While the designs are being iterated on, the development efforts have focused on tooling and processes. As soon as the designs are finalized, we plan to start active development of the new features.

#feature-notifications, #summary