A few references exist in our docs to the council-discuss mailing list and deliberately ask people to share to the mailing list, instead of the new Discourse category we use.
A few pages, like the Council ticket queues procedure page, mentions our old Mailman mailing list. We should do a close pass to see if we mention it anywhere else, and update it.
Creating a reusable attribute with all of our comms platforms in one file might be one way to reduce the burden of this maintenance too…
grep -rnw /path/to/council-docs/ -e "council-discuss"
People can share feedback and leave comments where the Fedora Council will see them
Metadata Update from @jflory7:
- Issue priority set to: waiting on assignee
- Issue tagged with: good first issue, help wanted, type - existing docs
Hello @jflory7! I would like to work on this issue, could you please tell me if the scope is to create a template with reusable attributes in council/ROOT/partials/ and then replace all the mailing-list appearances for the new one?
What would happen with cases like contact.adoc which explains redirects on engineering subthreads on this deprecated mailing list?
<img alt="contacting-fedora-council.png" src="/Fedora-Council/council-docs/issue/raw/files/d4d0a330ef2c865fd970d985f5642a96637cafd45b7364c21ab81f6db99d0825-contacting-fedora-council.png" />
Hi @josseline, thanks for your interest and patience here!
Yes, the scope is to create a reusable attribute, and then use the reusable attribute in all places where the mailing list is mentioned or linked.
For the contact.adoc page, that is a great point! For the most part, the copy-text can stay the same. We should replace "mailing list" with Discourse, and maybe add one new sentence to explain that we used to use mailing lists before we switched to Discourse.
Does this help explain the task at hand? Do you have enough info to feel confident in taking this ticket? Let me know, and I can assign it to you to work on. :smiley:
to comment on this ticket.