Repository: sktime/sktime
Pull request: [GOV] CC observers role, update to role holders, add Guzal to CC
<!--
Thanks for contributing a pull request! Please ensure you have taken a look
at our contribution guide: https://github.com/sktime/sktime/blob/main/CONTRIBUTING.md
-->

#### Reference Issues/PRs
<!--
Example: Fixes #1234. See also #3456.

Please use keywords (e.g., Fixes) to create link to the issues or pull requests
you resolved, so that they will automatically be closed when your pull request
is merged. See https://github.com/blog/1506-closing-issues-via-pull-requests
-->
Fixes https://github.com/sktime/community-org/issues/26 

#### What does this implement/fix? Explain your changes.
<!--
A clear and concise description of what you have implemented.
-->
Update the governance doc to add CC observer role
#### Does your contribution introduce a new dependency? If yes, which one?

<!--
If your contribution does add a new hard dependency, we may suggest to initially develop your contribution in a separate companion package in https://github.com/sktime/ to keep external dependencies of the core sktime package to a minimum.
-->
No
#### What should a reviewer concentrate their feedback on?

<!-- This section is particularly useful if you have a pull request that is still in development. You can guide the reviews to focus on the parts that are ready for their comments. We suggest using bullets (indicated by * or -) and filled checkboxes [x] here -->
- The role description - is it correct, anything to add?
- Readthedocs
#### Any other comments?
TODO:
- [x] add current observers to the team list

#### PR checklist
<!--
Please go through the checklist below. Please feel free to remove points if they are not applicable.
-->

##### For all contributions
- [x] The PR title starts with either [ENH], [MNT], [DOC], or [BUG] indicating whether the PR topic is related to enhancement, maintenance, documentation, or bug.


Problem statement:
[DOC] Governance update: add observers
#### Describe the issue linked to the documentation

1. All governance page links in this repo lead to a page that doesn't exist 
2. Observers' role in the CC is present but not documented.

#### Suggest a potential alternative/fix

<!--
Tell us how we could improve the documentation in this regard.
-->
1. Fix the links / update the documentation
2. Add a section on observers' role and current observer members of the CC.

Hints from issue discussion:

Commit message: chore: update team.rst

Patch to review:
diff --git a/docs/source/about/team.rst b/docs/source/about/team.rst
index f64d1298fff..469e3adf3a4 100644
--- a/docs/source/about/team.rst
+++ b/docs/source/about/team.rst
@@ -20,6 +20,20 @@ Community Council
    * - Martin Walter
      - :user:`aiwalter`
 
+Community Council Observers
+---------------------------
+
+.. list-table::
+   :header-rows: 1
+
+   * - Name
+     - GitHub ID
+   * - Leonidas Tsaprounis
+     - :user:`ltsaprounis`
+   * - Lovkush Agarwal
+     - :user:`lovkush-a`
+   * - Łukasz Mentel
+     - :user:`lmmentel`
 
 Code of Conduct Committee
 -------------------------
diff --git a/docs/source/get_involved/governance.rst b/docs/source/get_involved/governance.rst
index 5377a1a5841..3686666175c 100644
--- a/docs/source/get_involved/governance.rst
+++ b/docs/source/get_involved/governance.rst
@@ -232,7 +232,7 @@ Anyone is eligible to be a CoC committee member.
 Appointment
 ^^^^^^^^^^^
 
-Membership of the CC is by nomination by a core developer and a vote by
+Membership of the CoC is by nomination by a core developer and a vote by
 all core developers. A nomination will result in discussion which will stay
 open for 5 days excluding weekends and then a vote by the core
 developers which will stay open for 5 days excluding weekends. CoC committee
@@ -320,6 +320,45 @@ For more details about our meetings, please go to our `community-council reposit
 
 To contact the CC directly, please send an email to info@sktime.org.
 
+.. _cc-observers:
+
+CC observers
+~~~~~~~~~~
+
+CC (community council) observers are core developers with additional rights and
+responsibilities. Current CC observers are listed in the `community-council
+observers <https://www.sktime.org/en/stable/about/team.html>`__ .
+
+.. _rights-and-responsibilities-4:
+
+Rights and responsibilities
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Observers have a full view of CC and participate in the decision making process
+during CC discussions to ensure that more members of the community have direct
+input on CC decisions.
+
+Eligibility
+^^^^^^^^^^^
+Only core developers are eligible for appointment as CC observers.
+Non-core-developers can be nominated, but this must be accompanied
+by a nomination for core developer, and a core developer appointment vote
+concurrent with the 5 day discussion period (see below).
+
+.. _appointment-4:
+
+Appointment
+^^^^^^^^^^^
+Membership of the CC observers is by nomination by a core developer and a vote by
+all core developers. A nomination will result in discussion which will stay
+open for 5 days excluding weekends and then a vote by the core
+developers which will stay open for 5 days excluding weekends. CoC committee
+membership votes are subject to:
+
+* a 2/3 majority of all cast votes, and
+* a simple majority approval of all the current CoC committee members.
+
+In case of ties, the CC member with shortest tenure breaks the tie.
+
 .. _decision-making:
 
 Decision making


Code review comments:
diff_hunk: @@ -320,6 +320,45 @@ For more details about our meetings, please go to our `community-council reposit
 
 To contact the CC directly, please send an email to info@sktime.org.
 
+.. _cc-observers:
+
+CC observers
+~~~~~~~~~~
+
+CC (community council) observers are core developers with additional rights and
+responsibilities. Current CC observers are listed in the `community-council
+observers <https://www.sktime.org/en/stable/about/team.html>`__ .
+
+.. _rights-and-responsibilities-4:
+
+Rights and responsibilities
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Observers have a full view of CC and participate in the decision making process
path: docs/source/get_involved/governance.rst
text: @user1:
I would be specific and clearer. How about (based on your paragraph):

CC observers have a full view of reserved CC proceedings, the private CC channels and the sktime email account.
CC observers can participate in discussions on private CC channels to ensure that more members of the community have direct input on CC decisions.
CC observers do not possess the voting or decision making rights of full CC members.

diff_hunk: @@ -320,6 +320,45 @@ For more details about our meetings, please go to our `community-council reposit
 
 To contact the CC directly, please send an email to info@sktime.org.
 
+.. _cc-observers:
+
+CC observers
+~~~~~~~~~~
+
+CC (community council) observers are core developers with additional rights and
+responsibilities. Current CC observers are listed in the `community-council
+observers <https://www.sktime.org/en/stable/about/team.html>`__ .
+
+.. _rights-and-responsibilities-4:
+
+Rights and responsibilities
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Observers have a full view of CC and participate in the decision making process
+during CC discussions to ensure that more members of the community have direct
+input on CC decisions.
+
+Eligibility
+^^^^^^^^^^^
+Only core developers are eligible for appointment as CC observers.
+Non-core-developers can be nominated, but this must be accompanied
+by a nomination for core developer, and a core developer appointment vote
+concurrent with the 5 day discussion period (see below).
+
+.. _appointment-4:
+
+Appointment
+^^^^^^^^^^^
+Membership of the CC observers is by nomination by a core developer and a vote by
path: docs/source/get_involved/governance.rst
text: @user1:
this is copy-pasting the wrong paragraph, no?

Approval should be by CC, not CoC committee.
Other than that, makes sense as a mechanism.

I would actually tend to reduce the majorities required - since the idea is input and transparency rather than actual decision making, my intuition in mechanism design would tell me that we should reduce the barrier more. Perhaps to one third of all cast votes?

@user1:
(so it can be a minority! but there needs to be at least a group of people)