Similar to https://make.wordpress.org/systems/2016/12/20/deploy-key-and-mirroring-for-github-repo/ can we please add the same thing for bbPress?
Repo to mirror into is https://github.com/bbpress/bbPress
Ref: https://meta.trac.wordpress.org/ticket/637
#prio2
I’ve been getting 403s when trying to access dotorg trac from my home network. Not having access has become a sizable pain over the past month—is there way we could get that whitelist updated please?
We’ve gotten a few reports lately of emails not making it to our HelpScout instance. Looking at the Spam Filters settings in cPanel shows one potential culprit:
The current Auto-Delete Threshold Score (4) is lower than the Spam Threshold Score (5). This will cause the system to automatically delete messages that it did not previously consider to be spam. We strongly recommend that you increase your Auto-Delete Threshold Score.
When we try to change the threshold number to something else, like 5 or 6, the UI shows that the change was successful. However, after refreshing the page, the UI once again shows that the threshold is still 4. I suspect that this number must be hard-coded in a config file somewhere.
We would like to get this number bumped up to 5 or 6.
Thanks.
An old bbPress.org forum user made a request to remove their old bbPress 1.x generation plugin.
Their request:
https://bbpress.org/forums/topic/how-to-close-old-bbp-plugins-svn-account/.
Plugin:
https://plugins-svn.bbpress.org/xili-new-post-notification/
Author:
https://bbpress.org/forums/profile/xiligroupdev/
This is my first time seeing anyone ask for this, so I’m not sure what’s achievable. If it’s possible and there’s a way to do it from my sandbox, I’m happy to help moderate these.
Currently WPF trademark emails are sent from trademarks@audrey.co, but that causes confusion since people expect them to come from the Foundation, and don’t know what Audrey is. @clickysteve would like to be able to send those emails from trademarks@wordpressfoundation.org instead, and Matt approved that.
I’m guessing that means we’ll need a full mailbox for trademarks@wordpressfoundation.org, and also a forward from that new mailbox to the existing trademarks@audrey.co address.
They use Zendesk, though, so I’m not sure exactly how that’s setup. It’s possible that it just spoofs the Sender header and relies on the SPF record to allow that, instead of authenticating via SMTP. It sounds like they just want it configured the same way that the other Zendesk accounts are.
Does that give you all the information you need to set it up?
cc @kraftbj
Please update the forward of slackinvitehelp@w….org to forum-password-resets@w…..org instead.
Thanks!
#prio2
Core needs some PHP7-syntax files for the tests folder (latest PHPUnit requires PHP7) to provide a compatibility layer which operates between PHP 5.2 and 7.2 with the default-installed PHPUnit
We’ve previously enabled PHP7 linting for meta.svn and plugins.svn, can we extend that linting to all svn’s?
I don’t expect that a PHP5-specific lint is really required by any of the remaining repo’s. bbPress/BuddyPress/core are going to need PHP7 files at some point, glotpress/w.org/code/etc would benefit from PHP7 syntax too.
ref: https://meta.trac.wordpress.org/ticket/3506 & https://core.trac.wordpress.org/ticket/43218
Transactional emails coming from the WordCamp.org web server are getting dinged on their SpamAssassin score for not having correct Reverse DNS.
https://mxtoolbox.com/SuperTool.aspx?action=ptr:198.143.164.106
Presumably, the PTR should point to wordcamp.org instead of wordpress.org. This is the SpamAssassin rule message:
0.8 RDNS_NONE Delivered to internal network by a host with no rDNS
0.8 is almost 20% of the default spam threshold of 5, which gives us a lot less of a buffer, and we believe it’s contributing to ongoing reports of messages being flagged as spam.
Could we get the PTR record amended to address this issue?
Related: https://make.wordpress.org/systems/2016/11/23/wordcamp-forwarder-emails-blocked/
With the new sandbox setup, we no longer have direct access to the error logs on production, which will make it difficult to learn about and reproduce errors in order to fix them.
I have a couple ideas about potential solutions, but I’d like to know if Systems has any thoughts or preferences.
1) Pipe errors into Slack, the same way that w.org does. This would require setting up object caching (to rate limit the API hits, per Slack’s ToS). IIRC, @kovshenin looked into this a few years ago, and determined that there was a non-trivial amount of code that would need to be refactored in order to make it work. Konstantin, do you remember the details there?
2) Setup a cron job on production to parse the raw error log on disk, reduce it to the relevant/limited entries, and push those to Slack.
3) Setup a cron job on production to copy the raw error logs from production to sandboxes every ~60 seconds. They’d need a different name than the sandbox error logs, so that we could have both.
@coreymckrill and I could write any scripts that are necessary, etc.
Do you see any problems with any of those, or have any other ideas or suggestions?
Hello, can you please setup proxy access for @nao and @chantalc? As polyglots mentors they’ll be helping out with managing rosetta sites and need access to the global.wordpress.org network.
For @nao you can use her a8c key, for @chantalc:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCwrC2ENYnWN3DKyMLRMjx2frHCAx5An+CDHQHPE7fdJux8F4pW7ACkioLBDK7gLRIf2OsszlN7ERMth8QiIP5hytKQJg+qoBUy4rSsvfMZx096EcybHP6yPc9BhvQJsEIy+PFFXeT9btcKHDpdBLrv6oiSo+WyW3YzBefuZoCygHXQwIYauNohsZKJkYX3g1PU4CyLny9TBFHPeizv9Endoreye5YJvGkPnsePGc14Ght8pmeGS/V1R6KCJ5r4AbEpZv1Wu6uPMEyKmKuNXj/Ur42qK6bN+Wb/L1HTcqENSsnbzR/bcRpU/tYOfzJYr/gMPlkLp7HEsiVh9oP6j5/98iywzQ8DNotnj2Hsv7DfS7EvvlMCI1Ih8l3MIzBfKFUEMlbQXrIsk4Y5vV9PP4NguYZReGo2kf7aDh5J9W36Oc43KIdmLectHjakrcMoHuFWA/d8xlhI2IQrequZjnrsLqY9YTCoSQ2zuDFHTRt/vaXDV/TvdCdIbTU0DIgsxHa/HEwp2PdcBopeL9MMU0mOAWfONtj1KjZ4iOzpsSz0K72iGxs6Di2WqS0TI7Yg3lkYPgkg3PVkey7HJ9PeKeJ3BxomNlkfU8EUMOPfWNUnAfK8Ou/AatqZSWr/9nvBNimEEaRqblRkdE4lgClOahrNuJBlZlv3y0xlPdg/o3Bycw== chantal@webpressed.nl
Thank you!
