It looks like WordPress.org doesn’t use ALPN for negotiating the connection encryption. Chrome is dropping support for NPN next month, so it’d be nice if we could upgrade before then.
Recent Updates Toggle Comment Threads | Keyboard Shortcuts
The Community Team is discussing e-mail options for WordCamp organizing teams, and one of the potential solutions is to allow SMTP traffic from outside the network. If that was done, then the teams could send out mail from firstname.lastname@example.org accounts, rather than having to setup a Gmail account that messages get forwarded to, and sending mail from that.
I don’t know why SMTP is currently blocked, though, so I wanted to find out if allowing that traffic is an option or not.
Hello! Can I please have the mysqldump cli tool installed on my sandbox?
I’d like to dump some data from translate.w.org so I can do some testing regarding performance.
“Some data” are following tables:
And performance is regards this issue: https://github.com/GlotPress/GlotPress-WP/issues/376. I want to find out which current or new indexes will help to lower the execution time of queries.
Can I please get svn commit access to meta.svn.wordpress.org. Mostly I need commit to https://meta.svn.wordpress.org/sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory if you want to make it specific.
#1641meta has pointed out that plugins.trac.wordpress.org is missing ~8400 changesets.
Can we do something to import those missing changesets? As we’re running Trac with explicit synchronization, I think it might just be a case of running
trac-admin changeset addedfor each of the missing revisions.
Removing the PHP 5.4 plugin directory linting
The plugin directory has linting against PHP 5.4 for quite some time now. It used to be a feature to prevent accidental bad commits, but today it’s now regarded by many as a bug.
We need to do one or more of the following:
- Upgrade the PHP linting to PHP-latest-stable (7.0)
- Upgrade the PHP linting to PHP 5.6 with a plan to move to PHP 7.0 (latest stable) and keep up with future releases
- Switch PHP linting to being a warning instead of a block
- Remove the linting all together
Simply upgrading the linting to PHP 5.6 only kicks the can down the road, and still blocks people from using PHP 7 syntaxes in plugins (which is totally okay, if the plugin specifies that as a requirement).
Removing the linting seems like a bad idea, as I believe authors should still be notified they’re committing code that may not be compatible (Unfortunately we currently don’t do php fatal error prevention checks on plugin upgrades, so I’d like to retain it to prevent an unexpected WSOD).
So, I personally feel we should leave the linting at PHP 5.4 (which is what the majority of WordPress sites run today) and make it a warning, not a block.
In order to warn instead of outright blocking, the linting needs to be moved from the
pre-commithook to the
post-commithook and the script exiting with a error-level code, STDERR will then be sent to the client after the commit is made.
Hi, I need someone to handle the nginx part for #1352 (Switch translate.wordpress.org to the plugin version of GlotPress).
Step 1: Disable the
wporg-translate.wordpress.orgconfig on my (ocean90) sandbox.
Step 2: Remove the config from production servers.
Step 3: If possible, flush the cache for the keys
I’d like to start with step 1 so I can do further testing before we continue with step 2 and 3.
Can I get admin or editor access to make.wordpress.org? I need to update the widget on the landing page for Mobile and don’t have rights to that site.