WP Notify Meeting Recap – January 13 2020

This is a recap of the WP Notify meeting held on Monday, January 13, 2020, 14:00 UTC. You can read the meeting discussion here.

We’re resuming our work on the WP Notify project with better focus on actionable ways to address the challenge of notifications in WordPress.

We started by answering more pointed questions as to what the solution must address, and whether a temporary alternative should be entertained at all.

Temporary Solution

@psykro suggested to post a separate tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker., to improve the current admin_notices implementation, with sample code from @apedog

The benefit to this is that, as a team, we get something into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. that improves users lives and we gain some real world experience of how the process could be improved by the final solution.

The negative is that it would mean this code is likely to be eventually replaced by our final, better solution. This very discussion, is the reason we want to present this concept to the community, for feedback on whether to a) expand admin_notices, or b) affirm the need for an entirely new replacement solution altogether, and what are the critical elements of that new approach

@schlessera is of the opinion, and rightly so, that any work done to improve the current admin_notices functionality is not worth the time. We should rather work on a solid, scalable and manageable solution for notification channels.

Permanent Solution (From The Onset)

A few of the very direct questions we must address for the replacement solution as suggested by @folleto are

  • What are we replacing? (if anything)
  • What kind of backward compatibility do we need?
  • What’s the minimal APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. and UIUI User interface we need to build for a v1?

As we answer these questions, we’re keeping in mind the end-user experience together with the API required. For example, a notifications menu will need a completely new way of handling notifications in WordPress API through use of the database and rendering those messages.

As @schlessera pointed out “The initial UI should satisfy the 80% need of letting Core/plugins/themes communicate platform state changes within the adminadmin (and super admin) dashboard in a scalable way where the user/user group keeps control.”

Meeting time

During the course of the meeting it became somewhat clear that the time of the meeting might be causing some problems for folks in different time zones. Conversation in the meeting became much more active after the first hour. Therefore we would like to know if the current meeting time is suitable, or if we should consider an alternative?

Next-Steps

Please comment with your thoughts below. You can also add comments your comments in the WP Notifications Project Google Doc under Section 1. “Objectives”

Next 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/. Meeting

📅 Monday, January 20 @ 14:00 UTC

#feature-plugins, #feature-notifications, #summary

WP Notify weekly meeting notification for Monday 13 January 2020

The WP Notify feature project continues in 2020, with our first meeting of the year to be held on Monday, January 13, 2020, 14:00 UTC. We will take this opportunity to review the current status of the project, determine where we are at, where we need to go, and how we need to get there.

As the project has been on hiatus since late 2019, there is no fixed agenda, but I’ve listed a few items below we will be discussing.

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #feature-notifications channel , to join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #feature-notifications

WP Notify hiatus till January 2020

As the year end almost upon us, the WP Notify team will be taking a hiatus until January 2020.

Personally I’ve not been in a position to drive the current requirements gathering process and the weekly meetings, and @hrmervin has just started a new position, which is currently his primary focus.

We are both still committed to moving this project forward, and will post the first meeting time for the new year closer to the time, but for at least the rest of this year, we both need to focus our time elsewhere.

If anyone would like to continue the meetings for the month of December 2019 and help drive the requirements gathering process forward, please comment here or reach out to myself or @hrmervin 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/..

You can see the current status of this project in the #feature-notifications channel , to join, you’ll need an account on the Making WordPress Slack.

#feature-notifications

WP Notify meeting for 28 October 2019 cancelled.

With WCUS just around the corner, the WP Notify meeting for 28 October 2019 is canceled.

If anyone wants to chat about WP Notify, @hrmervin will be available to connect with folks at the WCUS Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/..

#feature-notifications

WP Notify – Meeting Recap – Oct 21, 2019

This is a recap of a meeting held October 21 for a CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. project related to WordPress Adminadmin (and super admin) Notifications. Meetings on this task are held every Monday at 14:00 UTC and 22:00 UTC respectively.

Related Links

Google Doc: WP Notify Project Requirements Document

Notes Per Agenda

Open Floor for Feedback

Our discussion this meeting further refined the focus of this project, to be a solution “… 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 and theme developers can leverage, again instead of using admin_notices.”

Present handling of admin_notices will require distinction between immediate (core) based notifications such as successful saves, and a queue of notifications to be followed up on at a later time.

This project seeks to pave the way so future projects can build upon the new notifications handling. Enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. such as mail or push notifications handling, will be able to leverage the processing we create here.

Next Steps

We welcome feedback on the project either here in this post, or in the requirements (via Google Doc, comments). 

We invite you to attend our next meeting, held in 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/. > #feature-notifications

  • Monday, October 28 2019 at 14:00 UTC 
  • Monday, October 28 2019 at 22:00 UTC

#summary

WP Notify weekly meeting agenda for 21 October 2019

Here is the agenda for the weekly meeting happening later today, Monday, October 21, 2019, 14:00 UTC and Monday, September 21, 2019, 22:00 UTC.

  • Opening and welcome
  • Discussion: What is the objective of this project?
  • Update on requirements gathering process
  • Open floor

If you have anything specific to propose for the agenda, please leave a comment below.

This meeting is held in the #feature-notifications channel , to join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #feature-notifications

WP Notify weekly meeting agenda for 14 October 2019

Here is the agenda for the weekly meeting happening later today, Monday, September 30, 2019, 14:00 UTC and Monday, September 30, 2019, 22:00 UTC.

Please note that the 14:00 UTC meeting has been cancelled, but the 22:00 UTC meeting will continue.

Our main point of focus is the ongoing work on the requirements gathering document process, so during this meeting we ask those who have been working on this document to give us a brief update.

If you have anything specific to propose for the agenda, please leave a comment below.

This meeting is held in the #feature-notifications channel , to join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #feature-notifications

WP Notify Meeting Recap – October 7 , 2019

This is a recap of a meeting held October 7 for a CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. project related to WordPress Adminadmin (and super admin) Notifications. Meetings on this task are held every Monday at 14:00 UTC and 22:00 UTC respectively.

Related Links

Google Doc: WP Notify Project Requirements Document

Notes Per Agenda

Proposal to continue merging recap and agenda into one post

@hrmervin: Volunteered to prepare the weekly recap following Eastern US time meeting

We have an open `call for scribes` if anyone is interested in volunteering alongside Mervin to take notes and/or prepare a recap.

Update on requirements gathering document

@hrmervin: Created a visual representation of the present hook workflow. As we continue to write the details of this project, we will create diagrams to illustrate A) The feature’s (feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.) hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., B) the Data being managed and how it will flow, and C) the user(s) views and endpoints (how the notifications will be consumed)

  • We discussed adding names for our target users.
    • Site Admins (non-technical)
    • Site Admins (Technical)
    • Product Authors (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 and Theme authors)

Discussion on overlap of TRT Admin Notices package

@aristath: Spoke on an admin notice package developed to help theme authors manage notices.

“The WPTRT package is a simple wrapper for the core functions to make it easier for theme-devs to add admin-notices in a consistent manner, avoiding all the issues we’ve had in the past with theme-reviews. It’s pretty simple if you look at its code, simply sanitizing/escaping, and handling the notices dismissing.”

  • We may incorporate aspects of this package into the front-end parts of our end solution.

Open floor

  • One recommendation for future technical implementation was made by @ediamin “fetch the notifications with 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/. and show them with 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/ Notice and/or Snackbar components”

Next Steps

We welcome feedback on the project either here in this post, or in the requirements (via Google Doc, comments). 

We invite you to attend our next meeting, held in 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/. > #feature-notifications

  • Monday, October 14 2019 at 14:00 UTC 
  • Monday, October 14 2019 at 22:00 UTC

#summary

WP Notify Meeting Recap – September 30, 2019 & Weekly Agenda

This post summarises the weekly WP Notify chat meeting from September 30th 2019.

For the sake of efficiency, it also includes the weekly meeting agenda for the meeting to be held later today (October 7th, 2019)

Weekly WP Notify meetings are held every Monday at 14:00 UTC and 22:00 UTC respectively.

Feedback on requirements gathering

Document link

Last week, we built a basic requirements table of content for the requirements. @dinhtungdu started filling it with the data collected from the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. and proposal document.

We still need to add more content from the conversations took place on the Trac ticket and the Proposal.

What we archived last week is a skeleton which is ready to add more content to. This does however make it easier for new contributors to get up to speed on the focus of the project

@karmatosed raised a concern that on reading the doc, it seems to be going to technical requirements first and asked whether explorations in user flows/experience been thought about yet.

@hrmervin has offered to start to piece something together for the flow of information.

@ediamin inquired about whether there any plan to include any background processor into WP coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., to facilitate WP Notify using WP Cron to dispatch the notifications. They also pointed out that WooCommerce uses this and it’s very efficient.

@daniloercoli asked that we take the mobile apps in the consideration. Right now the apps “talk” with the backend via XML-RPC. There is a plan to upgrade the communication layer to 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/., but it’s still not there due to the “missing” authentication part.

Agenda for next meeting

  • Proposal to continue merging recap and agenda into one post
  • Update on requirements gathering
  • Discussion on overlap of TRT Admin Notices package
  • Open floor

Comments/suggestions are encouraged and welcome. If you want to add any agenda topics, please also comment on this post.

#feature-notifications, #summary

WP Notify weekly meeting agenda for 30 September 2019

Here is the agenda for the weekly meeting happening later today, Monday, September 30, 2019, 14:00 UTC and Monday, September 30, 2019, 22:00 UTC.

Our focus at the moment is on the requirements gathering document process, so the meeting will be mostly updates on that process.

If you have anything specific to propose for the agenda, please leave a comment below.

This meeting is held in the #feature-notifications channel , to join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #feature-notifications