Prep project boards for Migration

[Rabia2219]

Overview

We need to prepare the Project Boards for the forced migration that GitHub is doing in August, so that it is already working well for the team by then.

Action Items

Repeat first 3 steps for each card

• copy this template to a comment below

  ### Text from project board card, [Add name of board here], [Add name of column here]
  ```
  [PASTE CARD CONTENT HERE]
  ```
  - [ ] Determine where this item goes on the wiki (page and section)
  - [ ] copy item to wiki
  - [ ] hide this comment when completed.
  

• copy the content of the card (by clicking the 3 dots and selecting Edit Note, and then CRTL+C) and paste it into your new comment where it says `[PASTE CARD CONTENT HERE]
• delete card from project board
• add project board URL(s) in resources below
• add the project board migration label to this issue
• add issue to project board
• move issue to Prioritized Backlog

Resources/Instructions

Classic Project board URL(s):

• Open:
  • Unclaimed/Project Management
• Closed: None

New Project board URL(s): https://github.com/orgs/100Automations/projects/4

[ExperimentsInHonesty]

I have edited down the text on each card to fit onto the new board (see hidden comments). And I updated the readme and wiki on this repo to link to the new board

[Rabia2219]

Note

• sent a msg to superbunker in the 100Automations Slack channel about 2FA for the GitHub project account

Hi 
[@Jason Brown](https://hackforla.slack.com/team/U01G7G1HMU1)
 I am trying to recover the github account for 100automations but I don't know whose authentication device was used to set it up, and the recovery codes are not in the 1password vault.  I am going to add you back to the 1password vault. Could you try to log into it using your 2FA account and see if that works.  If it does, please add the recover codes to the account so  we can reset it with a different 2FA.

*if he doesn't reply, follow-up by email 2024-09-09

We are trying to make the form for submitting new proposals work again, and it needs a github token in the google app script.. We can't get access to the github account because we don't know whose token is being used (it does not say, in 1Password vault)