Proxy Access: @evarlese

Can @evarlese please be granted 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/ proxy access, this is for her sponsored work on WordCamps / Campus Connect.

SSHSSH Secure SHell - a protocol for securely connecting to a remote system in addition to or in place of a password. Key:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJ+F2x+cK6e+98TMRRp7A7QXLJUbD/UfdpxKGkllkUIw evarlese@chat.wordpress.org

Profile: https://profiles.wordpress.org/evarlese/

#prio1 #proxy

SMTP access for Mercantile.

Mercantile.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/ is hosted on WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ VIP. Currently it’s configured to use mercantile@wordpress.org as the sender email address.

That’s failing the SPF/DMARC rules, as WordPress.org doesn’t have WP.com VIP setup as valid sender. Additionally, WP.com VIP is not attempting to sign the emails either.

Previously, it looks like mercantile used xxx@mercantile.wordpress.org as the sender via sendgrid, which is no longer configured.

Outgoing emails from Mercantile are being rejected by anything that verifies DMARC rules, which includes emails to Automattic and WordPress.org (The notifications from WooCommerce to mercantile@ are rejected, and then the undeliverable email notification is delivered to mercantile@…).

The simplest method forward appears to be to re-enable a SMTP 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, and have it send via mail.wordpress.org

  • Can I get a SMTP account setup for mercantile?
  • If so; We can remove the unused TXT on mercantile.wordpress.org. and _dmarc.mercantile.wordpress.org
  • If not; We’ll need to look at getting sendgrid setup again, which requires a manual human account approval on their side as they need to verify identity and domain access.

#prio1 #mercantile #email

I’d like to request access…

I’d like to request access to Mission Control for @jeffpaul to assist with packaging WordPress releases, particularly for upcoming minor releases over the next two years.

With the expectation of fewer contributors available for this role during that time, I’m hoping to help fill the gap and ensure continuity in the release process.

Please let me know what information or steps you need from me to more formally request this access, to move forward with granting access, and to run through any training needed.

#prio1 #mc #releases

WordCamp IPv6 not using LE SSL certs.

This is causing old links to WordCamps to be inaccessible.

Looks like it needs the IPv6 listeners added in dehydrated-wc-certs.sh.

$ curl -Isv https://2019.atlanta.wordcamp.org/ -6 2>&1 | grep -E '(Connected|subject)'
* Connected to 2019.atlanta.wordcamp.org (2607:f978:5:8002::c68f:a46a) port 443 (#0)
*  subject: CN=wordcamp.org
*  subjectAltName does not match 2019.atlanta.wordcamp.org
* SSL: no alternative certificate subject name matches target host name '2019.atlanta.wordcamp.org'

verses:

$ curl -Isv https://2019.atlanta.wordcamp.org/ -4 2>&1 | grep -E '(Connected|subject)'
* Connected to 2019.atlanta.wordcamp.org (198.143.164.106) port 443 (#0)
*  subject: CN=atlanta.wordcamp.org
*  subjectAltName: host "2019.atlanta.wordcamp.org" matched cert's "2019.atlanta.wordcamp.org"

Props @desrosj for the notification

#prio1 #wordcamp #ipv6

Flawed 6.9 branch history for wordpress-develop Git mirrors

After the 6.9 RC1 release was successfully published, the 6.9 branch was created. However, there were a few missteps.

The first attempt to branch in [61215] copied trunk to the top level of the repository. This was reverted in [61218].

The second attempt to branch in [61219] copied the branches folder into branches/6.9. This was reverted in [61220] with a branch deletion.

The third attempt to branch in [61221] appeared to work successfully from an SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. perspective. On GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ however, the wordpress-develop mirror shows that the branch is “8697 commits ahead of and 4 commits behind trunk“.

This seems to be caused by the fact that the scripts responsible for syncing the SVN repository to the GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. mirrors did not perform a proper deletion of the branch in Git for the develop.git.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/ mirror. I’ve confirmed this by running the following on a develop.git.wordpress.org checkout: git rev-list --count HEAD..6.9 (prints 8697).

    Is it possible to correct this, perhaps by properly deleting the branch in Git and re-syncing the mirrors so that the 6.9 branch is created cleanly starting with [61221]? Another possible option could be to perform two manual commits to the Git mirror that takes the same steps that [61219-61220] did for SVN (deletes the branch, properly creates the branch).

    While this will likely result in changes to the commit hashes, this seems like a fair trade off considering it just happened for the sake of an accurate history in version control. Any actions taken should not impact the RC1 release in any way because that was published from [61213] in trunk, and the post release version bump commit ([61214]) occurred before the first branching attempt in [61215].

    Possibly relevant: The post-receive hook on develop.git.wordpress.org is as follows: git push --mirror github-wp-develop:WordPress/wordpress-develop.git (note the absence of a --force flag).

    If necessary, guidance can be published to the Make WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog for anyone who has synced their fork in the last 24 hours.

    #prio1

    Domain Redirect Request

    These two domains have just been registered: wordpresscampusconnect.org and wpcampusconnect.org. Please redirect them to the main event page https://events.wordpress.org/campusconnect .

    Thanks, team!
    #piro3 #domains

    Domain forwarding: `wordpress.{ong,ngo}` => foundation donations

    Can we please set up these two domains to redirect to https://wordpressfoundation.org/donate/?

    These are both on 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/ nameservers (The .ngo isn’t configured there, but it is upstream), and currently have no A records.

    Per MarkMonitor, this is required to be compliant with the domain registration rules.

    #prio1 #domains

    Email rejected as ‘high probability of spam’

    There’s been multiple reports over the last few weeks of emails from Gsuite being rejected due to the below details, I’ve been unable to verify it from a gsuite account.

    The response from the remote server was:
    554 5.7.1 High probability of spam

    Here’s one example of it, including the full email headers of the rejection:
    https://wordpress.slack.com/archives/C02QB8GMM/p1704295191477689

    #email #prio1

    bbPress Git mirroring to Github

    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

    Mailing lists subscription functions broken.

    As reported in #meta by @westonruter:

    It seems like the wp-svn and wp-trac mailing lists aren’t working for new subscriptions. I’ve also tried unsubscribing an old email but I was unsuccessful. (edited)

    I’ve verified the behaviour that new subscriptions appear not to generate any emails, either subscription confirmation or notifications from TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. (I sub’d a ...@hulse.com.au email to wp-trac, and verified with Google Email Log search)

    #prio2 #lists #email