Could I get a sandbox again, for making changes to make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//cli (e.g. #6394)?
Thanks for the consideration!
It appears that the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party checksum download endpoint has had some rate limiting added, which is affecting clients of that endpoint.
See https://github.com/wp-cli/checksum-command/issues/91
See https://wordpress.slack.com/archives/C02QB8GMM/p1659451832035669
The legitimate uses of the endpoint do result in the checksums of all plugins on a site being requested in a short period of time. I’m unsure if clients avoid requesting 404 urls or only 200’s.
Helpscout cannot email to wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ from wordpress.org
Occasionally there’s the need for Helpscout inboxes, which are @wordpress.org inboxes to send emails to other @wordpress.org email addresses, these might be just CC’ing a given WordPress.org user, or forwarding an email to a different Helpscout instance.
Unfortunately, it appears that this is currently blocked by the WordPress.org SMTP servers. Can we allow HelpScout to send-as wordpress.org to WordPress.org?
The relevant part from the bounce is: (noting, I’ve replaced the inboxes for spam purposes, dpo is the sender, and recipient was security in this case)
Final-Recipient: rfc822;mailbox-here@wordpresss.org Action: failed Status: 5.7.1 (delivery not authorized) Remote-MTA: dns;mail.wordpress.org (198.143.164.147) Diagnostic-Code: smtp;554 5.7.1 <helpscout-inbox@wordpress.org>: Sender address rejected: Access denied X-PowerMTA-BounceCategory: invalid-sender
The bounce email is available here: https://secure.helpscout.net/conversation/1966354976/301771 and stored in the private PasteBin as #184485 with ID of 2d0a5. (Alternatively, ask a Neso team member for a copy of the email if you’re unable to locate that and unable to locate the HS credentials)
Can we please have an email forwarder from hosting@wordpress.org to hosting@wordpress.helpscoutapp.com
Ref: https://meta.trac.wordpress.org/ticket/6226
Can we please have an email forwarder set up from reports@wordpress.org to wp-project-reports@mu.helpscoutapp.com.
This is for some upcoming code-of-conduct stuff. I’ve set up a mailbox on the helpscout side (this is in the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more./Foundation HS instance).
cc @angelasjin.
Following on from https://make.wordpress.org/systems/2022/04/11/commit-for-images-core-emoji-could-i/ can we please add kraftbj to the dotorg tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. allowed users list?
Thanks in advance.
Commit for images/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./emoji
Could I get commit access for dotorg’s image/core/emoji directory to add me to the folks who can upload new emoji assets?
When twemoji updates to new versions, in addition to the Core patch (e.g. #55395-core ), we need to upload to assets for the CDN to distribute.
We can continue to do the past way of bugging folks with commit access, but I’ll be joining as an Emoji component maintainer and I already have partial commit access elsewhere.
cc: @desrosj
Per https://meta.trac.wordpress.org/ticket/6168 some codex pages have a cached header HTML + CSS which are incompatible with one another, causing a display mismatch.
While we’re migrating away from the Codex, it appears likely to remain for some time.
Can we please
1. Flush the codex cache
2. Lower the cache TTL, perhaps to a week or two, to avoid the need for future system requests?
The developer.wordpress.org host configuration doesn’t support sub-sites right now, this is due to nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. rules such as rewrite ^/(wp-(admin|includes)/.*) /wordpress/$1 break; rather than the sub-site variant of rewrite ^/([_0-9a-zA-Z-]+/)?(wp-(admin|includes)/.*) /wordpress/$2 break;.
While the existing developer.wordpress.org configuration could be updated to match that of the make.wordpress.org configuration, we can just combine them, serving both networks from the existing make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ configuration, with the addition of the developer.wordpress.org domain name in the server_name field. There’s nothing special/unique in either configuration, other than generic WordPress MultisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network. rules.
A working sub-site configuration would return 200 for this request:
$ curl -sI https://developer.wordpress.org/testing-subsites/wp-includes/css/dashicons.min.css HTTP/2 404 ..
