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

This was discussed during today's checkin and mostly changed to
accomodate people on the west coast, especially now that we don't have
people on the team in Europe checking in on a regular basis during meetings.

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)

Add a new 2021 roadmap item for Puppet

Closes team#40358

See merge request !16

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

Following a discussion during the last S9 meeting, I was asked to draft
ideas for a workflow for editing the new Lektor blog that avoids using
the command-line and the `git` command.

Document the anticensorship team services

Closes tpo/anti-censorship/team#4

See merge request !15