Email forwarding for git.wordpress.org

Would it be possible to add email forwarding for username@git.wordpress.org like we have for username@chat.wordpress.org for emails from 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/?

We currently request committers do it, but there’s a proposal to use Co-Authored-By: .....@git.wordpress.org which would benefit from being able to actually verify the email on GitHub.

In my opinion, this forwarder could be shared with the @chat forwarder, unless it’s super easy to split allowed senders by domain.

#prio3 #email #github

Add redirect for Font Collection JSON schema

I would like to request a new JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. schema file redirect, in line with theme.json and block.json, as discussed in this post.

As part of the new Font Library, there is a new JSON schema for defining font collections. There is more information in this PR.

The new redirect would be for:

https://schemas.wp.org/trunk/font-collection.json => https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/font-collection.json

This should be similar to how the theme.json and block.json redirects have been set up.

Thank you!

#prio1

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