WP Notify Meeting Recap – January 20 2020

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

Based on feedback received at meetings and comments, we focused on making the Objectives section in the requirements document more concise.

We also added a Use Cases section, based on feedback from the previous meeting recap post.

Use Cases

This is the excerpt of the “Use Cases” section as compiled by @folletto and @psykro.

Section 2. Use Cases
1. Action required: the plugin wants the user to take a decision, i.e. “you got a comment” (action, notification)
2. Onboarding: the plugin wants to provide guidance on a specific feature, i.e. “try this feature” (action, on-page/notification)
3. Informative: the plugin wants to inform the user about something, i.e. “backup completed” (no action, notification)
4. State: the plugin changes its state, i.e. “settings saved” (no action, on-page)
5. Marketing: the plugins wants to advertise something or suggest an upgrade, i.e. “buy an upgrade!” (action, on-page)

Requesting Feedback

  • Should we address possible unintended uses (example: Notifications of subscribe/unsubscribe from site which may include a profane username?) @folletto
  • For implementation, should we port notifications (such as marketing notes) only to the user who activated the plugin? @m1tk00
  • Further comments / remarks on the 📄 Requirement Document are welcome, and we added appendix references of related projects for inspiration (https://docs.google.com/document/d/1SoIaFqXkXiVzq5mizbZQafMfL36bD0WKj8iwYM823MI/edit#)

Next Slack Meeting

📅 Monday, January 27 @ 14:00 UTC

A note about how we hope to advance the project forward at a steady pace: by working together on the requirements document during meetings, and as time allows in between with comments and channel talks. Once we gather feedback on our goals and actionable steps in the best interest of a merge-able project, then we will progress with next sections of the document and work. @psykro @hrmervin

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

WP Notify weekly meeting agenda for Monday 20 January 2020

This is the agenda for the next WP Notify feature project meeting, to be held on Monday, January 20, 2020, 14:00 UTC.

In order to start shaping the final requirements document, I’d like to start focusing on each section of the document, ensuring that it contains the correct information. The idea here is that we keep iterating on each section until we consider it complete, and then we’ll move onto the next.

So the focus of this meeting, and it’s recap post, will be on the section titled “Objectives”. The general agenda of the meeting will be as follows:

  • Opening and welcome
  • Reviewing and updating the requirements document: Objectives
  • Open floor

If you have anything else 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 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 trac ticket, 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 core 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 API and UI 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 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 Slack 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 Slack.

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 Day.

#feature-notifications

WP Notify – Meeting Recap – Oct 21, 2019

This is a recap of a meeting held October 21 for a Core project related to WordPress 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 “… plugin 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. Enhancement 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 Slack > #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 Core project related to WordPress 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 plugin) hooks, 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 (Plugin 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 API and show them with 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 Slack > #feature-notifications

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

#summary