WP Notify meeting for 23 September 2019 cancelled.

Due to availability constraints, the WP Notify meeting for the 23rd of September 2019 is canceled.

We will pick up again on Monday the 30th of September 2019.

#feature-notifications

WP Notify Meeting Recap – September 16, 2019

This post summarises the weekly WP Notify chat meeting from 16 September 2019.

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

Project contributors document

@hrmervin has created a Project contributors document. If you haven’t already, and you’re keen to contribute to this project, please add your details there. Putting in things like areas of interest will help us determine who to ask for specific help. We’d also add that things like email address we consider non-compulsory, so you don’t have to put in your email.

Requirements gathering document

The requirements gathering document has been created, and is currently empty. Our goal is to have the bulk of the info we have so far in this document by the time of the next meeting. We’d like to get two other contributors on board (besides @psykro and @hrmervin) to help collate the information. If you’re keen to help, comment on this post. @dinhtungdu expressed interest in contributing to this document.

Project naming

We will be sticking with WP Notify for now, as it also ties into the namespace @schlessera proposed for 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. and should help avoiding confusion when discussing any specific parts of the project later on.

Meeting host availability and contingency plans

Right now this project has a bus factor of 1, in that if @psykro cannot post the agenda or host the first meeting, that weeks set of meetings are usually cancelled. It was suggested that this is acceptable as the nature of open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL..

Comments/suggestions are encouraged and welcome.

#feature-notifications, #summary

Summary of Core Privacy Office Hours, Sept. 18th 2019

Below is a summary of the discussion from this week’s CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Privacy chat (agenda, Slack Transcript).

Agenda Item: 5.3 Enhancements

The following tickets were flagged as enhancements for 5.3 privacy component;

  • #43890 – Allow Adminadmin (and super admin) to Skip e-mail confirmation for Export/Anonymization.
  • #44133 – Should the Data Export indicate when we have no information on the user.
  • #44135 – Have Erasure button workflow follow Export button workflow replacing with static link.
  • #44588 – Denote the Copy action is complete by updating the Copy button to state ‘Copied’.
  • #46303 – Update wp_privacy_send_personal_data_export_email to provide the same filters as _wp_privacy_send_erasure_fulfillment_notification.
  • #46895 – Personal Data Export Report: A way to display the group count.

#44133, #44135, #46303 and #46895 are all nearing completion but will need another set of eyes and review/testing before they can be marked commit.

#43890 and #44588 will need some work either a refresh or initial patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing..
#43890 needs discussion but @garrett-eclipse is leaning towards the use of checkboxes instead of dropdown.
#44588 has site health example to follow and just needs coding.

@pputzer graciously offered to review some of these tickets.

Agenda Item: Privacy Data Request Form

Feature Plugin Proposal – https://make.wordpress.org/core/2019/09/04/feature-plugin-proposal-privacy-data-request-form/

Not much feedback has been received yet so will let it gestate a little more. Initial feedback is pointing towards 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 territory over a core merge.

@audrasjb indicated it would be nice to test as a featured plugin so will determine how that can be accomplished.

Agenda Item: Consent and Logging Mechanism for User Privacy

Feature Plugin Discussion – https://make.wordpress.org/core/2019/08/07/feature-plugin-discussion-a-consent-and-logging-mechanism-for-user-privacy/

@garrett-eclipse asked if the effort needs to be setup like the WP-Notify #feature-notifications team and meetings.

Neither @idea15 nor @garrett-eclipse have capacity currently to spearhead the effort so decided to collect names of interested parties to create a working group. If anyone is interested in working on the consent/logging mechanism please feel free to comment on this thread or reach out in #core-privacy 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/..

#privacy

WP Notify weekly meeting agenda for 16 September 2019

Here is the agenda for the weekly meeting happening later today, Monday, September 16, 2019, 14:00 UTC and Monday, September 16, 2019, 22:00 UTC.

We were unable to meet last week, so this meeting will be follow up from the last meeting held on the 2nd of September, and will probably be a lot shorter.

  • Project contributors document
  • Follow up on project naming
  • Follow up on requirements gathering
  • Meeting host availability and contingency plans
  • Open Floor

If you have anything 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

WP Notify meeting for this week cancelled.

Due to circumstances out of my control, I was unable to post the agenda last week and I’m unable to run the early WP Notify meeting this week.

We will therefore skip this week’s meeting and pick things up next week.

Apologies to anyone for the inconvenience.

#feature-notifications

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

WP Notify weekly meeting agenda for 2 September 2019

Here is the agenda for the weekly meeting happening today, Monday, September 2, 2019, 14:00 UTC and Monday, September 2, 2019, 22:00 UTC. Please share any items you’d like to include in the comments below!

  • Opening and welcome
  • Decision on requirements gathering tools
  • Project naming
  • Requirements gathering planning
  • Open Floor

If you have anything 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

WP Notify Meeting Recap – August 26, 2019

The following is a summary of the kick off  WP Notify meetings that occurred on Monday, August 26, 2019. Weekly WP Notify are held every Monday at 14:00 UTC and 22:00 UTC respectively. A full transcript can be found here in the #feature-notifications channel in the Make WordPress Slack.

Attendees: @jon_bossenger, @juhise, @Hareesh, @nik, @richard_korthuis, @netpassprodsr, @jpry, @felipeelia, @sergey, @patpgogy, @timothybjacobs @hrmervin, @mnelson4, @justinahinon, @sergey, @garrett-eclipse, @xendin.unknown, @mikeschinkel

Recap

We kicked of both meetings with a review of the current project status, with a focus on the original tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. and the proposal post.

Next steps

  • Our proposed next step is to review the current data and start collecting all of the requirements.
  • This should also include any design requirements, and a data model that needs to be able to handle all of the use cases
  • Our ultimate first goal for the next few weeks or so would be a requirements document, including designs, and the data model

Requirements gathering tools

An important part of this process would be to agree on the tools we will use to gather and document the project requirements. Some form of collaborative documentation tool that doesn’t limit anyone based on operating system or location seems like the best choice. Options discussed include:

  • Google Docs
  • Microsoft offers a onedrive.live complement to Google Docs
  • 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//GitLab repo, with PR’s working as ways to accept items for the document
  • @netpassprodsr was curious as to whether 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/.’s document store be a practical option?
  • @hrmervin pointed out the using GitHub/GitLab might be limiting to non developer folks

There was also a lively discussion around the actual technical implementation, however it was agreed that it is too early to be discussing this.

Comments/suggestions are encouraged and welcome.

#feature-notifications, #summary

WP Notify Kick off meeting agenda for August 26th 2019

Here is the agenda for the kick off meeting happening next week, Monday, August 26, 2019, 14:00 UTC and Monday, August 26, 2019, 22:00 UTC. Please share any items you’d like to include in the comments below!

  • Opening and welcome
  • Review of current project status
  • Discussion of next steps
  • Open Floor

If you have anything 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

WP Notify Kick off meeting announcement

I’d like to announce the first meeting of the WP Notify project. The meeting will be held on Monday 26 August 2019 in the #feature-notifications channel.

In order to allow for multiple time zones, we’ll be having two meetings, one at 14:00 UTC, run by myself, and one at 22:00 UTC, run by @hrmervin. We’ll do our best to keep these two meeting times going forward.

I will post an agenda for the meeting closer to the time, and to allow folks to propose agenda items for the meeting.

#feature-notifications