Build GHA development practice

[ExperimentsInHonesty]

Overview

We need org level GHAs across projects, and it would be useful to have some general HfLA guides about GHAs so that we can make running projects easier.

Action Items

• Identify where the open GHAs will live
  • Review how the Data Science Community of Practice shares opportunities with their members
• How we will determine prioritization
• Who can submit
• Requirement drafting standards

Resources/Instructions

• Define Automations for the Org repos admin#52
• GHA: Automation of a Repository Activity Digest #11
• https://github.blog/changelog/2022-01-21-share-github-actions-within-your-enterprise/

[ExperimentsInHonesty]

People in the conversation
Kevin Ashworth - returning, used to be on civictechindex
Matt Pereira - been here about a month on merge team at hfla
Will Gillis - been here about a month on hfla backend
Garth Tuazon - will be joining the website team been at the org for a week
Satenik -
Mai Vang
Seth - website team
Arpita Pandya - hfla since april, on merge team - backend
Justin Dingman - on merge team been here a few months - backend
Abraham website team 1 week
Yoojin - website team - 1 week
Travis - week hfla team - backend
Jessica - almost a year, on website
Saumil - website team long time, full stack like backend
Ava Li, Civic tech jobs, also a backend developer
Suman, website team 3 months - backend

[ExperimentsInHonesty]

Make an issue for determining feasibility of installing GHAs at the org level

Claimed by @Aveline-art

[ExperimentsInHonesty]

Copy current instructions from Hack for LA website team and make it generic

[ExperimentsInHonesty]

Workshops we could run

• How the workflow works
• Syntax
• Command Line
• Testing the GitHub Actions you have written (to reduce the time your testing takes)

[ExperimentsInHonesty]

Assigned to: @JessicaLucindaCheng
Progress: Completed but pending review and getting questions answered
Blockers: Need a review and questions to be answered.
Availability: 2 hours
ETA: Nov 30, 2022

Tasks

• Project board (using new projects and iterations) with each GHA that is ready to work on, or in progress of being written.
• Columns
  • Proposed
    • automated as to do
  • review
    • label: ready for quality review
    • label: needs refinement
    • label: ready for prioritization
  • ready for dev
  • live beta
  • released (done)
  • will not do
• [ ]

Links

• CoP Eng - GHAs project board
  • Workflows
  • Settings
• Labels
  • ready for prioritization
  • needs refinement
  • ready for quality review

Questions and Review

• Review labels
• Review Project Board set up
  • Question: Did you want an In Progress column? If not, where do devs put in progress issues? Yes, keep In Progress.
• Review Workflows
  • Question: What do you mean by "automated as to do" for the "Proposed" column? See the website project board for what is in the automation
  • Question: Are pull requests (PRs) going on the board too? If so, which columns? How does it work?
  • Question: Do we want to auto-archive issues or PRs?
• Question: Do we want a wiki defining what goes in what columns and the process of how issues move through the columns?
• Review Settings
  • Project Settings
    • Project name
    • Description
    • README
      • Question: What, if anything, do you want in the README? Maybe wiki page if we decide to have one?
    • Visibility
      • Only organization owners can change project visibility.
      • If you want to change it to public, the organization owner has to do it.
  • Manage access
    • Base role
    • Manage access
      • Question: What is the difference between engineering-admin and engineering-maintain teams?
        • Also, I don't see Ava on either of those teams.
      • Question: I am currently an Admin on the board since I created it and needed to edit Settings and other admin aspects of the board. Do you want me to remove myself as Admin after I am done setting up the board? I won't be able to make additional admin level edits to the board.
  • Custom fields
    • Status
    • Iteration
    • Estimate

[ExperimentsInHonesty]

Create a template issue for submitting a GHA proposal. See #11 and add anything you think is necessary

[JessicaLucindaCheng]

Assigned to: @JessicaLucindaCheng
Progress: Completed but still have more questions to be answered and need for more items to be reviewed.
Blockers:

• Wait on Bonnie to think about if she wants to just use 100 Automations project board/management system or the new board I created. Thus, I am pausing any work on this until a decision is reached.
• Need a review and questions to be answered.
  Availability: 2 hours
  ETA: Nov 30, 2022

Tasks

• Project board (using new projects and iterations) with each GHA that is ready to work on, or in progress of being written.
• Columns
  • Proposed
    • automated as to do
  • Need product review
    • label: ready for quality review
    • label: needs refinement
    • label: ready for prioritization
  • ready for dev
  • live beta
  • released (done)
  • will not do
• [ ]

Links

• CoP Eng - GHAs project board
  • Workflows
  • Settings
• Labels - Only the following labels were created as part of this issue:
  • ready for prioritization
  • needs refinement
  • ready for quality review

Questions and Review

• Review labels
• Review Project Board set up
  • Question: Did you want an In Progress column? If not, where do devs put in progress issues? Yes, keep In Progress.
• Review Workflows
  • Question: What do you mean by "automated as to do" for the "Proposed" column? See the website project board for what is in the automation
  • Question: Are pull requests (PRs) going on the board too? If so, which columns? How does it work? No, don't put prs on the board. If a pr needs review, the associated issue should go in the PR needs review column.
  • Question: Do we want to auto-archive issues? No, we are just going to manually archive.
• Question: Do we want a wiki defining what goes in what columns and the process of how issues move through the columns? Yes
• Review Settings
  • Project Settings
    • Project name
    • Description
    • README
      • Question: What, if anything, do you want in the README? Maybe wiki page if we decide to have one?
      • ReadMe should have an overview. With a link to the wiki (actually use mkdocs or docusaurus instead of the wiki). Replicate the mkdocs directory from https://github.com/hackforla/civictechjobs but make it only a docs folder, like https://github.com/codeforamerica/brigade-project-index (this is the associated website to it https://brigade.cloud/).
    • Bonnie asked Ava will install mkdocs or docusaurus on the engineering repo.
• Notes: Separate repos for each GHAs but since this is the same as 100 Automations then we don't need separate repos but just use the 100 Automations process.
  • Visibility
    • Only organization owners can change project visibility.
    • If you want to change it to public, the organization owner has to do it.
  • Manage access
    • Base role
    • Manage access
      • Question: What is the difference between engineering-admin and engineering-maintain teams?
        • Also, I don't see Ava on either of those teams.
      • Question: I am currently an Admin on the board since I created it and needed to edit Settings and other admin aspects of the board. Do you want me to remove myself as Admin after I am done setting up the board? I won't be able to make additional admin level edits to the board.
  • Custom fields
    • Status
    • Iteration
    • Estimate

[Aveline-art]

Everything that can be done with a .github repo:

• https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile
• https://docs.github.com/en/actions/using-workflows/creating-starter-workflows-for-your-organization
• https://docs.github.com/en/enterprise-cloud@latest/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization
• https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file

[ExperimentsInHonesty]

Links from last meeting

• CoP Eng - GHAs project board
  • Workflows
  • Settings
• Labels - Only the following labels were created as part of this issue:
  • ready for prioritization
  • needs refinement
  • ready for quality review