Tag Archives: feature-notifications

Jonathan Bossenger 2:26 pm on December 2, 2020
Tags: feature-notifications,   

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

Jonathan Bossenger 3:00 pm on August 4, 2020
Tags: , feature-notifications,   

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

Jonathan Bossenger 8:33 am on July 9, 2020
Tags: , feature-notifications   

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

Jonathan Bossenger 12:20 pm on June 15, 2020
Tags: feature-notifications   

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

Jonathan Bossenger 8:58 am on March 23, 2020
Tags: , 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

Jonathan Bossenger 11:38 am on March 16, 2020
Tags: , feature-notifications   

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

Jonathan Bossenger 8:17 am on February 28, 2020
Tags: , feature-notifications   

WP Notify weekly meeting agenda for Monday 2 March 2020

This is the agenda for the next WP Notify feature project meeting, to be held today, Monday, March 2, 2020, 14:00 UTC.

Agenda

  • Opening and welcome
  • Reviewing work done on Current Status with a view to mark it complete
  • Reviewing and updating the requirements document: Project Goal
  • Reviewing and updating the requirements document: Overall Description
  • 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

Mervin Hernandez 7:04 am on February 27, 2020
Tags: , feature-notifications,   

WP Notify Meeting Recap – February 24 2020

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 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. features and limitations

Section 4. Project Goals

  • We continue refining the definitions of our 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 (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) 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 GutenbergGutenberg 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 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/. 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

#admin, #feature-notifications, #notifications

Jonathan Bossenger 9:12 am on February 24, 2020
Tags: , feature-notifications   

WP Notify weekly meeting agenda for Monday 24 February 2020

This is the agenda for the next WP Notify feature project meeting, to be held today, Monday, February 24, 2020, 14:00 UTC.

Agenda

  • Opening and welcome
  • Reviewing and updating the requirements document: Current Status
  • Reviewing and updating the requirements document: Project Goal
  • 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

Jonathan Bossenger 7:25 am on February 20, 2020
Tags: , feature-notifications,   

WP Notify Meeting Recap – February 03 2020

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

We opened by reviewing the Use Cases section. We moved an item related to which users 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 or theme notifications should be shown to, down to a later section in the document (Wish List Items), to be discussed at the relevant time.

@folletto noted that “here we are a bit playing a double role, use cases for users and use cases for developers. These luckily overlap a bit, and I think what we have is a good compromise”. @psykro left a comment that we might need to expand on use cases. We also had a brief discussion about the section on state changes. While the ultimate goal would be for WP Notify to replace those as well, this might not happen in our first release.

We reviewed the current status of the new Current Status section and had a discussion on the terminology related to the different types of notifications. @folletto suggested the following:

  • Notification = a notification hub, with maybe a dropdown or a container of some sort, that shows alerts across pages
  • On Page = a local notification, shown only on a specific page, and contextual to the page content

Finally we removed the admin_notices graphic from the Current Status section.

As always, we invite the community to share their feedback on any of these changes to the document, either here in the comments or on the document itself.

Next 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/. Meeting

📅 Monday, February 24 @ 14:00 UTC

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