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

HfLA website: Drive Migration #3058

Open
9 of 51 tasks
ExperimentsInHonesty opened this issue Apr 15, 2022 · 66 comments
Open
9 of 51 tasks

HfLA website: Drive Migration #3058

ExperimentsInHonesty opened this issue Apr 15, 2022 · 66 comments
Assignees
Labels
2 weeks inactive An issue that has not been updated by an assignee for two weeks Complexity: Medium Feature: Administrative Administrative chores etc. role: product Product Management size: 1pt Can be done in 4-6 hours
Milestone

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Apr 15, 2022

Overview

We need to finish the drive migration from the old to the new drive

Action Items

  • Confirm that you have access to the old and new drives, if not see instructions
  • Finish filling out the spreadsheet
  • Make a list of the people we need to contact and add it to this issue as check boxes
  • Create letter
  • Create booking link
  • Create a FAQ
  • Create form
  • Customize the letter
  • Get PM Sign-off
  • Make sure that all the people in the list are in the new drive with the permission of contributor
  • Send email from website@hackforla.org on agreed upon date from website@hackforla.org
  • Check daily to see if any responses to the form
  • Add zoom links to the meetings as they get added to the calendar
  • Add FAQ items as needed if new questions are asked in the form

Date to send letter

Sunday 2023-03-24

Resources/Instructions

People who need to migrate (add checks to the ones who have completed)

  • Adam Abundis
  • Ahdithan Uthayakumar
  • Akib Rhast
  • Alexandra Stubbs
  • Alyssa Benipayo
  • Andrew Ma
  • Ashley Lin
  • Ava Zheng
  • Basuhara Sen
  • Candance Seu
  • Christina Nguyen
  • David Rubinstein
  • Erika Bell
  • Harish Lingam
  • Hope Shin
  • Ibraheem Agbaje
  • Jacqueline Riley
  • Joshua Bubar
  • Kevin Ngaleu
  • Kian Badie
  • Kristine Eudy
  • Martha Martinez
  • Matthew Lee
  • Nielsen Hermanto
  • Olivia Chiong
  • Pamela Li
  • Qiqi Zheng
  • Raudel Blazquez Munoz
  • Roberta Fricker
  • Rosalyn Broddie
  • Shawn Duenas
  • Shelton Graves
  • Shruti Mukherjee
  • Shyam Amirthalingam
  • Sihem Gourou
  • Simone Campbell
  • Smitha Sindagi
@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 Apr 15, 2022
@github-actions

This comment has been minimized.

@ExperimentsInHonesty ExperimentsInHonesty added Feature: Administrative Administrative chores etc. role: product Product Management size: 1pt Can be done in 4-6 hours and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Apr 15, 2022
@ericvennemeyer ericvennemeyer added the role: back end/devOps Tasks for back-end developers label Jun 29, 2022
@ericvennemeyer ericvennemeyer self-assigned this Jun 29, 2022
@github-actions

This comment has been minimized.

@ericvennemeyer ericvennemeyer removed the role: back end/devOps Tasks for back-end developers label Jun 29, 2022
@ericvennemeyer ericvennemeyer removed their assignment Jun 29, 2022
@bishrfaisal

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as resolved.

@ExperimentsInHonesty
Copy link
Member Author

Last checked all the people currently in spreadsheet still have files to move 2023-03-24

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

Copy link

github-actions bot commented Aug 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 Tuesday, July 30, 2024 at 12:05 AM PST.

Copy link

github-actions bot commented Aug 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 Tuesday, August 6, 2024 at 12:04 AM PST.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 weeks inactive An issue that has not been updated by an assignee for two weeks Complexity: Medium Feature: Administrative Administrative chores etc. role: product Product Management size: 1pt Can be done in 4-6 hours
Projects
Status: Prioritized Backlog
Status: In progress (actively working)
Development

No branches or pull requests

3 participants