WP Notify Status Update

It has been approximately 2 and a half years since the WP Notify feature project was officially proposed. This post attempts to provide a high-level status update of the project.

Current resources

We have an official GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repository that includes initial work done by @schlessera, open issues that have been worked on, and a few open PRs. It also includes a wiki, which contains all our current documentation, including the V1 requirements document and the initial designs.

Much of the current development has been focused on two areas.

  1. Updating the 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. to make it ready to provide the desired endpoints to support the front end implementation.
  2. Taking the initial designs and turning them into HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers./CSSCSS Cascading Style Sheets. that can be sent out for feedback/review.

The progress of the latter item can be viewed on this open issue. Quite a bit of work has been done by @sephsekla, but there are still some things outstanding.

Meetings

Originally we met for a formal meeting with a meeting agenda at 2 pm UTC on Mondays in the #feature-notifications channel 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/.. However, due to a lack of available hosts, we moved towards an office hours approach. Sadly this has completely tapered off, as that time does not seem to benefit most interested contributors.

Where to from here

It would be great if we could get the open GitHub issue moved along, so that we have tangible designs that can be installed, reviewed, and feedback given. This will also allow developers to build the API to support the designs. If there are any front-end developers out there who would like to help, here is your opportunity.

I would also like to suggest that we move our office hours to another day in the week because I’m not able to make that time anymore. I am more than happy to continue hosting office hours from next week, at the same time, but on a different day of the week. My suggestion would be to move it to Wednesdays at 2 pm UTC.

#feature-notifications, #summary

WP Notify Office Hours Change

I’d like to suggest a shift in the weekly WP Notify Office Hours.

Due to a change in my personal life, I can no longer attend these office hours and successfully contribute.

I would therefore like to suggest that we move office hours to either Tuesdays at 14:00 UTC or Thursdays at 14:00 UTC.

I will leave the comments open until Monday, March 22, 2021, 18:00 UTC, at which time I will update this post with the final agreed upon change.

#feature-notifications, #meeting

WP Notify Planning Meeting Notes from Monday, February 8, 2021

The WP Notify team met on Monday, February 8, 2021, 18:00 UTC.

The purpose of this meeting was to discuss and prepare any relevant information needed in order to post a project update for the next WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev-chat.

Meeting notes

The meeting was ended on the hour by @psykro, with the team excited to share our progress with everyone at the next Core dev-chat.

We invite all designers, developers, documentation writers, project managers, testers, builders, butchers, bakers, candlestick makers, and any other interested parties to join us and help build the WP Notify notifications system for WordPress.

Anyone interested can get started by visiting the GitHub repository and following the relevant links to the wiki.

#feature-notifications, #meeting

Notification of formal WP Notify Planning Meeting – Monday, February 8, 2021

The WP Notify team would like to invite all interested parties to a formal planning meeting, to be held on Monday, February 8, 2021, 18:00 UTC in the #feature-notifications channel of the Make WordPress Slack. This meeting will take place instead of the weekly office hours chat for that week.

The purpose of this meeting will be to discuss and prepare any relevant information that might be needed, to be able to post a project update for the next WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat. Part of this update will be a call for developers, as we are at the stage where we would like to formally kick off the development phase of the project.

Meeting Agenda

  • Opening and welcome
  • Review of the project requirements document
  • Review of the design process outcomes
  • Review of the open GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issues
  • Open floor

By the end of this meeting, we hope to have a list (or action points to complete this list) of all relevant documents/issues/information that we would like to share with the core team during dev-chat, in order to allow interested parties to “hit the ground running”.

If there is anything specific you would like added to this agenda, please leave it in the comments section of this post.

#feature-notifications, #meeting

WP Notify Project Review

It has been approximately 5 months since the WP Notify team wrapped up the Requirements gathering process, and kicked off the next phase of the project. This post aims to summarise the work done so far and to start looking at how the project will evolve in the new year.

Call for office hours hosts

Our weekly office hours are held every Monday at 2pm UTC. Originally I was the sole host of these meetings/office hours, but due to the yearly daylight savings time change, that meeting now conflicts with a work-related meeting I have every week.

Fortunately, @raaaahman has stepped in to help host these office hours, but I would like to make an open call for a second office hours host, to help share the load. Another option would be to move it to a different time slot, but I don’t want the meeting time to be specific to my availability.

The requirements to host are very little, we provide you with a script you can follow, and all the relevant details of the project, and all you merely need to do is ensure that the office hours are opened, and closed, and be available to take any relevant notes that may come up during office hours.

If you are interested to assist, please comment on this post, or reach out to myself or @raaaahman.

GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repository

It was agreed that the project would be designed/developed publicly through GitHub, and a repository was created for this purpose. At the present time, the project trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. is empty, but the develop branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". contains the initial work done by @schlessera, which we will be using as a base for development.

Design

It was also agreed that our first steps would be to start iterating on the design of the new WordPress notification system, and much work has been done by @folletto, @ibdz, @hedgefield, and others, to visualize the requirements of the project. Much of the design work has been detailed in issue #23 and issue #26, and we invite other designers to challenge the direction, or just suggest different approaches. While we’re starting to get close to a final agreed-upon design, suggestions are still welcome.

Development

While the designs are being iterated on, the development efforts have focused on tooling and processes. As soon as the designs are finalized, we plan to start active development of the new features.

#feature-notifications, #summary

Outcomes from the last WP Notify feedback post

A month ago I posted an update post for WP Notify, in order to start planning for the next phase of this project.

This post includes a short review of the feedback from that post, as well as the outcomes/next steps.

Feedback

  • Generally the feedback on the post and the requirements document was good. It was also pleasing that more new contributors were made aware of the project, and left their comments on the document.
  • It was generally agreed that a GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repository makes the most sense as a central location for all work to be done.
  • There was no general consensus around the weekly meetings.

Outcomes

The GitHub repository has been created. We need to decide if we’re going to start building using existing code, or completely from scratch.

We also need to start designing the user interfaces. There are already designs from @hedgefield on the original trac ticket, but those designs may need a refresh based on our current requirements document.

And finally, I’ll be resurrecting the weekly meetings in the #feature-notifications channel 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/.. These meetings will however switch to an office hours format, without an informal agenda. These office hours will take place on Mondays at 14:00 UTC. Due to time constraints on my side, the first open office hours will be on Monday, August 17, 2020, 14:00 UTC.

I invite all interested parties to join me in our first office hours on the 17th of August 2020, as we start implementing the project we’ve all been planning for the past year.

#feature-plugins, #feature-notifications, #team-update

WP Notify – next steps

Now that we have finalized the initial requirements for the WP Notify project, it’s time to kick of the project build.

I would therefore like to open the floor for suggestions on how best to move forward. I have some initial comments/questions, that I would like to gather feedback on.

  • We should probably start with designing/prototyping what the various pieces will look like.
    • What software will we use for design/prototyping
    • How will we gather feedback to the designs.
  • As discussed in our requirements document, this will be built as a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.. We therefore need to start the process of deciding on where/how this 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 will be built
    • Will we use GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, or WordPress style svn + tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.?
    • Are we able to start developing the framework of the plugin/making development decisions?
  • It would be ideal if we could identify/select two separate reps for these efforts, a technical rep to manage the plugin development and a design rep to manage the design efforts.
    • How will we select these folks?
    • Do we have any candidates?
    • It’s important to note that these reps could change over time, but for now I’m just considering how we deal with making decisions.
  • Is it time to resurrect the weekly meetings?

Please feel free to leave your comments/suggestions here, I’ll leave comments open for 1 week until Thursday, July 16, 2020, 20:00 UTC, and then use the feedback to help us define our next steps.

#feature-notifications

#agenda

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 release? 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

WP Notify weekly meeting suspended, call for proposals for new meeting times or new meeting hosts.

At the present moment, due to various circumstances, the Monday 14:00 UTC time slot for the WP Notify weekly meeting has become problematic for me. This means it is becoming more and more difficult for me to attend, let alone host these meetings.

I am therefore putting these meetings on hold until we can agreed on either a new meeting time, or chose a new meeting host to drive the weekly meetings forward.

I will leave the post open for comment for the rest of the week, or until we can agree on a way forward.

#feature-notifications

#agenda

WP Notify weekly meeting for Monday 16 March 2020 cancelled

This post serves to notify everyone that the next WP Notify meeting, planned for today, Monday, March 16, 2020, 14:00 UTC has been cancelled.

We will continue with our planned weekly meetings next week on Monday, March 23, 2020, 14:00 UTC

#agenda, #feature-notifications