Contact info: Update platforms & methods to contact the Council

This commit updates information about how to contact the Fedora Council
and the best places to get in touch. This updates information about IRC
and mailing lists, and replaces them either with platform-agnostic
language or Matrix/Discourse specifically, where applicable.

This commit builds on what @mattdm already put together in January 2022
in PR #138. There is not a significant change to what was already voted
on and decided previously, but I did reorganize some of the content on
the "Contact" page in an attempt to enhance the page structure already
laid out. It includes @bcotton's feedback asked for previously.

These changes are a year old and do not include changes to the charter
other than links to the Council meetings wiki page and changing the
Discourse link from the old category to the Council tag. I intend to
merge this on commit, on the conditional affirmation by the Council has
approved this change during our February 2023 face-to-face meeting in
Frankfurt, Germany.

ref: Fedora-Council/council-docs#138

Signed-off-by: Justin W. Flory (he/him) <jwf@redhat.com>

council/modules/ROOT/pages/contact.adoc

@@ -1,22 +1,39 @@
 = Contacting the Fedora Council
 
-The Fedora Council uses two mailing lists.
+The Fedora Council uses three platforms for communications, one for asynchronous, one for asynchronous, and one for decision-making.
+Anyone registered with an account in the https://accounts.fedoraproject.org[Fedora Account System] (FAS) can log in with their account to participate in either platform.
 
-https://discussion.fedoraproject.org/c/project/council-discuss/60[*Council Discussion*] is a public category on Fedora Discussion.
-This is the main discussion point for the Fedora Council,
-and the goal of the is to either reach a decision,
-or to delegate the thread to a more appropriate location.
 
-https://lists.fedoraproject.org/admin/lists/council-private@lists.fedoraproject.org/[*council-private*] is a private list. Its membership is restricted to the current Council members,
-and it is not archived.
+[[discussion]]
+== Fedora Discussion (asynchronous)
+
+The https://discussion.fedoraproject.org/tag/council[*#council tag*] on https://discussion.fedoraproject.org/[Fedora Discussion] is the primary space for Fedora Council conversations.
+We use this for discussion within the Council as a team, and it is also the best place for any community member to engage in or start a conversation with us.
+
+[[discussion-private]]
+=== Private mailing list
+
+We also have a private mailing list: https://lists.fedoraproject.org/admin/lists/council-private@lists.fedoraproject.org/[*council-private*].
+Its membership is restricted to the current Council members and discussions there are not archived.
 This list is only used for topics that cannot be discussed on the public forum.
+We use it as little as possible.
 
-Council members are also often present on the https://matrix.to/#/#council:fedoraproject.org[*#council*] channel on chat.fedoraproject.org
-(bridged to the *#fedora-council* IRC channel on https://libera.chat/[Libera.Chat]).
 
-If you have an issue to be worked on by the Council you can also open a
-ticket on the https://pagure.io/Fedora-Council/tickets[Council Pagure
-instance]. This is a public issue tracker. However, if you have a
-particularly privacy- or security-sensitive issue, you can check the
-*Private* box when you create the ticket. If an issue is not sensitive
-the discussion should be in the open, in the public Pagure instance or Discussion.
+[[chat]]
+== Fedora Chat (synchronous)
+
+Council members are also often present on the https://matrix.to/#/#council:fedoraproject.org[*#council:fedoraproject.org* Matrix room] on https://chat.fedoraproject.org[chat.fedoraproject.org] (bridged to the *#fedora-council* IRC channel on https://libera.chat/[Libera.Chat]).
+
+
+[[decisions]]
+== Pagure (decision-making)
+
+It is better to start with an asynchronous conversation, described above.
+
+When you have a specific proposal for the Council to make a decision, open a ticket on the https://pagure.io/Fedora-Council/tickets[*Council Pagure instance*].
+This is a public issue tracker.
+However, if you have a privacy- or security-sensitive issue, check the *Private* box when you create the ticket.
+If an issue is not sensitive, the discussion should open and public.
+
+Note that ticket comments should be kept to a minimum.
+Discussion should be at https://discussion.fedoraproject.org/tag/council[#council] and the ticket used to record procedural actions like votes and approved resolutions.

council/modules/ROOT/pages/fpl.adoc

@@ -1,4 +1,6 @@
 = The Fedora Project Leader
+// Remember the one-sentence-per-line convention when editing this page.
+// https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line
 
 The _Fedora Project Leader_ (or _FPL_) is ultimately accountable for everything that happens within Fedora and in particular is responsible for maintaining Red Hat's relationship with Fedora and vice versa.
 They are Fedora's President, CEO, Chair, Fearless Leader, whatever-you-want-to-call-it.
@@ -6,19 +8,16 @@ However the project leader is not a dictator, benevolent or otherwise.
 The FPL chairs the Fedora xref:index.adoc[Council].
 
 image::mattdm-2014-fedora10y-thumb.jpg[float="right",50%,link="https://fedoraproject.org/w/uploads/e/e8/Mattdm-2014-fedora10y-small.jpg"]
-https://fedoraproject.org/wiki/User:mattdm[Matthew Miller] is the current Fedora Project Leader.
-He led the Fedora.next initiative for a strategic approach to Fedora's second decade,
-as well as the transition from the Fedora Board to the current Council governance model.
-Matthew created the BU Linux distribution for Boston University in 1999 and maintained that through 2008,
-when he moved to the Harvard School of Engineering and Applied Sciences to work on high performance computing and this up-and-coming “cloud” thing.
-He has been at Red Hat since 2012, first working on Fedora Cloud and becoming FPL in June, 2014.
 
-Contact Matthew as `mattdm` on Libera.Chat IRC,
-as https://twitter.com/mattdm[@mattdm] on Twitter, or
-on the
-https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/[Council-Discuss]
-mailing list.
+https://mattdm.org[Matthew Miller] is the current Fedora Project Leader.
+He led the Fedora.next initiative for a strategic approach to Fedora's second decade, as well as the transition from the Fedora Board to the current Council governance model.
+Matthew created the BU Linux distribution for Boston University in 1999 and maintained that through 2008, when he moved to the Harvard School of Engineering and Applied Sciences to work on high performance computing and this up-and-coming “cloud” thing.
+He has been at Red Hat since 2012, first working on Fedora Cloud and becoming FPL in June 2014.
 
+Contact Matthew as https://matrix.to/#/@mattdm:fedora.im[@mattdm:fedora.im] on Matrix, https://twitter.com/mattdm[@mattdm] on Twitter, or https://discussion.fedoraproject.org/u/mattdm/[mattdm] on https://discussion.fedoraproject.org/[Fedora Discussion].
+
+
+[[previous]]
 == Previous Fedora Project Leaders
 
 https://fedoraproject.org/wiki/User:Rbergero[Robyn Bergeron]::
@@ -41,4 +40,3 @@ Cristian Gafton::
 
 Michael Johnson::
   July 2003 – January 2004 (Fedora Core 1)
-

council/modules/ROOT/pages/index.adoc

@@ -200,9 +200,9 @@ of the Council.
 
 === Meetings
 
-The Fedora Council is not driven by meetings or by tickets, but does hold regular public meetings (via a chat system or video call).
+The Fedora Council is not driven by meetings or by tickets, but does hold https://fedoraproject.org/wiki/Council_Meetings[regular public meetings] (via a chat system or video call).
 The Council discusses current issues, clear through anything outstanding which can be quickly resolved, and to ensure that nothing urgent is left pending.
-All members are be expected to regularly communicate what is going on in their area, through blog posts or other public updates.
+All members are expected to regularly communicate what is going on in their area, through blog posts or other public updates.
 
 The Council holds a multi-day, face-to-face meeting annually.
 All members should strive to attend in person (travel funding is available).
@@ -212,22 +212,14 @@ These meetings are not public, but minutes and summary documents will be provide
 Additionally, the xref:fpl.adoc[Fedora Project Leader] will set aside regular times to meet with the community.
 Attendance is not mandatory for all Council members but is encouraged.
 
-
-Transparency
-~~~~~~~~~~~~
+=== Transparency
 
 The general policy of the Fedora Council is to default to open.
-Most meetings are held in public channels,
-and open to all Fedora users and contributors.
-iscussion is held in on a
-https://discussion.fedoraproject.org/tags/c/project/7/council[public forum]
-open to all subscribers, and formal decisions will be
-recorded in a public ticket tracking system.
+Most meetings are held in public channels, and open to all Fedora users and contributors.
+Discussion is held in a https://discussion.fedoraproject.org/tag/council[public forum] open to all, and formal decisions will be recorded in a public ticket tracking system.
 
-Occasionally, when personal, private, or sensitive issues need to be
-discussed, a phone call might be used. A private mailing list and ticket
-tracking instance also exist for these situations, but will also only be
-used when dealing with these uncommon issues.
+Occasionally, when personal, private, or sensitive issues need to be discussed, a video call might be used.
+A private mailing list and ticket tracking instance also exist for these situations, but will also only be used when dealing with these uncommon issues.
 
 
 Time Commitment