Re: Team directory docs

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEiEYb60m+ToMT+rY0OqLcH/ar8LYFAl9H6LIACgkQOqLcH/ar
8LZ2SQ//dR0k8kV5x5efNV88PjZM6UhVzUnQwaleBpjHY+FPO6MfuhVbODJpTxml
RERBuV2sqIgX6J/JF5kuQtTWH51ngwqdbBGFiLRZf/sAD+4MGGLhBuf+NLkrdKUU
XawHuchSzZntkepamLigxjiiKLuIRJ2toi4K5Lvy1xF0QHlAl3cPInAFq4Nl3zsp
vPsRi/O1F+DG3ChRyfZM/NV5lrWbcybKBn6EsFD2xHpkNGDmV8yj0x0mMbAAQc2Q
PerZmQEAL0A5+ZBlMWyf4WrhHy0EkWtJSl1s8bC0hwM3kFC4ftAPXHzgqfBs+K8I
3DhMustVxghL1HYPOaUzke+nOjZUw0rjPjN4FyBMujjWkI9L70DN7WCZ7plqivUf
GdDrdHwXMlwY5iZqSruv7cXwkxceYjENd6OSmzBVCMdqmVwsphJ6ynS8rvAuwH+8
3nT52BS+oZBDGVsOFF6/FnGOn+L1PHmmqYgkMDPAi9Plxm+pLEOVtTZqetoYN37n
QIAjweBrfvK9qYGENSvTji/dN//9NtzKr9CxRowP4Q9XNkTAA2nDaz5wpxGnuPiM
lo5cuLC4zJQAUCOxv2IlNh1U436jaUuvJvWIJc965BEJ34Fd1xlj6+sWrjMBKxz1
EV8ZR3AoK8JAGIYBxTXieZnhGUIJOvMR5wsNpdo0v3RcnFrqJbY=
=zReL
-----END PGP SIGNATURE-----
Hey Ben,

On 8/27/20 8:59 AM, Aleksandra Fedorova wrote:
> Hi, Ben,
>
> On Wed, Aug 26, 2020 at 7:43 PM Ben Cotton <bcotton@redhat.com> wrote:
>>
>> Hi all,
>>
>> I've published the first draft of the docs for the team directory in
>> an attempt to address the questions raised in last week's meeting:
>>
>> https://docs.fedoraproject.org/en-US/council/procedures/team_directory/
>
> Thank you for writing it.
>


Thanks for leading this work!


>> Does this make the expectations and purpose more clear?
>


I am looking for clarity on the deliverable. The expectation for
downstream teams is to create a file in a path like this:

`docs_repo_name/modules/ROOT/_partials/TEMPLATE_team_info.adoc`

And it has to be named exactly like that for it to be picked up?

If yes, this is a clever albeit non-obvious way of doing it. Additional
wording about the path requirement in a downstream docs repo clears that
up for me.

If no... need your help to explain another way. :)


> I would add a sentence to clarify that SIGs and Working Groups are
> also considered to be Teams in this doc. Because some people, like me,
> are used to thinking in terms of SIGs and may feel like the Team is
> something different.
>


+1. Team, SIGs, Working Groups, Objective leads, Sub-Projects... we are
a community of many names. :) With subtle, implicit meanings that are
not understood the same way by every person.

Better to make inclusion explicit so folks don't read this and then
self-select that they are not eligible to be listed.


--
Cheers,
Justin W. Flory (he/him)
https://jwf.io
TZ=America/New_York