Create a Shared Drive and Roster Sheet for CoP and their Leads

[ghost]

Dependency

Oh Hold until guides issue is done #14, then rethink this issue

Overview

We need to create a shared drive for the Community of Practice repository.

Action Items

• Create a shared drive for the Communities of Practice repository and invite all the members.
• Create a folder for the roster under this shared drive and add members from all their rosters.
• Request CoP leads to move their rosters to this shared drive.
• Give access to Gautham.
• Ask CoP leads to get leads to update their current roster and then let us know and post a comment here in this issue with link to the roster and that it has been updated.
• Update Gautham once the above checklists are done, through this issue as comments.

Resources/Instructions

• Roster Sheet for CoP Leads under CoP shared drive
• Community of Practice repository
• Notes provided to create the issue
• Community of Practice Shared Drive

[ghost]

Raw notes provided by Bonnie through Zoom chat to create this issue

• make a drive for the Communities of Practice repo
• add a roster to it
• add all the people from all their rosters onto it
• give Gautham access
• let cop leads know to keep it updated
• let Gautham know once I am done on my issue

[ExperimentsInHonesty]

• create a CoP leads roster from the roster copies in this folder https://drive.google.com/drive/folders/13eIpiD-Ff1hBi2f39oOhbWaPH2tKCXUg
• Confer at next guides meeting to confirm that its accurate
• reach out to CoP leads in our new roster, ask them for any names of co leads
• add co-leads from individual rosters to the combined roster.

Resources/Instructions

• Roster Sheet for CoP Leads under CoP shared drive

[ghost]

Created a roster sheet for Community of Practice Leads. Need to confirm formatting, fields to include and order of the fields as the roster format differs from team to team.

[ExperimentsInHonesty]

I will remove the shared drive for Communities of Practice because we have made a decision to have each CoP have its own drive and we will just make shortcuts to them

[ExperimentsInHonesty]

Hi Community of Practice Leader,

The Guides team needs you to update your Community of Practice roster with some information missing from your leaders rows (potentially yours and your coleads). We need all info from Name to linkedin profiles (and everything in between). Please post a link to your roster on this issue, when you have updated.

[ghost]

Tagged / Mentioned Team leads of these channels - UI/UX, Marketing, Data Science, Fundraising and Engineering with GitHub issue link below.

Hi Community of Practice Leader,

The Guides team needs you to update your Community of Practice roster with some information missing from your leaders rows (potentially yours and your coleads). We need all info from Name to linkedin profiles (and everything in between). Please post a link to your roster on this issue, when you have updated.

[ExperimentsInHonesty]

@gautham-l please update the Product roster to indicate Olivia, Bonnie And Ebele are the leaders of the Product Community of Practice
@DaTa science is Sophia and Ryan Swan

[ghost]

This issue was created under Bonnie's request (notes for reference). The plan was

1. To create a Shared drive folder for Community of Practice.
2. Move existing CoP rosters to this folder.
3. Create a roster sheet only for CoP leads.

We decided to create a roster for CoP leads so that we can give access to Shared drive whenever required.

[ghost]

@gautham-l please update the Product roster to indicate Olivia, Bonnie And Ebele are the leaders of the Product Community of Practice
@DaTa science is Sophia and Ryan Swan

Need more clarification regarding this comment.

[ghost]

Hi Community of Practice Leader,

The Guides team needs you to update your Community of Practice roster with some information missing from your leaders rows (potentially yours and your coleads). We need all info from Name to linkedin profiles (and everything in between). Please post a link to your roster on this issue, when you have updated.

Qiqi Zheng from the Engineering team responded to this message posted on slack.