Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial thoughts on WG process #54

Open
wants to merge 12 commits into
base: main
Choose a base branch
from
70 changes: 70 additions & 0 deletions governance/working groups/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,70 @@
# Working groups

For the UK TRE Community, a Working Group (WG) is the main method through which community outputs are created.
harisood marked this conversation as resolved.
Show resolved Hide resolved

WGs can be set up by any member of the community, and are focused on producing specific, tangible outputs within a given time period, and are modelled off the pre-existing concept of Working Groups found in communities like [DARE UK](https://dareuk.org.uk/dare-uk-launches-dynamic-collaborative-communities-invites-proposals-for-new-groups/), the [Research Data Alliance (RDA)](https://www.rd-alliance.org/groups/creating-and-managing-rda-groups/creating-or-joining-rda-working-group.html), the [W3C](https://www.w3.org/2017/Process-20170301/#GAGeneral) and more.
harisood marked this conversation as resolved.
Show resolved Hide resolved

There are two distinct processes for those considering creating WGs to consider:
harisood marked this conversation as resolved.
Show resolved Hide resolved
1. The establishment of the WG
2. The community endorsement of the WG outputs
harisood marked this conversation as resolved.
Show resolved Hide resolved

As the UK TRE community's primary focus is to act as a signposting and convening body for the TRE space in the UK and beyond, we have made a conscious effort to separate out the questions of:
- Work that is happening within the community (WG establishment)
- Outputs/resources for which there is community consensus and endorsement (community endorsement)
harisood marked this conversation as resolved.
Show resolved Hide resolved

Therefore it is important to note that establishing a WG with the UK TRE community **does not** imply any outputs of the WG are endorsed by the UK TRE Community.


## Process
### Establishing a Working group

1. Member(s) suggesting a working group fill in the [Working Group Charter](working-group-charter.md).
2. The Charter is reviewed by the [Steering Group]() to ensure it:
harisood marked this conversation as resolved.
Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. The Charter is reviewed by the [Steering Group]() to ensure it:
2. The Charter is reviewed by the [Steering Group](governance/steering group/steering_group.md) to ensure it:

- Aligns with [community principles]()
- Represents new work being undertaken in the community
3. If the Charter is rejected by the [Steering Group](), feedback is provided to the submitting member(s) on why, and the Working Group returns to step 1.
4. If the Charter is approved by the [Steering Group](), the Charter is made available for community review via an Issue on the [UK TRE GitHub](https://github.com/uk-tre/community-management) for a period of 2 weeks.
harisood marked this conversation as resolved.
Show resolved Hide resolved
harisood marked this conversation as resolved.
Show resolved Hide resolved
5. If, after a period of 2 weeks, there are no unresolved objections to the Charter, the working group is established :tada:
harisood marked this conversation as resolved.
Show resolved Hide resolved
6. If there are unresolved objections, these are reviewed by the [Steering Group](). Any outstanding objections requiring review after this are collated and shared with the Working Group proposers for updating the charter, and the Working Group returns to step 4.
harisood marked this conversation as resolved.
Show resolved Hide resolved
7. Once a Working Group is established, they are formally recognised on the [UK TRE Community website](https://www.uktre.org/), and the community is notified of its creation.

### Endorsing Working Group outputs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Endorsing Working Group outputs
### Sharing Working Group outputs


1. When a WG has outputs ready to share with the community, they notify the [Steering Group]()
2. The draft outputs are reviewed by the [Steering Group]() to ensure it:
- Aligns with [community principles]()
3. If approved by the [Steering Group](), the draft outputs are made available for community review via an Issue on the [UK TRE GitHub](https://github.com/uk-tre/community-management) for a period of 4 weeks.
harisood marked this conversation as resolved.
Show resolved Hide resolved
harisood marked this conversation as resolved.
Show resolved Hide resolved
4. At the end of this 4 week period, 3 outcomes are possible:

#### Rejection
The community rejects the draft outputs of the WG.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#### Rejection
The community rejects the draft outputs of the WG.
#### Rejection
The community rejects the draft outputs of the WG.


The [Steering Group]() will collate the reasons for rejection and share these with the WG.
The WG can decide to either close out the working group, or amend the outputs to resolve any reasons for rejection.

#### Approved for distribution
The community approves the outputs for distribution.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#### Approved for distribution
The community approves the outputs for distribution.
#### Approved for distribution
The community approves the outputs for distribution.


The UK TRE community will signpost to the outputs, but will not specifically endorse them.
The WG can decide to either close out the working group, or amend the outputs to work towards endorsement.

#### Approved and endorsed
Davsarper marked this conversation as resolved.
Show resolved Hide resolved
The community approves the outputs for distribution, and explicitly endorses them.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#### Approved and endorsed
The community approves the outputs for distribution, and explicitly endorses them.
#### Approved and endorsed
The community approves the outputs for distribution, and explicitly endorses them.


The UK TRE community will signpost to the outputs, and formally endorse them publicly.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have we defined what it means to "endorse" something?


The WG outputs will be tagged with a version referencing this endorsement.
If the WG wants to amend/update these outputs, they will have to go through the endorsement process above again.
No future versions beyond the tagged version are guaranteed to be endorsed by the community.


### Closing a Working Group

1. The Working group completes the [Working Groups closure form]() confirming its termination.
2. The [Steering Group]() reviews this form, and when approved, lists this working group under `Historical Working Groups`.

### Recommendations
In order to maximise the chance of community endorsement for Working Group outputs, we recommend all working groups:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Recommendations
In order to maximise the chance of community endorsement for Working Group outputs, we recommend all working groups:
### Recommendations
In order to maximise the chance of community endorsement for Working Group outputs, we recommend all working groups:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may need to do more than recommend, updates and contribution mechanisms should be mandatory. And recommend that if any pushback/dissenting opinions exist in the community then special attention is put to include them

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree but where do you think this stuff belongs? Probs not here (these are softer 'best practice' recommendations.

I guess if they are ignoring dissenting opinions that will be picked up by the Steering Group in their formal review?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't remember I had already made this point haha, I actually think this is a good place to include rather than have a separate document on best practices or recommendations on making a succesful output. This is the document all WGs will go through (or the charter), if not here then in the output approval process? I think it is worth formally mentioning that part of the community review is including (or at elast considering) its recommendations

- Share regular updates with the wider community, to ensure co-creation and allow amendments to happen live, rather than at the end
- To carefully consider the scope, and target outputs, based on community feedback. If specific suggested outputs face pushback, are there higher level outputs that are more reflective of what the community needs?
- To carry out informal reviews of outputs with the community regularly, before requesting formal review.
38 changes: 38 additions & 0 deletions governance/working groups/working-group-charter.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# Working group charter template

## Overview

This section should summarise in one or two paragraphs the Working group proposal, for any community member to read and quickly grasp the essence of the WG.

## Background

This section should dive into more detail on what the WG aims to address, why it is undertaking this work, and reference any background material/pre-existing work that this proposal builds on.

## Target outputs
This section should contain the target outputs of the WG

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Target outputs
This section should contain the target outputs of the WG
## Target outputs
This section should contain the target outputs of the WG.


## Meeting mechanisms
This section should include details on how, where and when the WG intends to meet
harisood marked this conversation as resolved.
Show resolved Hide resolved

## Communication mechanisms
This section should outline how the WG intends to communicate progress with its members, the UK TRE Community more widely, and any other interested stakeholders.
harisood marked this conversation as resolved.
Show resolved Hide resolved
harisood marked this conversation as resolved.
Show resolved Hide resolved

## Working Group roles
This section should outline the different roles within the Working Group. Examples include:
- **Chairs**: Leaders of the WG
- **Contact**: Primary contact for the WG
harisood marked this conversation as resolved.
Show resolved Hide resolved
- **Participating members**: Members who are undertaking work within the Working Group
harisood marked this conversation as resolved.
Show resolved Hide resolved

## Getting involved

This section should detail how interested parties can get involved with joining the WG.

It should also detail expected weekly time commitment for defined roles above

## Agreement
*Please submit this charter with all boxes checked below*
harisood marked this conversation as resolved.
Show resolved Hide resolved

By submitting this charter, this working group agrees to:
- [ ] Share any outputs openly under a [CC BY 4.0 licence](https://creativecommons.org/licenses/by/4.0/)
harisood marked this conversation as resolved.
Show resolved Hide resolved
- [ ] Allow participation from any interested parties
- [ ] Report on progress at each quarterly community meeting for the duration of the Working Group