Requesting a sandbox for @goldsounds,…

Requesting a sandbox for @goldsounds, so he can help debug a Jetpack sync issue. Meta commit access is not needed. You can use his Automattic ssh key.

Deploy Key and Mirroring for GitHub Repo

Ref: https://meta.trac.wordpress.org/ticket/633

git.develop is being mirrored by GitHub, but their mirror process only checks every few hours, which is way too slow to be useful. Instead, we want to replace it with a post-receive push.

To do that, we need a deploy key created, per GitHub’s docs.

The private key needs to live on the git server, either in ssh agent, or with a reference in the ssh config file:

Host github.com
    IdentityFile ~/.ssh/id_rsa_github

The push command then needs to be added to the post-receive script.

git push -f --mirror git@github.com:WordPress/wordpress-develop.git

I’d like to get this done quickly, so we can get GitHub integrations up and running. Thanks!

#prio1

Proxy access for Kim Hustad

Hi, can you please setup proxy access for @kimhustad? She’ll be helping out with bookkeeping and will need access to the WordCamp.org budgeting tools.

Her public key is:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCY5whCd2F7ZDsomK6yFJO4hlGo3iqxVJM/k2MVP31oXlusv2/KVFAtkawNKLaGk6SsSst2UZTTxJF76w4gQJiDSVlGZk54E5p+VR3jIv5api4LqbYwL7ibb12aaaq1a9l1qrW0faMIdJGZNXjpncPnjGSBbGM+gXXpV91s1LC/BzkL2dbog1AzwVW5aoplWJAj473klpSPzTnHK+/KAHYHmLN/v5P3XdRuC7LzdWSphaT7L413pe+BrjHSxlgZWHbFscMyv2VAjNwE6e3XJqwhC6XVz/IOtkmTQK/gqWgxA4W8nIW3FjmVmW4VbSEOH41FRergEJlH6K4SfC3ir2+9 automatticaccounting@Automattics-MacBook-Pro.local

Thanks 🙂

cc @juliaullrich

#prio2

SSL for wp.org

As wp.org is now a WordPress.org domain, can we please get SSL enabled for it?

ref https://wordpress.slack.com/archives/meta/p1480801420000002 / https://wordpress.slack.com/archives/meta/p1480909161000077

#prio3

Can we please disable the…

Can we please disable the ticket update module on plugins.trac?

Since plugins.trac is mostly unusable, many plugin authors use Github and sync over changes. Unfortunately many of these include commit messages which includes “closes #123” or “fixes #123” which ends up with many people subscribed to tickets on trac, for example:
https://plugins.trac.wordpress.org/ticket/1 & https://plugins.trac.wordpress.org/ticket/2

It looks like we can simply disable the Commit Ticket Updater trac module?

#prio2

Missing `Content-MD5` header for core downloads

$ curl -I https://downloads.wordpress.org/release/wordpress-4.6.1.zip
HTTP/1.1 200 OK
Server: nginx
Date: Thu, 24 Nov 2016 09:33:22 GMT
Content-Type: application/zip
Content-Length: 8650308
Connection: keep-alive
Cache-control: private
Content-Disposition: attachment; filename=wordpress-4.6.1.zip
Last-Modified: Wed, 07 Sep 2016 14:59:22 GMT
X-Frame-Options: SAMEORIGIN
X-nc: HIT lax 189
Accept-Ranges: bytes

The header was added 5 years ago in [dotorg5308]. [dotorg7078] added X-Accel-Redirect which may be the reason for the missing header now. To quote @dd32:

IIRC even when sent by PHP, when it’s a X-Accel-Redirect it needs to be whitelisted in nginx.. I think we’ve enabled it and never pushed a change into nginx..

#prio2

ERR_SPDY_PROTOCOL_ERROR on certain paged plugin searches

As reported in https://meta.trac.wordpress.org/ticket/1860 W.org is responding incorrectly for certain requests, I’m unsure what the cause is and whether it’s a nginx config or not.

Here’s a cURL command to reproduce:

$ curl -v 'https://wordpress.org/plugins/search.php?page=2&q=plugin'
*   Trying 66.155.40.250...
* Connected to wordpress.org (127.0.0.1) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.wordpress.org
* Server certificate: Go Daddy Secure Certificate Authority - G2
* Server certificate: Go Daddy Root Certificate Authority - G2
> GET /plugins/search.php?page=2&q=plugin HTTP/1.1
> Host: wordpress.org
> User-Agent: curl/7.43.0
> Accept: */*
>
* Empty reply from server
* Connection #0 to host wordpress.org left intact
curl: (52) Empty reply from server

This is lowest of the low priorities, more as a FYI. The plugin directory will hopefully retire soon and this isn’t reproducible against the new directory, most likely due to the change from query variables to rewrites. If this is a wontfix I don’t think anyone will mind.

#prio3

Can’t delete forwarders in WordCamp.org cPanel

Recently we started getting errors when trying to delete forwarders. For example:

Unable to locate the forwarder “waukesha@wordcamp.org” for account “example@gmail.com” on domain “gmail.com”.

We can still add them, though.

I tried manually edited /etc/valiases/wordcamp.org, but it just got overwritten a few minutes later with same contents it had before, so it seems like it’s not the canonical source for that data.

You can use the iandunntest2 forwarder for waukesha@wordcamp.org as a test.

#prio3

Can I please have commit…

Can I please have commit access granted to buddypress.svn.wordpress.org for the following WordPress.org usernames:

  • slaffik
  • netweb
  • offereins

Slaffik is our 2.8 release lead. Netweb will be helping maintain BuddyPress’s build-tools. Offereins will be helping with some feature development.

Boone had the roles & responsibilities talk with them, and confirmed secure passwords for all.

The entire core team is pumped for our new recruits to get started! <3

#buddypress, #commit, #prio2

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.