Core Privacy Office Hour Summary – 14 November

Moving forward, the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Privacy Office Hour will be held at 19:00 UTC.

Below is a summary of the discussion from this week’s #core-privacy chat. You can read the chat in its entirety in Slack.

The agenda for the chat is available here.

NTIA Comments (Pre-chat)

A few noteworthy comments on the NTIA RFC for the Proposed United States Privacy Approach:

Meeting Time

With daylight saving time changes behind us for now, a new time for the weekly office hours meeting was discussed. The top voted for time slot was 19:00 UTC with 10 votes. There was a tie for second with 17:00 and 18:00 UTC receiving 8 votes each. No time slot will work for everyone, so the 19:00 UTC time slot as chosen to maximize attendance. The hope is that if agendas and summaries continue to be consistently posted, the component can gain more momentum at this new time with higher attendance.

As always, the 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/. channel (#core-privacy) is always open for discussions! And catching up asynchronously is always welcome.

WordPress 5.0

WordPress 5 release is presently scheduled for Tuesday, November 27 – that’s less than two weeks away. A new beta released a day or so ago – great time to try out the new block editor and new release and double check privacy policy editing especially. Noteworthy patches: https://core.trac.wordpress.org/ticket/45151 and https://github.com/WordPress/gutenberg/pull/11604 and https://core.trac.wordpress.org/ticket/45057

We also discussed the use of Google Fonts in Gutenberg – see https://github.com/WordPress/gutenberg/issues/11648 – the issue title may not be accurate, but the issue does bear further investigation. @allendav and @desrosj will look at it and others are welcome to as well. @desrosj summed up a great approach for this and similar situations: “Not arguing to leave it in, but to change it, we need to have a clear suggestion for how to proceed, as well as a description of why it needs to be changed so others can understand. This seems like a larger issue though because [other items used by core] are loaded from Google.”
@desrosj also committed to “work on coming up with a list of all externally loaded resources and circle back with Allen on it. We’ll come up with a plan forward, and try to clarify why/if it must be changed.”

Needs-Privacy-Review

@garrett-eclipse ‘s ticket is waiting for commit to add the new tags – see https://meta.trac.wordpress.org/ticket/3896

Update on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ page 3rd party scripts

@allendav got the green light from @Matt to remove the Quantcast scripts as well as replace the Twitter and Facebook script-powered sharing buttons with simple links. This should improve end-user privacy as well as decrease page load times. See https://meta.trac.wordpress.org/ticket/3655#comment:25

Next Office Hour

The next core privacy office hour will be Wednesday, November 21st, 2018 at 1900 UTC in #core-privacy. Expect an agenda to be posted on Monday, November 19th. PingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @allendav @idea15 or @desrosj if you’d like to add an item to the agenda, or feel free to add it yourself at https://docs.google.com/document/d/1oQnV7L1KVeFhLCLRzJZ6cbntLmIxqAtWZGa7EAs9eQE/edit

#core-privacy
#privacy