From c78c5751031fe14d26403376b05f24b857941563 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Thu, 11 Jan 2024 10:53:28 +0100 Subject: [PATCH 01/21] Move community_topics_workflow to docs.ansible.com --- docs/docsite/rst/community/communication.rst | 2 + .../steering/community_topics_workflow.rst | 88 +++++++------------ 2 files changed, 36 insertions(+), 54 deletions(-) diff --git a/docs/docsite/rst/community/communication.rst b/docs/docsite/rst/community/communication.rst index 54fa46e350d..d929a4b0a82 100644 --- a/docs/docsite/rst/community/communication.rst +++ b/docs/docsite/rst/community/communication.rst @@ -22,6 +22,8 @@ The `Ansible Forum `_ is a single starting point and Take a look at the `forum groups `_ and join ones that match your interests. In most cases, joining a forum group automatically subscribes you to related posts. +.. _bullhorn: + The Bullhorn ------------ diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index dd2f1b2024e..6cce8389bc3 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -4,121 +4,101 @@ For other changes, create a `community topic `_ to discuss them. (Creating a draft PR for this file and mentioning it in the community topic is also OK.) -Ansible community topics workflow -================================= +.. _community_topics_workflow: + +Community topics workflow +========================= Overview -------- -This document describes the Ansible community topics workflow (herein after ``Workflow``) to provide guidance on successful resolving topics in an asynchronous way. +This document describes the Ansible Community Topics workflow (hereinafter Workflow) to provide guidance on successful resolving topics in the asynchronous way. The Workflow is a set of actions that need to be done successively within the corresponding time frames. -.. note:: - - If you have any ideas on how the Workflow can be improved, please create an issue in this repository or pull request against this document. - Creating a topic ---------------- -Any person can `create a topic `_ tagged with ``community-wg`` under the ``Project Discussions`` category in the `Ansible Forum `_. A :ref:`Steering Committee member` can tag the forum post with `community-wg-nextmtg` to put it on the meeting agenda. +Any person can `create a topic `_ tagged with ``community-wg`` under the ``Project Discussions`` category in the `Ansible Forum `_. +A :ref:`steering committee ` member can tag the forum post with ``community-wg-nextmtg`` to put it on the meeting agenda. Workflow -------- .. note:: - This is a rough scenario and it can vary depending on a topic's complexity and other nuances, for example, when there is a mass agreement upfront. + This is a rough scenario and it can vary depending on a topic's complexity and other nuances, for example, when there is a mass agreement up-front. Preparation stage -^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~ -A Committee person checks the topic content and asks the author, or other persons, to provide additional information if needed. +* A Committee person checks the topic's content, asks the author/other persons to provide additional information if needed. Discussion stage -^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~ * If the topic is ready to be discussed, the Committee person: * Adds the ``community-wg-nextmtg`` tag if it needs to be discussed in the meeting. - * Opens the discussion by adding a comment asking the Community and the Committee to take part in it. - * No synchronous discussion is needed (there are no blockers, complications, confusion, or impasses). Voting stage -^^^^^^^^^^^^ +~~~~~~~~~~~~ -* Depending on the topic complexity, 1-2 weeks after the discussion was opened, the Committee person formulates vote options based on the prior discussion and gives participants a reasonable amount of time to propose changes to the options (no longer than a week). The person summarizes the options in a comment and also establishes a date when the vote begins if there are no objections about the options or vote date. -* In the vote date, the vote starts with a comment from a Committee person who opens the vote and establishes a date when the vote ends ($CURRENT_DATE + no longer than 21 days; Usually it should not exceed 14 days. 21 days should only be used if it is known that a lot of interested persons will likely not have time to vote in a 14 day period). +* Depending on the topic's complexity, 1-2 weeks after the discussion was opened, the Committee person formulates vote options based on the prior discussion and gives participants reasonable amount of time to propose changes to the options (no longer than a week). The person summarizes the options in a comment and also establishes a date when the vote begins if there are no objections about the options/vote date. +* In the vote date, the vote starts with the comment of a Committee person which opens the vote and establishes a date when the vote ends ($CURRENT_DATE + no longer than 21 days; usually it should not exceed 14 days, 21 days should only be used if it is known that a lot of interested persons will likely not have time to vote in a 15 days period). * The Committee person labels the topic with the ``active-vote`` tag. -* The Committee person adds ``[Vote ends on $YYYY-MM-DD]`` to the beginning of the topic description. +* The Committee person adds ``[Vote ends on $YYYY-MM-DD]`` to the beginning of the topic's description. * A vote is actually two polls, one for the Steering Committee, one for everyone else. To create a vote in a topic: * Create a new post in the topic. - - * Click the ``gear`` button in the composer and select ``Build Poll``. - + * Click the ``gear`` button in the composer and select Build Poll. * Click the ``gear`` in the Poll Builder for advanced mode. - * Set up the options (generally this will be Single Choice but other poll types can be used). - * Title it "Steering Committee vote" and "Limit voting" to the ``Steering Committee``. - - * Do not set the close date because it cannot be changed later. - - * Results should be "Always Visible" unless there is some good reason for the SC votes not to be public. - + * Do not set the close date because this cannot be changed later. + * Results should be ``Always Visible`` unless there is some good reason for the SC votes not to be public. * Submit the poll (the BBcode will appear in the post) and then repeat the above for the second poll. - - * The title should be "Community vote". - - * No group limitation. + * Title should be "Community vote". + * No group limitation. Voting result stage -^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~ -* The day after the last day of the vote, the Committee person: +* The next day after the last day of the vote, the Committee person: * Closes the polls. - * Removes the ``active-vote`` tag. - * Add a comment that the vote ended. - * Changes the beginning of the topic's description to ``[Vote ended]``. - * Creates a summary comment declaring the vote result. - -* The vote result and final decision are announced via the `Bullhorn newsletter `_. - +* The vote's result and the final decision are announced via the :ref:`Bullhorn `. Implementation stage -^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~ * If the topic implies some actions (if it does not, just mark this as complete), the Committee person: - * Assigns the topic to the person who is responsible for performing the actions. - + * Assigns the topic to a person responsible for performing the actions. * Add the ``being-implemented`` tag to the topic. - - * After the topic is implemented, the assignee: +* After the topic is implemented, the assignee: * Comments on the topic that the work is done. - * Removes the ``being-implemented`` tag. - * Add the ``implemented`` tag. - * If the topic implies actions related to the future Ansible Community package releases (for example, a collection exclusion), the Committee person: * Adds the ``scheduled-for-future-release`` tag to the topic. + * Checks if there's a corresponding milestone in the `ansible-build-data `_ repository. If there's no milestone, the person creates it. + * Creates an issue in ansible-build-data that references the topic in community-topics, and adds it to the milestone. - * Checks if there is a corresponding milestone in the `ansible-build-data `_ repository. If there is no milestone, the person creates it. +Tools +~~~~~ - * Creates an issue in ansible-build-data that references the :ref:`community topic`, and adds it to the milestone. +There are a few `scripts `_ that can be used to create Ansible community announcements on Bullhorn and similar. -Tools ------ +.. seealso:: -We have some `scripts `_ that can be used to create Ansible community announcements in the Bullhorn and similar places. + :ref:`steering committee ` + Ansible Community Steering Committee From 21fa7e73d8b8c2424c1c03c9e918977972cb2482 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Fri, 12 Jul 2024 11:03:25 +0200 Subject: [PATCH 02/21] Simplify --- .../steering/community_topics_workflow.rst | 121 +++++++++++------- 1 file changed, 72 insertions(+), 49 deletions(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 6cce8389bc3..38a70684974 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -16,85 +16,108 @@ This document describes the Ansible Community Topics workflow (hereinafter Workf The Workflow is a set of actions that need to be done successively within the corresponding time frames. +.. note:: + + This is a rough scenario and it can vary depending on a topic's complexity and other nuances, for example, when there is a mass agreement up-front. + Creating a topic ---------------- Any person can `create a topic `_ tagged with ``community-wg`` under the ``Project Discussions`` category in the `Ansible Forum `_. -A :ref:`steering committee ` member can tag the forum post with ``community-wg-nextmtg`` to put it on the meeting agenda. - -Workflow --------- - -.. note:: - - This is a rough scenario and it can vary depending on a topic's complexity and other nuances, for example, when there is a mass agreement up-front. Preparation stage -~~~~~~~~~~~~~~~~~ +----------------- * A Committee person checks the topic's content, asks the author/other persons to provide additional information if needed. Discussion stage -~~~~~~~~~~~~~~~~ +---------------- -* If the topic is ready to be discussed, the Committee person: +* The discussion by default happens asynchronously in the topic. - * Adds the ``community-wg-nextmtg`` tag if it needs to be discussed in the meeting. - * Opens the discussion by adding a comment asking the Community and the Committee to take part in it. -* No synchronous discussion is needed (there are no blockers, complications, confusion, or impasses). + * A :ref:`steering committee ` member can tag the forum post with ``community-wg-nextmtg`` to put it on the synchronous meeting agenda. Voting stage -~~~~~~~~~~~~ +------------ + +The Committee person: -* Depending on the topic's complexity, 1-2 weeks after the discussion was opened, the Committee person formulates vote options based on the prior discussion and gives participants reasonable amount of time to propose changes to the options (no longer than a week). The person summarizes the options in a comment and also establishes a date when the vote begins if there are no objections about the options/vote date. -* In the vote date, the vote starts with the comment of a Committee person which opens the vote and establishes a date when the vote ends ($CURRENT_DATE + no longer than 21 days; usually it should not exceed 14 days, 21 days should only be used if it is known that a lot of interested persons will likely not have time to vote in a 15 days period). -* The Committee person labels the topic with the ``active-vote`` tag. -* The Committee person adds ``[Vote ends on $YYYY-MM-DD]`` to the beginning of the topic's description. -* A vote is actually two polls, one for the Steering Committee, one for everyone else. To create a vote in a topic: +* Depending on the topic's complexity, 1-2 weeks after the discussion was opened, formulates vote options based on the prior discussion and gives participants reasonable amount of time to propose changes to the options (no longer than a week). +* Summarizes the options in a comment and also establishes a date when the vote begins and ends if there are no objections about the options. +* In the vote date, starts the vote and establishes its end date, which is $CURRENT_DATE plus: + + * 7 days: simple cases + * 14 days: should not be more than that + * 21 days: only used in cases like common holiday seasons when the majority of the Committee out of participation +* Labels the topic with the ``active-vote`` tag. +* Adds ``[Vote ends on $YYYY-MM-DD]`` to the beginning of the topic's description. + +The vote always consists of two polls: one for the Steering Committee, one for everyone else. To create a vote in a topic: * Create a new post in the topic. - * Click the ``gear`` button in the composer and select Build Poll. - * Click the ``gear`` in the Poll Builder for advanced mode. - * Set up the options (generally this will be Single Choice but other poll types can be used). - * Title it "Steering Committee vote" and "Limit voting" to the ``Steering Committee``. - * Do not set the close date because this cannot be changed later. + * Click the ``gear`` button in the composer and select ``Build Poll``. + * Click the ``gear`` in the ``Poll Builder`` for advanced mode. + * Set up the options (generally this will be ``Single Choice`` but other poll types can be used). + * Title it "Steering Committee vote" and ``Limit voting`` to the ``@SteeringCommittee``. + * Do NOT set the close date because this cannot be changed later. * Results should be ``Always Visible`` unless there is some good reason for the SC votes not to be public. - * Submit the poll (the BBcode will appear in the post) and then repeat the above for the second poll. - * Title should be "Community vote". - * No group limitation. + * Submit the poll (the BBcode will appear in the post): + * Repeat the above for the second poll: + + * Title should be "Community vote". + * No group limitation. Voting result stage -~~~~~~~~~~~~~~~~~~~ +------------------- -* The next day after the last day of the vote, the Committee person: +The next day after the last day of the vote, the Committee person: - * Closes the polls. - * Removes the ``active-vote`` tag. - * Add a comment that the vote ended. - * Changes the beginning of the topic's description to ``[Vote ended]``. - * Creates a summary comment declaring the vote result. -* The vote's result and the final decision are announced via the :ref:`Bullhorn `. +* Closes the polls if the :ref:`quorum` is reached, otherwise prolongs the polls. +* Removes the ``active-vote`` tag. +* Add a comment that the vote ended. +* Changes the beginning of the topic's description to ``[Vote ended]``. +* Creates a summary comment declaring the vote result. +* Announces the vote result and the final decision in the :ref:`Bullhorn `. Implementation stage -~~~~~~~~~~~~~~~~~~~~ +-------------------- + +No further action required +~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The Committee person: + +* Merges an associated pull request if exists. +* Adds the ``resolved`` tag. + +Further actions required +~~~~~~~~~~~~~~~~~~~~~~~~ + +The Committee person: + +* Assigns a person responsible for performing the actions by mentioning them in a comment. +* Adds the ``being-implemented`` tag to the topic. + +After the actions are done, the assignee: + +* Comments on the topic that the work is done. +* Removes the ``being-implemented`` tag. +* Adds the ``implemented`` and ``resolved`` tags. -* If the topic implies some actions (if it does not, just mark this as complete), the Committee person: +Package-release related actions required +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - * Assigns the topic to a person responsible for performing the actions. - * Add the ``being-implemented`` tag to the topic. -* After the topic is implemented, the assignee: +If the topic implies actions related to the future Ansible Community package releases (for example, a collection exclusion), the Committee person/assignee: - * Comments on the topic that the work is done. - * Removes the ``being-implemented`` tag. - * Add the ``implemented`` tag. -* If the topic implies actions related to the future Ansible Community package releases (for example, a collection exclusion), the Committee person: +* Adds the ``scheduled-for-future-release`` tag to the topic. +* Checks if there is a corresponding milestone in the `ansible-build-data `_ repository. - * Adds the ``scheduled-for-future-release`` tag to the topic. - * Checks if there's a corresponding milestone in the `ansible-build-data `_ repository. If there's no milestone, the person creates it. - * Creates an issue in ansible-build-data that references the topic in community-topics, and adds it to the milestone. + * If there is no milestone, the person creates it. +* Creates an issue in ansible-build-data that references the topic and adds it to the milestone. +* After it is implemented, adds the ``implemented`` and ``resolved`` tags. Tools -~~~~~ +----- There are a few `scripts `_ that can be used to create Ansible community announcements on Bullhorn and similar. From eecf5bcd101bcde7473bd48914623a64eb260965 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 08:53:19 +0200 Subject: [PATCH 03/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Mario Lenz --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 38a70684974..fe433fa0776 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -28,7 +28,7 @@ Any person can `create a topic Date: Tue, 16 Jul 2024 08:53:34 +0200 Subject: [PATCH 04/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Mario Lenz --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index fe433fa0776..a40576afcfb 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -33,7 +33,7 @@ Preparation stage Discussion stage ---------------- -* The discussion by default happens asynchronously in the topic. +* By default, the discussion happens asynchronously in the topic. * A :ref:`steering committee ` member can tag the forum post with ``community-wg-nextmtg`` to put it on the synchronous meeting agenda. From 9d0276acf0a3185bab577d36245db7aa8aa62b5a Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 08:57:45 +0200 Subject: [PATCH 05/21] Improve --- .../rst/community/steering/community_topics_workflow.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index a40576afcfb..8334c860bcb 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -12,9 +12,9 @@ Community topics workflow Overview -------- -This document describes the Ansible Community Topics workflow (hereinafter Workflow) to provide guidance on successful resolving topics in the asynchronous way. +This document describes the Ansible community topics workflow to provide guidance on successful resolving topics in the asynchronous way. -The Workflow is a set of actions that need to be done successively within the corresponding time frames. +The workflow is a set of actions that need to be done successively within the corresponding time frames. .. note:: @@ -107,7 +107,7 @@ After the actions are done, the assignee: Package-release related actions required ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -If the topic implies actions related to the future Ansible Community package releases (for example, a collection exclusion), the Committee person/assignee: +If the topic implies actions related to the future Ansible community package releases (for example, a collection exclusion), the Committee person/assignee: * Adds the ``scheduled-for-future-release`` tag to the topic. * Checks if there is a corresponding milestone in the `ansible-build-data `_ repository. From 8b7562150ddc9bd8781ea045f4938cd2dcefaeeb Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 09:09:53 +0200 Subject: [PATCH 06/21] Replacing Creating a topic section content --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 8334c860bcb..5b0e7bafea4 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -23,7 +23,7 @@ The workflow is a set of actions that need to be done successively within the co Creating a topic ---------------- -Any person can `create a topic `_ tagged with ``community-wg`` under the ``Project Discussions`` category in the `Ansible Forum `_. +Any person can :ref:`create a community topic`. Preparation stage ----------------- From 53801b7aa08b32dadd1526fe22781e279bd2a013 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:12:19 +0200 Subject: [PATCH 07/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 5b0e7bafea4..93a704248a0 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -14,7 +14,7 @@ Overview This document describes the Ansible community topics workflow to provide guidance on successful resolving topics in the asynchronous way. -The workflow is a set of actions that need to be done successively within the corresponding time frames. +The workflow is a set of actions that need to be completed in order within the corresponding time frames. .. note:: From c0d6a057cc9d44231762c19cf8173518e3c8dad4 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:12:33 +0200 Subject: [PATCH 08/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 93a704248a0..80970dadb1c 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -18,7 +18,8 @@ The workflow is a set of actions that need to be completed in order within the c .. note:: - This is a rough scenario and it can vary depending on a topic's complexity and other nuances, for example, when there is a mass agreement up-front. + The following section outlines a generic scenario for a workflow. + Workflows can vary depending on a topic's complexity and other nuances; for example, when there is a mass agreement from the beginning. Creating a topic ---------------- From d78ceb1715c3efa9678a84f1b44e7a22699e92d3 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:13:00 +0200 Subject: [PATCH 09/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 80970dadb1c..6aea7e336d6 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -29,7 +29,7 @@ Any person can :ref:`create a community topic`. Preparation stage ----------------- -* A Committee person checks the topic's content and asks the author/other persons to provide additional information if needed. +* A Committee person checks the topic's content and asks the author/other persons to provide additional information as needed. Discussion stage ---------------- From b87a1e4c3605bcce093d172fba791d1eb6a283e2 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:13:30 +0200 Subject: [PATCH 10/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 6aea7e336d6..dc75e1ec6da 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -43,7 +43,7 @@ Voting stage The Committee person: -* Depending on the topic's complexity, 1-2 weeks after the discussion was opened, formulates vote options based on the prior discussion and gives participants reasonable amount of time to propose changes to the options (no longer than a week). +* Formulates vote options based on the prior discussion and gives participants up to one week to propose changes to the options. This step takes place one to two weeks after the discussion was opened, depending on the complexity of the topic. * Summarizes the options in a comment and also establishes a date when the vote begins and ends if there are no objections about the options. * In the vote date, starts the vote and establishes its end date, which is $CURRENT_DATE plus: From 881d084b271d71116b80b669260732598cc6a010 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:13:49 +0200 Subject: [PATCH 11/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index dc75e1ec6da..3ffd0f2130d 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -44,7 +44,7 @@ Voting stage The Committee person: * Formulates vote options based on the prior discussion and gives participants up to one week to propose changes to the options. This step takes place one to two weeks after the discussion was opened, depending on the complexity of the topic. -* Summarizes the options in a comment and also establishes a date when the vote begins and ends if there are no objections about the options. +* Summarizes the options in a comment and establishes a dates for the vote to begin if there are no objections to the options. * In the vote date, starts the vote and establishes its end date, which is $CURRENT_DATE plus: * 7 days: simple cases From ab0c8d8c35c57c1b39a6d79540d521051b543c13 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:14:08 +0200 Subject: [PATCH 12/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 3ffd0f2130d..da0ed6bfda3 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -45,7 +45,7 @@ The Committee person: * Formulates vote options based on the prior discussion and gives participants up to one week to propose changes to the options. This step takes place one to two weeks after the discussion was opened, depending on the complexity of the topic. * Summarizes the options in a comment and establishes a dates for the vote to begin if there are no objections to the options. -* In the vote date, starts the vote and establishes its end date, which is $CURRENT_DATE plus: +* Starts the vote on the beginning date and establishes an end date, which is $CURRENT_DATE plus: * 7 days: simple cases * 14 days: should not be more than that From 63ccc65d7366f8cdbd264ab9923c9b9de675f4ee Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:14:17 +0200 Subject: [PATCH 13/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index da0ed6bfda3..fe943022841 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -48,7 +48,7 @@ The Committee person: * Starts the vote on the beginning date and establishes an end date, which is $CURRENT_DATE plus: * 7 days: simple cases - * 14 days: should not be more than that + * 14 days: maximum vote length * 21 days: only used in cases like common holiday seasons when the majority of the Committee out of participation * Labels the topic with the ``active-vote`` tag. * Adds ``[Vote ends on $YYYY-MM-DD]`` to the beginning of the topic's description. From 0f755bf367531909885ff00fd6a72c5f378f2b6d Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:14:37 +0200 Subject: [PATCH 14/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index fe943022841..2032f581b03 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -49,7 +49,7 @@ The Committee person: * 7 days: simple cases * 14 days: maximum vote length - * 21 days: only used in cases like common holiday seasons when the majority of the Committee out of participation + * 21 days: only used in exceptional cases such as holiday seasons when the majority of the Committee are not able to participate in the vote * Labels the topic with the ``active-vote`` tag. * Adds ``[Vote ends on $YYYY-MM-DD]`` to the beginning of the topic's description. From 0ddf5fa2e1e3fa18ebff842aa674ce22aa41ac22 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:14:52 +0200 Subject: [PATCH 15/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 2032f581b03..af47ccb0330 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -61,7 +61,7 @@ The vote always consists of two polls: one for the Steering Committee, one for e * Set up the options (generally this will be ``Single Choice`` but other poll types can be used). * Title it "Steering Committee vote" and ``Limit voting`` to the ``@SteeringCommittee``. * Do NOT set the close date because this cannot be changed later. - * Results should be ``Always Visible`` unless there is some good reason for the SC votes not to be public. + * Results should be ``Always Visible`` unless there is a good reason for the SC votes not to be public. * Submit the poll (the BBcode will appear in the post): * Repeat the above for the second poll: From aa33a1605cda9e07d215a91dee8145f0538d2bde Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:14:59 +0200 Subject: [PATCH 16/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index af47ccb0330..310d76aff8d 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -63,7 +63,7 @@ The vote always consists of two polls: one for the Steering Committee, one for e * Do NOT set the close date because this cannot be changed later. * Results should be ``Always Visible`` unless there is a good reason for the SC votes not to be public. * Submit the poll (the BBcode will appear in the post): - * Repeat the above for the second poll: + * Repeat the above steps for the second poll: * Title should be "Community vote". * No group limitation. From 662b5c706a5ee2340aad91587950f62d610fac41 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:15:23 +0200 Subject: [PATCH 17/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 310d76aff8d..914b5fef875 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -75,7 +75,7 @@ The next day after the last day of the vote, the Committee person: * Closes the polls if the :ref:`quorum` is reached, otherwise prolongs the polls. * Removes the ``active-vote`` tag. -* Add a comment that the vote ended. +* Adds a comment that the vote has ended. * Changes the beginning of the topic's description to ``[Vote ended]``. * Creates a summary comment declaring the vote result. * Announces the vote result and the final decision in the :ref:`Bullhorn `. From bf559e6832d0edf2f936730ecd35e17126e661b7 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:15:32 +0200 Subject: [PATCH 18/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 914b5fef875..da5b6ee8ed9 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -114,7 +114,7 @@ If the topic implies actions related to the future Ansible community package rel * Checks if there is a corresponding milestone in the `ansible-build-data `_ repository. * If there is no milestone, the person creates it. -* Creates an issue in ansible-build-data that references the topic and adds it to the milestone. +* Creates an issue in ``ansible-build-data`` that references the topic and adds it to the milestone. * After it is implemented, adds the ``implemented`` and ``resolved`` tags. Tools From 2af1d5fa5e0f52db9d7d5d90203d3f8c6f787ca4 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:15:48 +0200 Subject: [PATCH 19/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index da5b6ee8ed9..7baa0c7a71b 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -120,7 +120,7 @@ If the topic implies actions related to the future Ansible community package rel Tools ----- -There are a few `scripts `_ that can be used to create Ansible community announcements on Bullhorn and similar. +There are a few `scripts `_ that can be used to create Ansible community announcements on the Bullhorn and similar locations. .. seealso:: From 572dae1c36ecec914373425a3500574a26be45d5 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 16 Jul 2024 13:17:57 +0200 Subject: [PATCH 20/21] Clarify --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 7baa0c7a71b..1971be8479e 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -71,7 +71,7 @@ The vote always consists of two polls: one for the Steering Committee, one for e Voting result stage ------------------- -The next day after the last day of the vote, the Committee person: +On the vote end date, the Committee person: * Closes the polls if the :ref:`quorum` is reached, otherwise prolongs the polls. * Removes the ``active-vote`` tag. From 596306e77a67a84225d64eff377ecab8cc8dbb47 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Wed, 17 Jul 2024 07:31:36 +0200 Subject: [PATCH 21/21] Update docs/docsite/rst/community/steering/community_topics_workflow.rst Co-authored-by: Don Naro --- .../rst/community/steering/community_topics_workflow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 1971be8479e..0e32d516d37 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -44,7 +44,7 @@ Voting stage The Committee person: * Formulates vote options based on the prior discussion and gives participants up to one week to propose changes to the options. This step takes place one to two weeks after the discussion was opened, depending on the complexity of the topic. -* Summarizes the options in a comment and establishes a dates for the vote to begin if there are no objections to the options. +* Summarizes the options in a comment and establishes a date for the vote to begin if there are no objections to the options. * Starts the vote on the beginning date and establishes an end date, which is $CURRENT_DATE plus: * 7 days: simple cases