Well, like everything committer related, it's in the committer's guide https://docs.freebsd.org/en/articles/committers-guide/#ports-exp-run, but I don't see what would break with this change.

I don't think this should break too many things.

Approved, with a small change.

This looks good to me.

This looks good, could my comments be addressed ?

It feels ok to me, yes.
Maybe there is a need to add some autotools env variables too, or maybe those should go in Templates/config.site.

Using must is a no.
This rule should not be absolute.
You can advise people to not put a variable, but variables may need to happen from time to time.
The WWW variable is there so make(1) can create things out of it.
The ports tree is to be used by developpers, not end users. End users have packages and should not have to interact with the ports tree ever.
If a developper needs to know the actual value, they can run make -V WWW, we could even add a few targets, like make open-www that would do stuff like xdg-open "${WWW}".

As the sentence says "should", it's an advice, which means, it's not enforcable, so, it's just more text that do not really add any no value.

In D30315#1225899, @mat wrote:

Also, ansible ahould probably not be using USE_PYTHON=concurrent

I'd rather we used ?= here.

With the s/SUDO_DEPEND/SUDO_DEPENDS/ that Mateusz talked about, feel free to push it.