Those do not work for people not using TB, while the reverse was
working for both.

The change was also hard to decode: it turns out it only changed to
links to point to the roadmap items instead of the issues.

it's just one possible solution on the deliverability issue, which
will probably require a TPA-RFC to officialize

We are using "Must have" instead of "Need to have" there, and it seems
like a more natural wording that we should also use here. It also
happens to reuse RFC-like vocabulary so it may be more explicit for
some people.

Those were duplicates and putting the former up in "Need to have"
seemed to imply the latter was promoted to that as well.

We still agree that the ENC is a priority, but we prefer avoiding the
confusion. See:

!16 (comment 2747932)

Working on and improving our Puppet environment while following best
practices [0] is currently blocking on our lack of an external node
classifier, or ENC. Adding this item as a priority on our roadmap will
resolve team#40358 and help advance team#29387

Deploying `hiera-enc` in itself should be fairly straightforward,
however since some nodes are assigned multiple roles, some of those
roles (eg. roles::fde) will have to be converted into profiles instead
and included from the role class. So a small amount of restructuring of
our roles manifests and current hiera data is to be expected.

If I can focus on this I don't expect it should take more than one
week's time (20h) to implement this fully.

[0] https://puppet.com/docs/puppet/7/the_roles_and_profiles_method.html

This is a nice to have, but it's definitely something we're still
interested in helping people with.

that way we don't have to rebuild our CA infrastructure immediately,
yet are still able to fix email reception from (say) state.gov