WP Notify Meeting Recap – September 2, 2019

This post summarises the weekly WP Notify chat meeting from September 2nd 2019 (agenda / Slack Archive).

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

Requirements gathering tools

Based on the discussions from last weeks meetings, and the comments on the recap post, the general consensus is that a combination of a single Google document and the Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). blogs and/or tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets would be suitable enough for our requirements gathering efforts. @nadir is of the opinion that trac is not suited for this, it gets noisy quickly with any reference or simple change, it will also add mental space to anyone triaging.

Project Naming

@netweb raised a good point and enquired as to whether there was any specific reason for naming the project “WP-Notify”, and suggested “Notifications-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.”. However, as the project aims to introduce a better overall experience, of which a new API will form part of, other names suggested include:

  • Notifications Feature
  • Notifications System
  • Notifications Hub
  • WP Notifications

@netweb added his feedback on the various names during the second meeting, and is still in favour of “Notifications API”, based on the fact that this was what the original proposal was called, and will the vast majority of the work required to be undertaken.

Requirements gathering process

We need to put together a team who will work on this document, so if you’re keen to assist with compiling this document, based on the original trac ticketticket Created for both bug reports and feature development on the bug tracker. and the project proposal, please comment on this post of this meeting. We probably need 2 – 3 extra hands, over and above @psykro

Open floor

  • @hrmervin will be, sometime in the next few weeks, compiling a team members list – with time zones, and desired area to contribute to.
  • @folletto pointed out that we should reach out at some point to existing businesses and 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 developers to make sure they can extend the system as they need.
  • A11yAccessibility 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) considerations where discussed and @hrmervin has offered to take lead on such efforts.

Comments/suggestions are encouraged and welcome.

#feature-notifications, #summary