hackforla / hackforla/google-drive-migration

Product Manager Out Reach

Open
#62 0 comments 0 reactions 0 assignees View on GitHub
dependency epic role: project
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

### Dependency
- [ ] **50% of the projects have the** `status: ready for invite` **label.** The way to get this number is:
A. get the total number of [open issues with `feature: Google Drive Migration` label](https://github.com/hackforla/google-drive- migration/issues?q=is%3Aissue+is%3Aopen+label%3A%22feature%3A+Google+Drive+Migration%22)
B. divide by 2
C. get the total number of [open issues with `status: ready for invite` label](https://github.com/hackforla/google-drive-migration/issues?q=is%3Aissue+is%3Aopen+label%3A%22feature%3A+Google+Drive+Migration%22+label%3A%22status%3A+ready+for+invite%22)
D. Is C>=B

### Overview
We need to decide how we are going to involve the PMs in helping with the drive migration.

### Action Items
- [ ] Review prior notes about how to engage with them
- [ ] Decide what to do
- [ ] Decide how to do it
- [ ] Write next steps

### Prior Notes
- [ ] Engage with product managers
- [ ] Make sure all necessary people are added to the new shared drive (below)
- [ ] Once added, confirm information in worksheet
- [ ] Ask PM to comment their meeting times on this issue
- [ ] Show pm demo of file migration and how to use spreadsheet and teach them permissions
- [ ] Ask product manager if they are able to communicate with old members to get files moved
- [ ] If yes, then assign them the issue
- [ ] Once files moved, close issue with a comment

### Resources/Instructions
- #3
- #61

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.