From fd72bf2ab659c6e17a0e4fa286e17fb09b43c72d Mon Sep 17 00:00:00 2001 From: RRosio Date: Wed, 13 Dec 2023 10:30:43 -0800 Subject: [PATCH 01/14] Initial Documentation working group charter --- charters/DocumentationCharter.md | 54 +++++++++++++++++++ ..._standing_committees_and_working_groups.md | 5 ++ 2 files changed, 59 insertions(+) create mode 100644 charters/DocumentationCharter.md diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md new file mode 100644 index 00000000..7428898f --- /dev/null +++ b/charters/DocumentationCharter.md @@ -0,0 +1,54 @@ +# Docs Working Group Charter (Proposed) + +## Mission and Goals + +The Docs Working Group serves as a support, helper, and advisory body to Jupyter subprojects on all aspects of documentation. The core pillars of our mission: + +- Improve all aspects of documentation across the Jupyter ecosystem +- Make high quality documentation that is clear, comprehensive, inclusive, and serves the varying needs of Jupyter's diverse community +- Engage with the community to help users with Jupyter products, discover their needs, and connect them with relevant information, expertise and resources + +The Docs Working Group will provide a place for consistent, focused, holistic efforts to be spent on docs across the whole ecosystem. This group exists in part to provide capacity and resources to the subprojects (some of which are already suffering from a lack of resources/capacity, and more specifically to work on docs in particular). + +We want all users to have positive experiences inside the Jupyter ecosystem, especially users who are learning and coming in for the first time, and users with disabilities. + +## The Docs Working Group's Activities + +The Docs Working Group will focus on the efforts described below, in service of its mission: + +- Help write docs (inside the bounds of each subproject's governance) + - This includes meta docs, cross-cutting docs (items relevant to multiple subprojects), developer and contributor docs, non user-facing docs and others +- Develop recommendations and guidance: + - For communicating common information and concepts across the Jupyter ecosystem + - Because we want to encourage consistency across the Jupyter ecosystem and between different projects + - For style and best practices when authoring documentation media + - Including technical advice, such as tools-usage and markdown guidance that helps support high level goals, like interlinking/cross-connection between subprojects +- Community engagement + - To help connect users with information, expertise and resources + - To gather feedback from the community about what needs to be documented/what information they need +- Help support and improve all aspects of documentation across the Jupyter ecosystem + - This means, for members of the group, also taking on any related (non-document) tasks that will be beneficial to docs and support the Docs Working Group's goals, such as: + - Developing application extensions related to docs, like in-app integrated docs, guided in-application tours or hoverable "what's this" features + - Automations for gathering ReadTheDocs traffic stats to gauge user interest + - Creating pip installable packages for getting offline docs + - Writing PRs for unit tests related to documentation code + - Automated discourse or CI bots for gathering user feedback from community sites + - Adding a new embedded "Hot Topics" feature on ReadTheDocs FAQ pages to automated discourse community discussion aggregator + - Any other innovations or work that may improve Jovyans' experience in/understanding of the Jupyter ecosystem + +## Founding Members + +- Carlos Brandt +- Carol Willing +- Eric Gentry +- Frederic Collonval +- Mike Krassowski +- Nick Bollweg +- Paul Ivanov +- Rosio Reyes + +## Decision Making + +The Docs Working Group will establish a council (by Jupyter convention) to make decisions. + +The Docs Working Group Council will initially be made up of the founding members. Council members can then initiate a vote to add new members (or remove members by a two thirds majority with a quorum of two thirds of all council members). The voting process will follow the guidelines established in the [Jupyter Governance Decision Making document](https://jupyter.org/governance/decision_making.html). \ No newline at end of file diff --git a/list_of_standing_committees_and_working_groups.md b/list_of_standing_committees_and_working_groups.md index 05329e8e..4fc2b3e3 100644 --- a/list_of_standing_committees_and_working_groups.md +++ b/list_of_standing_committees_and_working_groups.md @@ -33,3 +33,8 @@ Charter Summary: License, protect, and promote the trademarks and visual and tex ### Jupyter Media Strategy [Charter](charters/MediaStrategyCharter.md) Summary: Ensure that communications in Jupyter official channels are strategic and benefit Project Jupyter. + + +### Jupyter Documentation + +[Charter](charters/DocumentationCharter.md) Summary: Serve as a support, helper, and advisory body to assist in improving all aspects of documentation across Jupyter subprojects. \ No newline at end of file From edaf7d6258f4737dc4242ed3899291bf366847a0 Mon Sep 17 00:00:00 2001 From: Rosio Date: Thu, 14 Dec 2023 10:34:32 -0800 Subject: [PATCH 02/14] Update charters/DocumentationCharter.md Co-authored-by: Afshin Taylor Darian --- charters/DocumentationCharter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index 7428898f..8cceda49 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -2,7 +2,7 @@ ## Mission and Goals -The Docs Working Group serves as a support, helper, and advisory body to Jupyter subprojects on all aspects of documentation. The core pillars of our mission: +The Docs Working Group serves as a support, helper, and advisory body to Jupyter Subprojects on all aspects of documentation. The core pillars of our mission: - Improve all aspects of documentation across the Jupyter ecosystem - Make high quality documentation that is clear, comprehensive, inclusive, and serves the varying needs of Jupyter's diverse community From a034362055fb9c06a713ffd3da9d4d559740548e Mon Sep 17 00:00:00 2001 From: Rosio Date: Thu, 14 Dec 2023 10:34:41 -0800 Subject: [PATCH 03/14] Update charters/DocumentationCharter.md Co-authored-by: Afshin Taylor Darian --- charters/DocumentationCharter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index 8cceda49..4a7b8ddb 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -16,7 +16,7 @@ We want all users to have positive experiences inside the Jupyter ecosystem, esp The Docs Working Group will focus on the efforts described below, in service of its mission: -- Help write docs (inside the bounds of each subproject's governance) +- Help write docs (inside the bounds of each Subproject's governance) - This includes meta docs, cross-cutting docs (items relevant to multiple subprojects), developer and contributor docs, non user-facing docs and others - Develop recommendations and guidance: - For communicating common information and concepts across the Jupyter ecosystem From 74e87a0f8c951bbc8fbb745064dee87594dddbca Mon Sep 17 00:00:00 2001 From: Rosio Date: Thu, 14 Dec 2023 10:34:48 -0800 Subject: [PATCH 04/14] Update charters/DocumentationCharter.md Co-authored-by: Afshin Taylor Darian --- charters/DocumentationCharter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index 4a7b8ddb..f8538c44 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -17,7 +17,7 @@ We want all users to have positive experiences inside the Jupyter ecosystem, esp The Docs Working Group will focus on the efforts described below, in service of its mission: - Help write docs (inside the bounds of each Subproject's governance) - - This includes meta docs, cross-cutting docs (items relevant to multiple subprojects), developer and contributor docs, non user-facing docs and others + - This includes meta docs, cross-cutting docs (items relevant to multiple Subprojects), developer and contributor docs, non user-facing docs and others - Develop recommendations and guidance: - For communicating common information and concepts across the Jupyter ecosystem - Because we want to encourage consistency across the Jupyter ecosystem and between different projects From 3cfe9ea852baa191c97cad8786cf58578214e417 Mon Sep 17 00:00:00 2001 From: Rosio Date: Thu, 14 Dec 2023 10:35:12 -0800 Subject: [PATCH 05/14] Update charters/DocumentationCharter.md Co-authored-by: Afshin Taylor Darian --- charters/DocumentationCharter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index f8538c44..893b4872 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -24,7 +24,7 @@ The Docs Working Group will focus on the efforts described below, in service of - For style and best practices when authoring documentation media - Including technical advice, such as tools-usage and markdown guidance that helps support high level goals, like interlinking/cross-connection between subprojects - Community engagement - - To help connect users with information, expertise and resources + - To help connect users with information, expertise, and resources - To gather feedback from the community about what needs to be documented/what information they need - Help support and improve all aspects of documentation across the Jupyter ecosystem - This means, for members of the group, also taking on any related (non-document) tasks that will be beneficial to docs and support the Docs Working Group's goals, such as: From 6636f95d3bcdd33a07b9d60e8c6967af8ebdfa2f Mon Sep 17 00:00:00 2001 From: RRosio Date: Thu, 14 Dec 2023 13:00:20 -0800 Subject: [PATCH 06/14] WIP updates as per EC meeting --- charters/DocumentationCharter.md | 42 +++++++++++++++----------------- 1 file changed, 19 insertions(+), 23 deletions(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index 893b4872..c1c12351 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -1,40 +1,36 @@ -# Docs Working Group Charter (Proposed) +# Documentation Working Group Charter ## Mission and Goals -The Docs Working Group serves as a support, helper, and advisory body to Jupyter Subprojects on all aspects of documentation. The core pillars of our mission: +The Documentation Working Group ("Docs Working Group") serves as a support, helper, and advisory body to Jupyter Subprojects on all aspects of documentation. The core pillars of our mission: - Improve all aspects of documentation across the Jupyter ecosystem - Make high quality documentation that is clear, comprehensive, inclusive, and serves the varying needs of Jupyter's diverse community - Engage with the community to help users with Jupyter products, discover their needs, and connect them with relevant information, expertise and resources -The Docs Working Group will provide a place for consistent, focused, holistic efforts to be spent on docs across the whole ecosystem. This group exists in part to provide capacity and resources to the subprojects (some of which are already suffering from a lack of resources/capacity, and more specifically to work on docs in particular). +The Docs Working Group will provide a place for consistent, focused, holistic efforts to be spent on documentation across the whole ecosystem. This group exists in part to provide capacity and resources to the subprojects (some of which are already suffering from a lack of resources/capacity, and more specifically to work on documentation in particular). We want all users to have positive experiences inside the Jupyter ecosystem, especially users who are learning and coming in for the first time, and users with disabilities. -## The Docs Working Group's Activities +## Areas of Responsibility + +The Docs Working Group is responsible for: + +- Creating and implementing minimum standards for documentation +- The Docs working group will take ownership of documentation and related materials not owned by a Subproject. +- Jupyter.org website and documentation + +## Doumentation Working Group's Activities The Docs Working Group will focus on the efforts described below, in service of its mission: -- Help write docs (inside the bounds of each Subproject's governance) - - This includes meta docs, cross-cutting docs (items relevant to multiple Subprojects), developer and contributor docs, non user-facing docs and others -- Develop recommendations and guidance: - - For communicating common information and concepts across the Jupyter ecosystem - - Because we want to encourage consistency across the Jupyter ecosystem and between different projects - - For style and best practices when authoring documentation media - - Including technical advice, such as tools-usage and markdown guidance that helps support high level goals, like interlinking/cross-connection between subprojects -- Community engagement - - To help connect users with information, expertise, and resources - - To gather feedback from the community about what needs to be documented/what information they need -- Help support and improve all aspects of documentation across the Jupyter ecosystem - - This means, for members of the group, also taking on any related (non-document) tasks that will be beneficial to docs and support the Docs Working Group's goals, such as: - - Developing application extensions related to docs, like in-app integrated docs, guided in-application tours or hoverable "what's this" features - - Automations for gathering ReadTheDocs traffic stats to gauge user interest - - Creating pip installable packages for getting offline docs - - Writing PRs for unit tests related to documentation code - - Automated discourse or CI bots for gathering user feedback from community sites - - Adding a new embedded "Hot Topics" feature on ReadTheDocs FAQ pages to automated discourse community discussion aggregator - - Any other innovations or work that may improve Jovyans' experience in/understanding of the Jupyter ecosystem +- Help write documentation (inside the bounds of each Subproject's governance) including meta documentation, cross-cutting documentation (items relevant to multiple Subprojects), developer and contributor documentaion, non user-facing documentation and others. +- Develop recommendations and guidance for best practices surrounding documentation authoring, communication of information, concepts and styling to promote consistency across the Jupyter ecosystem. +- Community engagement to help connect users with information, expertise, and resources; and to gather feedback from the community about what needs to be documented/what information they need. +- Help support and improve all aspects of documentation across the Jupyter ecosystem: our scope also includes any tasks, beyond writing documents, that will support the Doumentation Working Group's goals. To help illustrate the scope of our work, some clarifying examples are included below: + - Improving the user experience inside Jupyter applications by implementing offline and interactive documentation extensions. + - Implementing analytics systems for documentation webpages for better understanding of documentation use. + - Any other innovations or work that may improve Jovyans' experience in/understanding of the Jupyter ecosystem ## Founding Members From 429d5e97dd325f59b9a3e2279db5e8dd93c024c4 Mon Sep 17 00:00:00 2001 From: Rosio Date: Fri, 15 Dec 2023 10:53:53 -0800 Subject: [PATCH 07/14] Update charters/DocumentationCharter.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Michał Krassowski <5832902+krassowski@users.noreply.github.com> --- charters/DocumentationCharter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index c1c12351..8c274836 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -38,7 +38,7 @@ The Docs Working Group will focus on the efforts described below, in service of - Carol Willing - Eric Gentry - Frederic Collonval -- Mike Krassowski +- Michał Krassowski - Nick Bollweg - Paul Ivanov - Rosio Reyes From 09bd4d0968ef869d345d6c90d13ca6e3220b10e4 Mon Sep 17 00:00:00 2001 From: RRosio Date: Fri, 15 Dec 2023 11:17:51 -0800 Subject: [PATCH 08/14] Edits to areas of responsibilities. --- charters/DocumentationCharter.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index 8c274836..8b9cf0aa 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -14,11 +14,11 @@ We want all users to have positive experiences inside the Jupyter ecosystem, esp ## Areas of Responsibility -The Docs Working Group is responsible for: +The Docs Working Group is responsible for the following: + +- Setting standards for documentation where needed. +- The Docs working group will take ownership of documentation and related materials not owned by a Subproject (Jupyter.org website and documentation). -- Creating and implementing minimum standards for documentation -- The Docs working group will take ownership of documentation and related materials not owned by a Subproject. -- Jupyter.org website and documentation ## Doumentation Working Group's Activities @@ -30,7 +30,7 @@ The Docs Working Group will focus on the efforts described below, in service of - Help support and improve all aspects of documentation across the Jupyter ecosystem: our scope also includes any tasks, beyond writing documents, that will support the Doumentation Working Group's goals. To help illustrate the scope of our work, some clarifying examples are included below: - Improving the user experience inside Jupyter applications by implementing offline and interactive documentation extensions. - Implementing analytics systems for documentation webpages for better understanding of documentation use. - - Any other innovations or work that may improve Jovyans' experience in/understanding of the Jupyter ecosystem + - Any other innovations or work that may improve Jovyans' experience in/understanding of the Jupyter ecosystem. ## Founding Members From 54e40999f0a4260ee6d86c9b4098f1c37729d41f Mon Sep 17 00:00:00 2001 From: RRosio Date: Fri, 15 Dec 2023 11:25:34 -0800 Subject: [PATCH 09/14] Minor formatting updates. --- charters/DocumentationCharter.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index 8b9cf0aa..34a264fd 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -4,9 +4,9 @@ The Documentation Working Group ("Docs Working Group") serves as a support, helper, and advisory body to Jupyter Subprojects on all aspects of documentation. The core pillars of our mission: -- Improve all aspects of documentation across the Jupyter ecosystem -- Make high quality documentation that is clear, comprehensive, inclusive, and serves the varying needs of Jupyter's diverse community -- Engage with the community to help users with Jupyter products, discover their needs, and connect them with relevant information, expertise and resources +- Improve all aspects of documentation across the Jupyter ecosystem. +- Make high quality documentation that is clear, comprehensive, inclusive, and serves the varying needs of Jupyter's diverse community. +- Engage with the community to help users with Jupyter products, discover their needs, and connect them with relevant information, expertise and resources. The Docs Working Group will provide a place for consistent, focused, holistic efforts to be spent on documentation across the whole ecosystem. This group exists in part to provide capacity and resources to the subprojects (some of which are already suffering from a lack of resources/capacity, and more specifically to work on documentation in particular). @@ -25,9 +25,9 @@ The Docs Working Group is responsible for the following: The Docs Working Group will focus on the efforts described below, in service of its mission: - Help write documentation (inside the bounds of each Subproject's governance) including meta documentation, cross-cutting documentation (items relevant to multiple Subprojects), developer and contributor documentaion, non user-facing documentation and others. -- Develop recommendations and guidance for best practices surrounding documentation authoring, communication of information, concepts and styling to promote consistency across the Jupyter ecosystem. +- Develop recommendations and guidance for best practices surrounding documentation authoring, communication of information, concepts and styling, to promote consistency across the Jupyter ecosystem. - Community engagement to help connect users with information, expertise, and resources; and to gather feedback from the community about what needs to be documented/what information they need. -- Help support and improve all aspects of documentation across the Jupyter ecosystem: our scope also includes any tasks, beyond writing documents, that will support the Doumentation Working Group's goals. To help illustrate the scope of our work, some clarifying examples are included below: +- Help support and improve all aspects of documentation across the Jupyter ecosystem: our scope also includes any tasks - beyond writing documents - that will support the Doumentation Working Group's goals. To help illustrate the scope of our work, some clarifying examples are included below: - Improving the user experience inside Jupyter applications by implementing offline and interactive documentation extensions. - Implementing analytics systems for documentation webpages for better understanding of documentation use. - Any other innovations or work that may improve Jovyans' experience in/understanding of the Jupyter ecosystem. From ef93af2c59ba86a6875e4f0266648b3351bd0656 Mon Sep 17 00:00:00 2001 From: RRosio Date: Fri, 15 Dec 2023 11:35:06 -0800 Subject: [PATCH 10/14] More minor formatting updates. --- charters/DocumentationCharter.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index 34a264fd..b49cccb0 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -17,14 +17,13 @@ We want all users to have positive experiences inside the Jupyter ecosystem, esp The Docs Working Group is responsible for the following: - Setting standards for documentation where needed. -- The Docs working group will take ownership of documentation and related materials not owned by a Subproject (Jupyter.org website and documentation). - +- The Docs working group will take ownership of documentation and related resources not owned by a Subproject (including the Jupyter.org website and documentation). ## Doumentation Working Group's Activities The Docs Working Group will focus on the efforts described below, in service of its mission: -- Help write documentation (inside the bounds of each Subproject's governance) including meta documentation, cross-cutting documentation (items relevant to multiple Subprojects), developer and contributor documentaion, non user-facing documentation and others. +- Help write documentation (inside the bounds of each Subproject's governance) including meta documentation, cross-cutting documentation (items relevant to multiple Subprojects), developer and contributor documentation, non user-facing documentation and others. - Develop recommendations and guidance for best practices surrounding documentation authoring, communication of information, concepts and styling, to promote consistency across the Jupyter ecosystem. - Community engagement to help connect users with information, expertise, and resources; and to gather feedback from the community about what needs to be documented/what information they need. - Help support and improve all aspects of documentation across the Jupyter ecosystem: our scope also includes any tasks - beyond writing documents - that will support the Doumentation Working Group's goals. To help illustrate the scope of our work, some clarifying examples are included below: From aaf0076ccd0022b0d05d6f2a88d7fd8198999831 Mon Sep 17 00:00:00 2001 From: RRosio Date: Fri, 15 Dec 2023 11:46:32 -0800 Subject: [PATCH 11/14] Additional formatting updates. --- charters/DocumentationCharter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index b49cccb0..ccb83563 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -23,7 +23,7 @@ The Docs Working Group is responsible for the following: The Docs Working Group will focus on the efforts described below, in service of its mission: -- Help write documentation (inside the bounds of each Subproject's governance) including meta documentation, cross-cutting documentation (items relevant to multiple Subprojects), developer and contributor documentation, non user-facing documentation and others. +- Help write documentation (inside the bounds of each Subproject's governance) including meta documentation, cross-cutting documentation (items relevant to multiple Subprojects), developer and contributor documentaion, non user-facing documentation and others. - Develop recommendations and guidance for best practices surrounding documentation authoring, communication of information, concepts and styling, to promote consistency across the Jupyter ecosystem. - Community engagement to help connect users with information, expertise, and resources; and to gather feedback from the community about what needs to be documented/what information they need. - Help support and improve all aspects of documentation across the Jupyter ecosystem: our scope also includes any tasks - beyond writing documents - that will support the Doumentation Working Group's goals. To help illustrate the scope of our work, some clarifying examples are included below: From 0adb09e3cbe34d03fd843fa9659a61b0b9cf1426 Mon Sep 17 00:00:00 2001 From: RRosio Date: Fri, 15 Dec 2023 11:50:14 -0800 Subject: [PATCH 12/14] Additional updates to formatting. --- charters/DocumentationCharter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index ccb83563..b49cccb0 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -23,7 +23,7 @@ The Docs Working Group is responsible for the following: The Docs Working Group will focus on the efforts described below, in service of its mission: -- Help write documentation (inside the bounds of each Subproject's governance) including meta documentation, cross-cutting documentation (items relevant to multiple Subprojects), developer and contributor documentaion, non user-facing documentation and others. +- Help write documentation (inside the bounds of each Subproject's governance) including meta documentation, cross-cutting documentation (items relevant to multiple Subprojects), developer and contributor documentation, non user-facing documentation and others. - Develop recommendations and guidance for best practices surrounding documentation authoring, communication of information, concepts and styling, to promote consistency across the Jupyter ecosystem. - Community engagement to help connect users with information, expertise, and resources; and to gather feedback from the community about what needs to be documented/what information they need. - Help support and improve all aspects of documentation across the Jupyter ecosystem: our scope also includes any tasks - beyond writing documents - that will support the Doumentation Working Group's goals. To help illustrate the scope of our work, some clarifying examples are included below: From 5771bb18da9c31bd56f59b224b1aaebb06901415 Mon Sep 17 00:00:00 2001 From: RRosio Date: Fri, 15 Dec 2023 11:54:38 -0800 Subject: [PATCH 13/14] Additional updates to format. --- charters/DocumentationCharter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index b49cccb0..cd70d06d 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -28,7 +28,7 @@ The Docs Working Group will focus on the efforts described below, in service of - Community engagement to help connect users with information, expertise, and resources; and to gather feedback from the community about what needs to be documented/what information they need. - Help support and improve all aspects of documentation across the Jupyter ecosystem: our scope also includes any tasks - beyond writing documents - that will support the Doumentation Working Group's goals. To help illustrate the scope of our work, some clarifying examples are included below: - Improving the user experience inside Jupyter applications by implementing offline and interactive documentation extensions. - - Implementing analytics systems for documentation webpages for better understanding of documentation use. + - Implementing analytics systems for documentation webpages for better understanding of documentation usage. - Any other innovations or work that may improve Jovyans' experience in/understanding of the Jupyter ecosystem. ## Founding Members From d3869c0d6377ec0b2d1c007ddbb8c30c3a2df390 Mon Sep 17 00:00:00 2001 From: RRosio Date: Mon, 8 Jan 2024 11:55:13 -0800 Subject: [PATCH 14/14] additional updates based on feedback --- charters/DocumentationCharter.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/charters/DocumentationCharter.md b/charters/DocumentationCharter.md index cd70d06d..145e4281 100644 --- a/charters/DocumentationCharter.md +++ b/charters/DocumentationCharter.md @@ -17,7 +17,8 @@ We want all users to have positive experiences inside the Jupyter ecosystem, esp The Docs Working Group is responsible for the following: - Setting standards for documentation where needed. -- The Docs working group will take ownership of documentation and related resources not owned by a Subproject (including the Jupyter.org website and documentation). +- The Docs working group will take ownership of documentation and related resources not owned by a Subproject. + - Including the Jupyter.org documentation (under docs.jupyter.org/). ## Doumentation Working Group's Activities