Add alexforcier to make/updates

Can you add alexforcier as an editor to He’s going to be posting the mobile update and needs publishing rights. Thanks!

Let me know if this isn’t the right place to request this as well 🙂

Tighten the config block rules.

Currently the 403 LB block for config is being too greedy. Can we please tighten it up to allow legitimate urls such as these through?,

Ref: #4776-meta



Remove old bbPress1 Search blocking

Currently requests to /support/search.php and /plugins/search.php are blocked for GoogleBot at the LB
Since neither of these URLs are in use today, can we remove these blocks?

Low-priority ref #4765-meta



Update some 302 redirects to 301s

Hi, as per #4630-meta can we update the following 302 redirects to 301’s?


Additional ones via #4075-meta


Here’s a diff that should apply to the web role:

Index: wporg-redirects.conf
--- wporg-redirects.conf	(revision 9066)
+++ wporg-redirects.conf	(working copy)
@@ -112 +112 @@
-	return 302;
+	return 301;
@@ -134 +134 @@
-	return 302;
+	return 301;
---	(revision 9066)
+++	(working copy)
@@ -36 +36 @@
-	rewrite ^/extend/?$ redirect;
+	rewrite ^/extend/?$ permanent;
@@ -88 +88 @@
-		rewrite ^ /support/ redirect;
+		rewrite ^ /support/ permanent;
@@ -91 +91 @@
-		rewrite ^ /support/ redirect;
+		rewrite ^ /support/ permanent;
@@ -99 +99 @@
-		rewrite ^/tags/(.*) /support/topic-tag/$1 redirect;
+		rewrite ^/tags/(.*) /support/topic-tag/$1/ permanent;


#4075-meta, #4630-meta

Redirect$ to Currently…

Redirect$ to

Currently if a user visits url into a browser, they hit a nginx 404, The nginx configuration isn’t setup to allow an index.php file to be served for that domain, so could we either have it redirect the root to or haveindex.php support enabled?



Blackberry Mobile App Trac being targeted for hacks

We’ve noticed an influx of new entries in the BlackBerry Trac that are hacky/spammy. Example:

Can we block this from happening for the existing bad accounts posting and also prevent it from happening further? The BlackBerry app is also dead (for several years now) so we can freeze the entire site or get rid of it entirely.

#mobile #prio3

Make GSOC trac read-only

It’s getting pentested:

Can we make it read-only, and if not, then maybe back it up and shut it down, or put it behind proxy auth or something? It’d be nice to preserve the content for history, but it’s probably not worth maintaining anymore, and definitely not worth cleaning up after pentesters.


Grant default theme commit to @ianbelanger

I need to get theme commit access for @ianbelanger to manage work on the default themes. Our most recent two theme committers have had to step back and they worked with him directly to do some training/hand off. I will make sure to share the following documentation with him as well:

  • Not a post, but the welcome/onboarding chat as has been passed down to me by @desrosj @mikeschroder and @aaroncampbell.

This is a #prio2, but would be great to get sorted for work on WP5.2.3 and WP5.3.

#commit #themes

Remove trailingslashit rule for theme directory URIs

Currently the nginx rules for the theme directory includes a similar to the following, can we please remove it, as it breaks access to URLs that shouldn’t have a trailing slash, such as
There should already be a handler in the PHP environment to add the trailing slash if it’s missing.

location /themes/ {
        # Add a trailing slash to all themes
        rewrite ^/themes/([^/]+)$ /themes/$1/ permanent;


plugins.svn is very slow

This is a known issue, but it seems like it’s gotten significantly worse in the past ~6 months, to the point where it’s disruptive to workflows, and would delay promptly recovering from bad deploys.

Here are some timings from my sandbox using, using themes.svn as a baseline.

/wp-content/themes ( 10 svn:externals to themes.svn )
$ time svnup

real 0m0.313s

wp-content/plugins ( 27 svn:externals to plugins.svn items, 1 to meta.svn )
$ time svnup

real 3m29.532s

$ time

real 4m44.074s

With a deploy taking almost 5 minutes, there’ll be a lot of extra/unnecessary downtime if we ever need to revert a bad commit and re-deploy.