Hi there! Can we please enable the imap php extension for wordcamp.org? Thanks!
Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts
Hey there, I want to ask if I can get more space on my sandbox
ocean90.dev.wordpress.orgtoo. On my sandbox we generate localized release packages and language packs which requires a checkout of i18n.svn.wordpress.org. The size of the project is currently 5.5GB.
For now 5GB more would be great.
Is there a chance I can get more space on my sandbox at
nbachiyski.dev.wordpress.org? We generate some POT files there and all of the project checkouts take a ton of space. I checked – it’s not temp files that will it up. Another 5-10GB would be great.
I’ve also seen it happen when connecting Jetpack to WPCOM, but that’s intermittent and I haven’t noticed a pattern yet.
We have use cases where API clients will need 75-100 posts. They could make multiple requests, but that would add additional overhead and slow things down on their end.
The nginx logs say,
upstream sent too big header while reading response header from upstream, and it sounds increasing the buffer sizes may be all that’s needed to fix it.
Can someone please deploy the following deploy wporg-web commits?
- 5981 – Allows for xx.wordpress.org/plugins/about/* rewrite rules to work on rosetta sites
- 5984 – Updates the stats cronjobs, removing those which no longer process data
A note on the cronjobs, `api-stats-cron` wasn’t renamed to better suit it’s purpose as there’s a non-versioned link pointing to it from /etc/cron.d/ so it was easier to just leave it be.
The additional autoupdate cronjobs are currently kicked off by the existing wp-url & plugin cronjobs. After deploy those scripts will run twice temporarily which won’t cause an issue.
Hi there! I’d like to request a few nginx changes on WordCamp.org if possible. In wordcamp-web.conf:
- Remove the second server block (for server_name wordcamp.org http://www.wordcamp.org)
- Remove the last two server blocks that listen on 443, but
- Move those SSL directives (listen, ssl, include conf.d/ssl-config, ssl_*) to the main server block (with server_name _)
- At this point wordcamp.org-common doesn’t seem to be used anymore, so we can nuke it
This is part of forcing https on WordCamp.org. In order to support old-format requests and hot-linking (photos, etc.) we will still be serving some traffic over port 80, but mostly it’s redirects via sunrise.php.
Can I please have commit access granted to buddypress.svn.wordpress.org for the username “hnla″?
Hugo will be focusing on BuddyPress’s theme compatibility with WordPress’s core themes in 2.3, and will be a permanent committer for all releases going forward in a similar capacity.
We’ve chatted about responsibilities, expectations, and security of commit access. His front-end abilities will really help BuddyPress fit more naturally and feel more turn-key, and the core team is excited for him to get started.
Emails being sent by WordPress.org & WordCamp WordPress instances are currently SPF softfail’ing, I suspect that’s what has caused Gmail to mark all contact requests from a WordCamp site to me (and the rest of the team) as spam.
This is happening as the bounce reply address is currently set to
firstname.lastname@example.org doesn’t accept w.org IP ranges as SPF permitted senders (as expected).
WordPress.org emails are DKIM signed (where as WordCamp ones are not), so i suspect that’s why they don’t get marked as spam.
Relevant part of a WordCamp email:
Received-SPF: softfail (google.com: domain of transitioning email@example.com does not designate 188.8.131.52 as permitted sender) client-ip=184.108.40.206;
spf=softfail (google.com: domain of transitioning firstname.lastname@example.org does not designate 220.127.116.11 as permitted sender) email@example.com
Received: from [18.104.22.168] (port=20977 helo=wordcamp1.lax.wordpress.org)
by marx.multipattern.com with esmtp (Exim 4.85)
for *brisbane wc email removed*; Sat, 04 Apr 2015 03:49:16 +0000
And that of a Make blog:
Received-SPF: softfail (google.com: domain of transitioning firstname.lastname@example.org does not designate 22.214.171.124 as permitted sender) client-ip=126.96.36.199;
spf=softfail (google.com: domain of transitioning email@example.com does not designate 188.8.131.52 as permitted sender) firstname.lastname@example.org;
Received: from mail.wordpress.org (localhost.localdomain [127.0.0.1])
by mail.wordpress.org (Postfix) with ESMTP id 3DAEA206CA9;
Fri, 27 Mar 2015 04:05:43 +0000 (UTC)