Privacy Office Hour Notes: January 23, 2019

The following is a summary of the weekly Privacy office hours that occurred on January 23, 2019. Weekly privacy office hours are held every Wednesday at 19:00 UTC. A full transcript can be found here in the #core-privacy room in the Make WordPress Slack.

Attendees: @desrosj, @garrett-eclipse, @postphotos, @riankinney, @birgire.

Here are the highlights of the meeting:

WordPress 5.1 Related Items

The full WordPress 5.1 release schedule can be found here

  • At the time of the meeting, 13 privacy component or focus tickets had been committed for release in 5.1 on February 21, 2019. Thanks to everyone that contributed to the final push to land additional tickets in 5.1.
  • Moving forwards, only tickets addressing bugs or regressions only in trunk will be considered.
  • With 5.1 closed for Privacy items, attention should shift to the Privacy component and focus tickets in the 5.2 milestone. There are currently 8 and all but 1 has an owner assigned. More can be added if they are ready.
  • Moving forward, all Privacy tickets should have an owner when being added to a numbered milestone (not Future Release). This will help ensure Privacy tickets are not punted release to release and contributors have a clearer focus.

New Trac Keywords

Two new privacy-related keywords can be found in the Trac keyword dropdown field (see Meta-3896). These keywords (needs-privacy-review, has-privacy-review) need to be added and detailed in two locations to encourage proper use:

  1. The privacy component page on Make WordPress.
  2. The Trac Workflow Keywords page in the WordPress Core Handbook.

After some wordsmith work from attendees, the following descriptions are being proposed:

  • needs-privacy-review: Input is needed from the core privacy team with regards to the privacy implications of the suggested changes.
  • has-privacy-review: Input has been given from the core privacy team reviewing the privacy implications of the suggested changes.

Barring any feedback in the #core-privacy room on the Make WordPress Slack or in the comments below, these keywords and descriptions will be added to those locations.

Open Floor

  • #45999 was re-raised by @garrett-eclipse for feedback. The main concern expressed was “Is removing these pointers in 5.2 too soon?” Some research needs to be done to see what Core has deemed an acceptable timeline for removal in the past.
  • As items on the V2 start to be tackled, work for this should be done using GitHub.
  • Smaller, single feature focused plugins is preferred. But, there will be some features that are too closely related to build in isolation.
  • The pre-existing WordPress Privacy group on GitHub should also be utilized.

The next weekly privacy office hours will be held on Wednesday, January 30, 2019, at 19:00 UTC in the #core-privacy room in the Make WordPress Slack.