This is a recap of the WP Notify meeting held on Monday, February 24, 2020, 14:00 UTC. You can read the full meeting discussion here in Slack.
We focused on the next sections of the requirements document, Section 3 “Current Status”, and Section 4 “Project Goals”.
Section 3. Current Status
- Finalized description of existing API 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. features and limitations
Section 4. Project Goals
- We continue refining the definitions of our MVP "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 (minimum 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) a.k.a. Version 1.0
- We outlined important research the project should include
- We noted importance of retaining backwards compatibility of notifications handling
At the close of the meeting, @hrmervin posed the question of how/if Gutenberg 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/ methods of notification handling can influence this project, either in short term or long term.
Next Slack 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
Join us next week, where we’ll continue the discussion on the project goals, and system feature requirements.
📅 Monday, March 2 @ 14:00 UTC