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.

Sign up for GitHub

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

Jump to bottom

Onboard & Offboard: Product #2688

Open
3 tasks
ExperimentsInHonesty opened this issue Jan 16, 2022 · 91 comments
Open
3 tasks

Onboard & Offboard: Product #2688

ExperimentsInHonesty opened this issue Jan 16, 2022 · 91 comments
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Dependency An issue is blocking the completion or starting of another issue Feature: Onboarding/Contributing.md manual dependency release role: product Product Management size: 0.5pt Can be done in 3 hours or less
Milestone
08. Team workflow

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jan 16, 2022 •
edited
Loading

Dependency

  • Onboarding a new pm

Overview

We need to have a checklist of items to do when a product manager onboard and offboards so that the process can be consistent and fast.

Action Items

  • Copy template to comment below
  • Add name of person
  • Check off as done
#### Onboard
- [ ] Google Drive
   - [ ] Add to drive as Manager
- [ ] Roster
  - [ ] Send link
  - [ ] Team member adds themselves
  - [ ] Check for Public
- [ ] GitHub Teams
     - [ ] Add GitHub Handle to read team
        - [ ] Change membership to maintainer
     - [ ] Add to GitHub Handle to write team
        - [ ] Change membership to maintainer
     - [ ] Add to GitHub Handle to PM team
        - [ ] Change membership to maintainer
- [ ] Figma
  - [ ] invite
  - [ ] acceptance
- [ ] 1password 
     - [ ] invitation
     - [ ] acceptance
     - [ ] add to vaults
       - [ ] hackforla.org website vault
       - [ ] Zoom vault
           - [ ] send them a link to the zoom spreadsheet and confirm that they have editing rights.  If they don't, add them to the project management community of practice drive.
- [ ] Train how to 
   - [ ] login to team email account
   - [ ] setup chrome extension shortcut (chrome profile for email account)
   - [ ] use zoom spreadsheet, vault and accounts
   - [ ] calendar invite
- [ ] Gmail
   - [ ] set up forwarder to add personal email address
   - [ ] set up filter to forward all incoming mail from website@hackforla.org to personal email
- [ ] HFLA Project team
   - [ ] Add to HFLA website project page https://www.hackforla.org/projects/website  by opening a new issue
- [ ] VRMS
   - [ ] Add PM Admin Access on VRMS

#### Offboard
  - [ ] 1password setup
    - [ ] remove from team vaults
       - [ ] hackforla.org website vault
       - [ ] Zoom vault
- [ ] Google Drive
   - [ ] demote to viewer
- [ ] Roster
  - [ ] mark as inactive
- [ ] GitHub
     - [ ] demote member to read only team and remove from write team
- [ ] Figma
  - [ ] remove from team
- [ ] Gmail
   - [ ] remove filter to forward all incoming mail from website@hackforla.org to personal email
   - [ ] remove forwarder to add personal email address
- [ ] HFLA Project team
   - [ ] Remove from HFLA website project page https://www.hackforla.org/projects/website
- [ ]  VRMS
   - [ ] Remove PM Admin Access on VRMS

Resources/Instructions

to do things

Change someone to Maintainer on a GitHub Team

Select the person or people you'd like to promote to team maintainer.

Above the list of team members, use the drop-down menu and click Change role....

Select a new role, then click Change role.
@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Jan 16, 2022
@ExperimentsInHonesty ExperimentsInHonesty added size: 0.5pt Can be done in 3 hours or less role: product Product Management Feature: Onboarding/Contributing.md and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Jan 16, 2022
@Providence-o Providence-o self-assigned this Jan 23, 2022
@Providence-o

This comment was marked as outdated.

Sign in to view
Open
2 tasks
@ExperimentsInHonesty
Copy link
Member Author

Perform offboarding to all people marked as inactive on roster

@ExperimentsInHonesty ExperimentsInHonesty added Feature Missing This label means that the issue needs to be linked to a precise feature label. Feature: Onboarding/Contributing.md and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. labels Mar 1, 2022
@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Mar 18, 2022
@hackforla hackforla deleted a comment from phuonguvan Mar 27, 2022
@hackforla hackforla deleted a comment from github-actions bot Sep 4, 2022
@hackforla hackforla deleted a comment from github-actions bot Sep 4, 2022
@hackforla hackforla deleted a comment from github-actions bot Sep 4, 2022
@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Sep 4, 2022 •
edited
Loading

Onboard Akram 2022-09-04

  • Google Drive
    • Add to drive as Manager
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub Teams
    • Add to read team
      • Change membership to maintainer
    • Add to team write
      • Change membership to maintainer
    • Add to PM team
      • Change membership to maintainer
  • Figma
    • invite
    • acceptance
  • 1password
    • invitation
    • acceptance
    • add to vaults
      • hackforla.org website vault
      • Zoom vault
  • Train how to
    • login to team email account
    • setup chrome extension shortcut (chrome profile for email account)
    • use zoom spreadsheet, vault and accounts
    • calendar invite
  • Gmail
    • set up forwarder to add personal email address
    • set up filter to forward all incoming mail from website@hackforla.org to personal email
  • HFLA Project team

@hackforla hackforla deleted a comment from github-actions bot Sep 4, 2022
@hackforla hackforla deleted a comment from github-actions bot Sep 4, 2022
@hackforla hackforla deleted a comment from github-actions bot Sep 4, 2022
@hackforla hackforla deleted a comment from github-actions bot Sep 4, 2022
@github-actions GitHub Actions
Copy link

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, December 18, 2023 at 11:06 PM PST.

@github-actions GitHub Actions
Copy link

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, December 25, 2023 at 11:06 PM PST.

@github-actions GitHub Actions
Copy link

github-actions bot commented Jan 5, 2024

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 1, 2024 at 11:06 PM PST.

@github-actions GitHub Actions
Copy link

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 8, 2024 at 11:05 PM PST.

@github-actions GitHub Actions
Copy link

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 15, 2024 at 11:06 PM PST.

@github-actions GitHub Actions
Copy link

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 22, 2024 at 11:05 PM PST.

@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 2, 2024

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 29, 2024 at 11:06 PM PST.

@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 9, 2024

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, February 5, 2024 at 11:06 PM PST.

@github-actions GitHub Actions
Copy link

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, February 12, 2024 at 11:05 PM PST.

@github-actions GitHub Actions
Copy link

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, February 19, 2024 at 11:06 PM PST.

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 1, 2024

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, February 26, 2024 at 11:06 PM PST.

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 8, 2024

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, March 4, 2024 at 11:06 PM PST.

@github-actions GitHub Actions
Copy link

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, March 12, 2024 at 12:06 AM PST.

@github-actions GitHub Actions
Copy link

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, March 19, 2024 at 12:06 AM PST.

@github-actions GitHub Actions

This comment was marked as outdated.

Sign in to view
@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Apr 1, 2024 •
edited
Loading

Onboard 2024-04-01 Kelly Chuang

  • Google Drive
    • Add to drive as Manager
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub Teams
    • Add GitHub Handle to read team
      • Change membership to maintainer
    • Add to GitHub Handle to write team
      • Change membership to maintainer
    • Add to GitHub Handle to PM team
      • Change membership to maintainer
  • Figma
    • invite
    • acceptance
  • 1password
    • invitation
    • acceptance
    • add to vaults
      • hackforla.org website vault
      • Zoom vault
        • add to zoom spreadsheet as editor
  • Train how to
    • login to team email account
    • setup chrome extension shortcut (chrome profile for email account)
    • use zoom spreadsheet, vault and accounts
    • calendar invite
  • Gmail
    • set up forwarder to add personal email address
    • set up filter to forward all incoming mail from website@hackforla.org to personal email
  • HFLA Project team

@ExperimentsInHonesty ExperimentsInHonesty removed their assignment Apr 2, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Dependency An issue is blocking the completion or starting of another issue and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Apr 2, 2024
@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jun 5, 2024 •
edited
Loading

Onboard 2024-06-05 Yugma

  • Google Drive
    • Add to drive as Manager
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub Teams
    • Add GitHub Handle to read team
      • Change membership to maintainer
    • Add to GitHub Handle to write team
      • Change membership to maintainer
    • Add to GitHub Handle to PM team
      • Change membership to maintainer
  • Figma
    • invite
    • acceptance
  • 1password
    • invitation
    • acceptance
    • add to vaults
      • hackforla.org website vault
      • Zoom vault
        • send them a link to the zoom spreadsheet and confirm that they have editing rights. If they don't, add them to the project management community of practice drive.
  • Train how to
    • login to team email account
    • setup chrome extension shortcut (chrome profile for email account)
    • use zoom spreadsheet, vault and accounts
    • calendar invite
  • Gmail
    • set up forwarder to add personal email address
    • set up filter to forward all incoming mail from website@hackforla.org to personal email
  • HFLA Project team

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jul 2, 2024 •
edited
Loading

Onboard Eleftherios 2024-07-02

  • Google Drive
    • Add to drive as Manager
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub Teams
    • Add GitHub Handle to read team
      • Change membership to maintainer
    • Add to GitHub Handle to write team
      • Change membership to maintainer
    • Add to GitHub Handle to PM team
      • Change membership to maintainer
  • Figma
    • invite
    • acceptance
  • 1password
    • invitation
    • acceptance
    • add to vaults
      • hackforla.org website vault
      • Zoom vault
        • send them a link to the zoom spreadsheet and confirm that they have editing rights. If they don't, add them to the project management community of practice drive.
  • Train how to
    • login to team email account
    • setup chrome extension shortcut (chrome profile for email account)
    • use zoom spreadsheet, vault and accounts
    • calendar invite
  • Gmail
    • set up forwarder to add personal email address
    • set up filter to forward all incoming mail from website@hackforla.org to personal email
  • HFLA Project team

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Aug 7, 2024 •
edited
Loading

Onboard Mayank Tibrewal 2024-08-07

  • Google Drive
    • Add to drive as Manager
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub Teams
    • Add GitHub Handle to read team
      • Change membership to maintainer
    • Add to GitHub Handle to write team
      • Change membership to maintainer
    • Add to GitHub Handle to PM team
      • Change membership to maintainer
  • Figma
    • invite
    • acceptance
  • 1password
    • invitation
    • acceptance
    • add to vaults
      • hackforla.org website vault
      • Zoom vault
        • send them a link to the zoom spreadsheet and confirm that they have editing rights. If they don't, add them to the project management community of practice drive.
  • Train how to
    • login to team email account
    • setup chrome extension shortcut (chrome profile for email account)
    • use zoom spreadsheet, vault and accounts
    • calendar invite
  • Gmail
    • set up forwarder to add personal email address
    • set up filter to forward all incoming mail from website@hackforla.org to personal email
  • HFLA Project team
  • VRMS
    • Add to VRMS

@mayankt153
Copy link
Member

mayankt153 commented Aug 19, 2024 •
edited
Loading

Onboard Eleftherios Christou 2024-08-19

  • Google Drive
    • Add to drive as Manager
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub Teams
    • Add GitHub Handle to read team
      • Change membership to maintainer
    • Add to GitHub Handle to write team
      • Change membership to maintainer
    • Add to GitHub Handle to PM team
      • Change membership to maintainer
  • Figma
    • invite
    • acceptance
  • 1password
    • invitation
    • acceptance
    • add to vaults
      • hackforla.org website vault
      • Zoom vault
        • send them a link to the zoom spreadsheet and confirm that they have editing rights. If they don't, add them to the project management community of practice drive.
  • Train how to
    • login to team email account
    • setup chrome extension shortcut (chrome profile for email account)
    • use zoom spreadsheet, vault and accounts
    • calendar invite
  • Gmail
    • set up forwarder to add personal email address
    • set up filter to forward all incoming mail from website@hackforla.org to personal email
  • HFLA Project team
  • VRMS
    • Add PM Admin Access on VRMS

@mayankt153
Copy link
Member

mayankt153 commented Aug 19, 2024 •
edited
Loading

Onboard Samhitha Kamma 2024-08-19

  • Google Drive
    • Add to drive as Manager
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub Teams
    • Add GitHub Handle to read team
      • Change membership to maintainer
    • Add to GitHub Handle to write team
      • Change membership to maintainer
    • Add to GitHub Handle to PM team
      • Change membership to maintainer
  • Figma
    • invite
    • acceptance
  • 1password
    • invitation
    • acceptance
    • add to vaults
      • hackforla.org website vault
      • Zoom vault
        • send them a link to the zoom spreadsheet and confirm that they have editing rights. If they don't, add them to the project management community of practice drive.
  • Train how to
    • login to team email account
    • setup chrome extension shortcut (chrome profile for email account)
    • use zoom spreadsheet, vault and accounts
    • calendar invite
  • Gmail
    • set up forwarder to add personal email address
    • set up filter to forward all incoming mail from website@hackforla.org to personal email
  • HFLA Project team
  • VRMS
    • Add PM Admin Access on VRMS

@Samhitha444
Copy link
Member

Samhitha444 commented Aug 19, 2024 •
edited
Loading

Onboard Venkatasai Poorna Tushara Chada 2024-08-19

  • Google Drive
    • Add to drive as Manager
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub Teams
    • Add GitHub Handle to read team
      • Change membership to maintainer
    • Add to GitHub Handle to write team
      • Change membership to maintainer
    • Add to GitHub Handle to PM team
      • Change membership to maintainer
  • Figma
    • invite
    • acceptance
  • 1password
    • invitation
    • acceptance
    • add to vaults
      • hackforla.org website vault
      • Zoom vault
        • send them a link to the zoom spreadsheet and confirm that they have editing rights. If they don't, add them to the project management community of practice drive.
  • Train how to
    • login to team email account
    • setup chrome extension shortcut (chrome profile for email account)
    • use zoom spreadsheet, vault and accounts
    • calendar invite
  • Gmail
    • set up forwarder to add personal email address
    • set up filter to forward all incoming mail from website@hackforla.org to personal email
  • HFLA Project team
  • VRMS
    • Add PM Admin Access on VRMS

@mayankt153
Copy link
Member

mayankt153 commented Sep 15, 2024 •
edited by ExperimentsInHonesty
Loading

Onboard Sofiat Ajide 2024-09-15

  • Google Drive
    • Add to drive as Manager
  • Roster
    • Send link
    • Team member adds themselves
    • Check for Public
  • GitHub Teams
    • Add GitHub Handle to read team
      • Change membership to maintainer
    • Add to GitHub Handle to write team
      • Change membership to maintainer
    • Add to GitHub Handle to PM team
      • Change membership to maintainer
  • Figma
    • invite
    • acceptance
  • 1password
    • invitation
    • acceptance
    • add to vaults
      • hackforla.org website vault
      • Zoom vault
        • send them a link to the zoom spreadsheet and confirm that they have editing rights. If they don't, add them to the project management community of practice drive.
  • Train how to
    • login to team email account
    • setup chrome extension shortcut (chrome profile for email account)
    • use zoom spreadsheet, vault and accounts
    • calendar invite
  • Gmail
    • set up forwarder to add personal email address
    • set up filter to forward all incoming mail from website@hackforla.org to personal email
  • HFLA Project team
  • VRMS
    • Add PM Admin Access on VRMS

@t-will-gillis t-will-gillis mentioned this issue Oct 21, 2024
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Dependency An issue is blocking the completion or starting of another issue Feature: Onboarding/Contributing.md manual dependency release role: product Product Management size: 0.5pt Can be done in 3 hours or less
Projects
P: HfLA Website: Project Board
Status: Ice box
Milestone
08. Team workflow
Development

No branches or pull requests
10 participants
@mayankt153 @TJameel120 @ethant3 @ExperimentsInHonesty @Josiah-O @Providence-o @7kram @bishrfaisal @Tusharachada1406 @Samhitha444