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

Proposal for Community communication and working spaces #40

Closed
6 tasks
Davsarper opened this issue Nov 28, 2023 · 7 comments · Fixed by #42
Closed
6 tasks

Proposal for Community communication and working spaces #40

Davsarper opened this issue Nov 28, 2023 · 7 comments · Fixed by #42
Assignees
Labels
governance How the community is run

Comments

@Davsarper
Copy link
Contributor

Davsarper commented Nov 28, 2023

Detail

Create a proposal on how we want to use each space: chiefly jisc mailing list, any other lists, slack

  • Are we pointing people to the slack space now? As a workign or general discussion space
  • Are we creating an announcements separate list? Can we achieve the same just with jisc setting?

To be done this week, discuss async and ratify next Tuesday

Actions

  • Sketch proposal here or slack, Hari and David
  • Communicate to chairs and CMWG members
  • Decide together
  • Put it in writing to present at event
  • Once approved update the related document
  • Add document to website

Who can help

@manics @harisood @hardakerm @balintstewart77

@Davsarper Davsarper added the governance How the community is run label Nov 28, 2023
@Davsarper Davsarper self-assigned this Nov 28, 2023
@harisood
Copy link
Member

I think we should make the Slack the communication hub (with e.g. separate channels for different working groups etc.), with the Jisc mailing list being used for announcements and base-level comms channel. I would want to avoid people leaving the community because they're getting too many emails

@manics
Copy link
Member

manics commented Nov 28, 2023

I think we should create a new announcements list, and keep the existing list unchanged:
#14 (comment)

@Davsarper Davsarper linked a pull request Nov 28, 2023 that will close this issue
@harisood
Copy link
Member

Let's ask this at the meeting - last time people said it'd be overkill, we can ask again if it now feels appropriate

@manics
Copy link
Member

manics commented Nov 28, 2023

How are we going to present this? We know there's a problem, we also know that not everyone is going to speak up, so we need to present the background/reasoning too and not just the proposal.

@harisood
Copy link
Member

How are we going to present this?

"Present the background/reasoning too and not just the proposal"

Question and answer in same comment 😅

@Davsarper
Copy link
Contributor Author

Davsarper commented Nov 28, 2023

last time people said it'd be overkill

Actually, this is why we decided to bring it to the event. Some people answered it would be overkill, most did not answer and a few left. Assuming the feedback was not to create the list is listening to only a few voices.
The CMWG majority still thought an announcement list would be best.

@Davsarper
Copy link
Contributor Author

This conversation is splitting in too many ways, it is clear (I think) we want to ask about the announcement lists but also about the overall proposal for spaces (?). So, do we reference this proposal/issue or #14 during the Dec event?
I would say this proposal, which I then should finalise today. The rest of the CMWG should chime in, take it to slack?

@Davsarper Davsarper changed the title Proposal for Community communicaiton and working spaces Proposal for Community communication and working spaces Nov 29, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in TRE Community - project board Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
governance How the community is run
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants