Call for feedback – WP Notify v1 requirements document

Way back in August of 2019, we posted a Feature Project Proposal for a new way of handling WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. notifications, called WP Notify.

The goal of this proposal is to create a new (better) way to manage and deliver notifications to the relevant audience.

Since then, a small team of dedicated, passionate contributors have been working on what this feature should look like, how it should work and ultimately, what it should deliver to both users and developers of WordPress. Early on it was agreed that we should focus on drafting the requirements for a minimum viable productMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia (MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia) of this feature, in order to put the pieces in place, deliver value early, and iterate with feedback.

I am happy to report that the requirements document for this MVP has been competed, and is ready for review and community feedback.

You can view that document here.

We would like to reach out to the wider WordPress community, ask them to review this document, and add their feedback in the comments of this post.

Feedback like “great work”, or just a like, is always welcome :-), but we would also ask you to consider the details of the document. Is there some technical limitation we’ve missed? Perhaps something that could be left out of the MVP releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.? While we ideally don’t want to making drastic changes to the list of project requirements at this stage, we do know that it takes a village to build a new feature.

Comments for this post will remain open until Tuesday, June 30, 2020, 22:00 UTC.

#feature-notifications