Documenting Working Groups - Community Handbook

book/website/_toc.yml

@@ -697,7 +697,6 @@ parts:
           - title: Ethical Considerations for Open Source Governance Models
             file: ethical-research/ethics-open-source-governance
 
-
       # ===== Community Handbook ========================================
 
       - file: community-handbook/community-handbook
@@ -822,6 +821,17 @@ parts:
                 file: community-handbook/fireside-chat/fireside-chat-roles
           - title: Giving a Turing Way Talk
             file: community-handbook/presenting
+          - title: Working Groups
+            file: community-handbook/working-groups
+            sections:
+              - title: Guidelines for the Working Groups
+                file: community-handbook/working-groups-guideline
+              - title: Formalising a Working Group
+                file: community-handbook/working-groups/working-groups-formalisation
+              - title: Charter Template for the Working Groups
+                file: community-handbook/working-groups/working-groups-charter-template
+              - title: References
+                file: community-handbook/working-groups/working-group-resources   
           - title: Template Collection
             file: community-handbook/templates
             sections:

book/website/community-handbook/working-groups.md

@@ -0,0 +1,46 @@
+(ch-working-groups)=
+# *The Turing Way* Working Groups
+
+A working group (WG) is an organised group or committee within a project, organisation or community.
+WGs are formed for a specific purpose, such as addressing a need or opportunity identified in a project or community. 
+WGs are composed of individuals who bring their interests, expertise, or willingness to engage with a specific topic or context for which the WG is formed.
+WG members collaborate to provide accountability, solve problems and make decisions to achieve the goals set for the group.
+WGs scope can be time-bound (short-term or long-term) or open-ended based on the type of tasks the group is assigned.
+
+WGs are used across many sectors including government, academia, business and nonprofit or volunteer-led organisations to decentralise operations and decision making.
+In open science, many communities carry out their work through established WGs.
+Projects like [Jupyter](https://jupyter.org/governance/standing_committees_and_working_groups.html), [Kubernetes](https://github.com/kubernetes/community/blob/master/governance.md), [Eclipse Foundation](https://www.eclipse.org/org/workinggroups/process.php#wg-member-roles), [Sustain OSS](https://sustainoss.org/working-groups/), [The Carpentries](https://carpentries.org/) and [CHAOSS](https://chaoss.community/cgi-sys/suspendedpage.cgi) are few examples where WGs have been organised to ensure timely and open engagement with their communities.
+
+Within *The Turing Way*, WGs are formed by a small groups of people who work together on specific topics, themes, or types of work identified by community members as areas of interest. 
+From the onset, different kinds of work in *The Turing Way* project have been led and executed by different groups of people.
+For example, since 2020, localisation and translation work is being carrying out by a group international community members, who although initially worked in an ad-hoc manner, later were named and recognised as 'Translation and Localisation Team'.
+Similarly, in 2021, after moving Book Dash as online-first event, a 'Book Dash Planning Committee' was convened yearly joined by a few previous attendees of Book Dashes who supported the planning and delivery of the event.
+Nonetheless, formation of WGs had largely remained informal: after existing streams of work had been identified, community members engaged with the work were formally recognised and encouraged to develop ways of working that align with their needs. 
+
+However, as the community has grown, creating explicit pathways for formalising WGs is the only way for ensuring that everyone has the same opportunity to navigate and benefit from structure that WGs provide.
+We also recognise that lack of guidance leads to the [tyranny of structurelessness](https://www.jofreeman.com/joreen/tyranny.htm), where navigating information may be easier for people who have been involved from the beginning, the uncertainty of roles and responsibilities can ultimately exclude those who don't have direct contact with the project team.
+
+In *The Turing Way*, the formalisation of WGs started in 2022.
+The current research community manager of the project started her familiarity with the project through community mapping work in 2022.
+The goals were to (1) formalise already existing and ongoing work within the community, and (2) support new areas of work that could address the observed and documented needs of the project and community.
+
+We believe that everyone in *The Turing Way* community has expertise to share, and thereby anyone can join our project and community.
+We describe different ways to contribute to the project in our [contribution guideline](https://github.com/the-turing-way/the-turing-way/blob/main/CONTRIBUTING.md).
+Similarly, we encourage anyone who would like to join an existing WG to reach out to the specific chairs and leads of those group ({ref}`find details of our current WG<subprojects>`).
+
+While anyone who joins *The Turing Way* can attend a WG meeting and join the WG, joining a WG is **not** a requirement for engaging with *The Turing Way*.
+
+We have also been hosting _The Turing Way_ Community Forums where WG members share updates and provide resources for the community members to get involved ([recordings on our YouTube channel](https://www.youtube.com/theturingway)).
+
+For informal groups that are interested in formalising their work, developing a working group offers an opportunity for groups to benefit from formalised support from *The Turing Way* team, as well as to openly get recognition for their work within the community.
+However, there are a few requirements for community members to *create* a working group, process and documentation for which is provided in this chapter. 
+
+With information shared in this chapter, we want to ensure that community members can identify infrastructure and support they need, as well as ways to sustain WGs' efforts.
+A standard approach for establishing and managing WG will also allow *The Turing Way* leadership and project delivery team to provide the oversight and support needed to bring cohesiveness across all WGs and align WGs goals with the project's overarching goals.
+
+The process described in this chapter adheres to our commitment to ensuring transparency and engagement with our community.
+For WGs this means that our community members are informed of the WGs work and can participate openly, ensuring critical mass required to establish, maintain and sustain a WG.
+
+In addition to {ref}`guidelines<ch-working-groups-guidelines>` and {ref}`process for formalising a WG<ch-working-groups-formalising>`, we provide {ref}`a template<ch-working-groups-charter-template>` (in the final subchapter) for interested members of the community to self-organise, incubate, maintain, and/or eventually sunset a working group. 
+This document, as is the case with *The Turing Way* guides themselves is a living document.
+Please help us keep this updated as the community and its governance evolves.

book/website/community-handbook/working-groups/working-group-resources.md

@@ -0,0 +1,26 @@
+# References
+
+The following resources were used in drafting and creation of templates for this documentation:
+
+* Gitlab: [Working Groups](https://about.gitlab.com/company/team/structure/working-groups/)
+* The Carpentries: [Executive Council's Standing Committees](https://docs.carpentries.org/topic_folders/governance/executive-council.html#executive-council-s-standing-committees)
+* OLS (Open Life Science): [OLS Working Groups](https://docs.google.com/document/d/1EUHvYv5wvZiJSK4yYDwwDHs9Ds6tCjqB3XezqCaetEI/edit#)
+* Project Jupyter Governance: [Standing Committees and Working Groups](https://jupyter.org/governance/standing_committees_and_working_groups.html)
+* HOTOSM: [Humanitarian OSM Team Working Groups](https://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Team/Working_groups)
+* Kubernetes: [Community Governance](https://github.com/kubernetes/community/blob/master/governance.md)
+* Decidim: [Our Governance](https://meta.decidim.org/assemblies/our-governance)
+* Open Life Science: [Open Life Science Charter](https://docs.google.com/document/d/1pD_P8oKLenyxCM39PZxu3X8a6hZQ4jZi-fA-xBB3DXQ/edit#heading=h.gjdgxs)
+* Django: [Django Internals Organization](https://docs.djangoproject.com/en/dev/internals/organization/)
+* Social.coop: [Governance](https://wiki.social.coop/wiki/Governance)
+* Brockwell Greenhouses: [Governance at BPCG](https://www.brockwellgreenhouses.org.uk/governance-at-bpcg/)
+* data.coop (danish): [Data.coop Governance](https://data.coop/#)
+* Code for Science & Society: [Fiscal Sponsorship Model](https://www.codeforscience.org/)
+* HOT OpenStreetMap: [HOT Working Groups Governance](https://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Team/Working_groups/Governance)
+* Wikipedia: [Wikimedia Foundation](https://foundation.wikimedia.org/wiki/Home)
+* Pyladies: [PyLadies Global Council](https://pyladies.com/blog/Announcing-the-Inaugural-PyLadies-Global-Council/inaugural-pyladies-council/)
+* Wikipedia Education WG: [Wikipedia Education Working Group](https://en.wikipedia.org/wiki/Wikipedia:Education_Working_Group)
+* Eclipse: [Eclipse Working Groups Process](https://www.eclipse.org/org/workinggroups/process.php)
+* IEEE SA: [Mobilizing Working Group](https://standards.ieee.org/develop/mobilizing-working-group/governedwg/)
+* W3C: [Working Group Charter](https://www.w3.org/Guide/process/charter.html)
+* Loomio: [Working Groups](https://www.loomio.coop/working_groups.html)
+* Metaarchive: [Metaarchive Charter 2021](https://metaarchive.org/wp-content/uploads/2021/06/ma_charter_2021.pdf)