Can we please add a Git post-update hook on meta.git.wordpress.org to push to git@github.com:WordPress/wordpress.org.git?
There exists an existing configuration for this for the develop.git repo: https://make.wordpress.org/systems/2016/12/20/deploy-key-and-mirroring-for-github-repo/
Either add the key directly in https://github.com/WordPress/wordpress.org/settings/keys or let me know and I’ll add it.
Back in October some rate limiting was added for certain traffic from Chinese sources, can we re-evaluate that rate limiting? Is it still needed? Can it be relaxed?
I realise the blocking was added due to significant abuse at the time with little other options, I’m just hopeful that that’s no longer the case.
There’s been several complains over the last few months, and as it turns out, there’s now some Chinese clones/proxies of WordPress.org to work around it.
Some relevant threads:
Over time, some erroneous WordPress releases or branches were accidentally created:
5.4-RC3-47470. This should have been a nightly bump instead.4.9.8-beta1-43498. This too should have been a nightly bump.4.2.26 branch on git://develop.git.wordpress.org/ mirror. This should have been a tag instead, and is already deleted on Core SVN, but still exists in the Git mirror and shows up on GitHub.Would it be possible to clean them up to avoid confusion?
When WordPress is in RC stage and a new version of Akismet is released, the svn:externals property has to be updated on the build repo (core.svn.wordpress.org).
For the upcoming WordPress 5.4 release this is already handled in https://core.trac.wordpress.org/ticket/49662#comment:2, so we’re good for now 🙂
Would it be possible for me (SergeyBiryukov) to get write access to core.svn.wordpress.org so I could help with these tasks in the future?
Can @dufresnesteven please have access to dotorg.trac.wordpress.org and read-only access to the corresponding svn. He’s helping to open source some of the WP and bbPress plugins that are tucked away in the dotorg repo.
As per #4974-meta for future Core builds the NodeJS/NPM versions will need bumping for proper Gutenberg building. The PR won’t be merged prior to the svn build servers being updated.
Gutenberg now requires Node.js 12.x and npm > 6.9.x and the “build server” requires updating to accommodate this.
At the time of creating this ticket:
* the latest Node.js LTS release is 12.14.1 https://nodejs.org/en/
* the latest npm release is 6.13.6 https://blog.npmjs.org/
See also: https://github.com/WordPress/gutenberg/pull/19680
For any questions, you’ll need to follow up with someone more involved with Gutenberg development, see the above Trac ticket or Gutenberg PR.
I’ve been noticing intermittently slow load times for wordcamp.org lately, and others have reported it as well.
Most of the times things are normal, but when it happens the page takes 10-30 seconds to load. While it’s going on, it seems like any page I visit is slow (e.g., 2020.asia.wordcamp.org/wp-admin and also 2019.seattle.wordcamp.org/contact). Then it resolves itself after a minute or so.
I noticed it this morning around 7:40am Pacific.
Because all requests are affected, it doesn’t feel like a slow MYSQL query. I’m wondering if it’s a DDoS that was automatically mitigated?
Do we have any logs that would give clues? I don’t see anything in the Slack channels. Or do you have any other ideas?
Can I please have commit access granted to bbpress.svn.wordpress.org for the WordPress.org username casiepa?
Pascal has been contributing to localizing bbPress and moderating the forums for several years. He’ll be helping the rest of the team maintain strings going forward.
(He has secure passwords on his WordPress.org, Slack, and GitHub accounts.)
Was @sippis‘ proxy access automatically blocked (maybe similar to a few people last month)?
We’ve been trying to get it working on his new machine (using his old key), but haven’t been able to. Here’s the output with ports 8080 and 8090; I think they’re both supposed to work, but not sure.
$ ssh -vvv -ND 8080 -p22 -i worgproxy_rsa sippis@proxy.wordpress.org
OpenSSH_7.9p1, LibreSSL 2.7.3
debug1: Reading configuration data /Users/sippis/.ssh/config
debug1: /Users/sippis/.ssh/config line 1: Applying options for proxy.wordpress.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 48: Applying options for *
debug1: Connecting to proxy.wordpress.org port 22.
debug1: Connection established.
debug1: identity file worgproxy_rsa type 0
debug1: identity file worgproxy_rsa-cert type -1
debug1: identity file /Users/sippis/.ssh/worgproxy_rsa type 0
debug1: identity file /Users/sippis/.ssh/worgproxy_rsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.9
ssh_exchange_identification: Connection closed by remote host$ ssh -vvv -ND 8090 -p22 -i worgproxy_rsa sippis@proxy.wordpress.org
OpenSSH_7.9p1, LibreSSL 2.7.3
debug1: Reading configuration data /Users/sippis/.ssh/config
debug1: /Users/sippis/.ssh/config line 1: Applying options for proxy.wordpress.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 48: Applying options for *
debug1: Connecting to proxy.wordpress.org port 22.
debug1: Connection established.
debug1: identity file worgproxy_rsa type 0
debug1: identity file worgproxy_rsa-cert type -1
debug1: identity file /Users/sippis/.ssh/worgproxy_rsa type 0
debug1: identity file /Users/sippis/.ssh/worgproxy_rsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.9
ssh_exchange_identification: read: Connection reset by peer
If you don’t see what’s wrong, could you replace his old public key with this new one?
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDRBalZIm7+6MjsAOdm9HVd7rOoy4Z1cyd8vpsGGfejo5qYfRszOHbkOSouXLIuRymm/+vSvmshFLh2N3FhGDMYE/F8rTPrBTTVCNh36aOutBqTPW3ynTHEq7scG9VRM2Ir7ongSjFKF+MIseycJ/6BmEVSwRxvXDV22iCWwZoJwB/qhr8g8nycV152aZPpLPTlWhjZVmZYJg1AhWYX7yc+D3ih06bkfDiKzr+VygIxrhg6R6+MiC4KN8KFuYvsqHSvlgS8CMqj8WJRmcfs0lBmwMSvixzchDfJDeXPqCu1P60wqGaDMvZ+p1/Sx7ttI08g9qsso2R2d1CnGku7FYjP sippis@Illusia.local
Can you add alexforcier as an editor to make.wordpress.org/updates? 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 🙂
