Minimum steps for new project setup

[ExperimentsInHonesty]

Overview

We need a checklist of all new projects, so that new PMs can take ownership of the process and get the resources they need from leadership

Action Items

• [ ] Product Manager
  • [ ] Ideate on name of project (including is it available as a domain name and on socialmedia: twitter, instagram, facebook)
  • [ ] get signoff from HfLA leadership
• [ ] Hack for LA org Leader
  • [ ] Create Google Drive #11
    • [ ] Add PM to drive
  • [ ] register domain name (if needed)
  • [ ] setup email in gsuite (nameofproject@hackforla.org)
  • [ ] setup GitHub repository
  • [ ] create the following teams for the repository (remembering to add the correct permissions for each)
    • [ ] name of repo
    • [ ] name of repo-write
    • [ ] name of repo-maintain
    • [ ] name of repo-admin
  • [ ] setup 1 password vault
    • [ ] add PM to vault
    • [ ] add project gmail to vault
• [ ] Product Manager
  • [ ] Add roster from template folder and fill out
  • [ ] Create initial issues and milestones (related issue #7 needs some cleanup)

Resources/Instructions

HfLA gsuite HfLA 1 password

Resources that still need to be written

how to use 1 password how to add new people to the google drive link to the template folder (or roster, etc.)

[ExperimentsInHonesty]

@Olivia-Chiong I am thinking we should make this into a template and ask each new project to use it. But the big question I have for it, is what is the trigger.

[ExperimentsInHonesty]

Here is the next project that we did this on. See if we added anything new and update the template https://github.com/hackforla/product-management/issues/240#issuecomment-818021339