Grant support theme commit to @netweb and @SergeyBiryukov

Both @netweb and @SergeyBiryukov have been assisting with improvements to the support forum theme since we switched to bbPress 2. We’re working on a new theme now and both should have commit to it (note that @netweb already has commit to the current theme, but not the new one).

Please grant meta svn commit to both of them for the new theme.

I believe @dd32 can handle this, but calling it #prio2 if he can’t.

Updates to rezbot

Our resident IRC logging bot, rezbot, gets a little crazy when there’s a net-split. We don’t need rezbot in any channels except #WordPress at this point. Can you please:

  1. Remove rezbot from all channels except #WordPress.
  2. Setup some kind of monitoring or resetting so that rezbot fully restarts after a net-split instead of joining/leaving channels repeatedly.

#prio3

Can s.w.org be upgraded to use http/2?

Alternatively, can we get gzip enabled?

#prio2

Hello, can someone please change…

Hello, can someone please change the redirect for *.trac.wordpress.org/logout from https://wordpress.org/support/bb-login.php?action=logout to https://login.wordpress.org/logout? Thanks!

Meta ticket: #2029-meta

#prio3 #trac

#2029-meta

Caching Tagregator requests on WordCamp.org

I’d like to get some form of network-layer caching of GET requests to *.wordcamp.org/wp-json/tagregator/*. Cached responses would need to expire after 30 seconds.

This is part of the solution to the problem we ran into at WCUS last year. Is that possible?

I’d also like to run a stress test to make sure we can handle the expected traffic for this year. Are you able to assist with that?

#prio2

security.wporg has an invalid SSL certificate

http://security.wordpress.org is just a redirect to https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/, but loading https://security.wordpress.org fails to redirect because of an invalid certificate.

#prio3

Visibility into WordCamp.org mail failures

Right now I’m blind to any errors that occur with messages sent from the WordCamp.org web server. This week there was a Core bug that resulted in many (most?) messages being rejected by the receiving MTA, but I didn’t know for several days, until the reports started coming in from users and the Core bug was discovered.

I think two things would help resolve this, but I’m open to whatever suggestions you have.

1) Set the Envelope-FROM to bounce@wordcamp.org instead of bounce@wordpress.org. I’ve already setup the address.
2) Grant read access to mail.* in the logs directory

Thanks!

#wordcamp.org #email #logs #prio3

There are no cache instructions…

There are no cache instructions on mp4s on the CDN, could you please add some on?

curl -I https://s.w.org/images/core/4.6/streamlined-updates.mp4
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Type: video/mp4
Date: Tue, 16 Aug 2016 13:13:27 GMT
Last-Modified: Tue, 16 Aug 2016 12:58:26 GMT
Server: nginx
X-Frame-Options: SAMEORIGIN
X-nc: MISS lax 186
Content-Length: 225101

Looks like webm has them:

curl -I https://s.w.org/images/core/4.6/streamlined-updates.webm
HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: max-age=315360000
Content-Type: video/webm
Date: Tue, 16 Aug 2016 13:14:11 GMT
Expires: Thu, 31 Dec 2037 23:55:55 GMT
Last-Modified: Tue, 16 Aug 2016 12:58:26 GMT
Server: nginx
X-Frame-Options: SAMEORIGIN
X-nc: HIT lax 186
Content-Length: 449672

For 4.6 we don’t use ogv but 4.3 had one:

curl -I https://s.w.org/images/core/4.3/formatting.ogv
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Type: application/octet-stream
Date: Tue, 16 Aug 2016 13:09:55 GMT
Last-Modified: Wed, 29 Jul 2015 16:49:59 GMT
Server: nginx
X-Frame-Options: SAMEORIGIN
X-nc: MISS lax 186
Content-Length: 1939540

The content type should probably be video/ogg.

#prio3

Release of WordPress 4.6 on August 16th at 19:00 UTC

Just a heads up that we’re planning to release a new major release today, August 16th at 19:00 UTC.

Low prio request: Can we…

Low prio request: Can we prevent direct access to PHP files in the wp-content directory?

I originally noticed this for wp-themes.com. @dd32 suggested to return “a 403 for ^http://wp-themes.com/wp-content/(.+).php$ but the rest of wordpress.org could benefit of the same restriction.

#prio3