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

Create a Guide/Template: Using GitHub Labels on HfLA Projects #115

Open
1 of 12 tasks
lasryariel opened this issue Sep 20, 2024 · 4 comments
Open
1 of 12 tasks

Create a Guide/Template: Using GitHub Labels on HfLA Projects #115

lasryariel opened this issue Sep 20, 2024 · 4 comments
Assignees
Labels
Complexity: Missing CoP: Product drive: knowlegebase ALL the files are moved into the knowledgebase content repo drive feature : guide creation milestone: missing Phase: 1 - Gather Examples Solo size: missing status: 1.1 needs wiki examples Gathering examples by checking each team's wiki status: 1.2 needs issues examples Gathering examples by checking each team's issues status: 1.3 needs project board examples Gathering examples by checking each team's project board cards status: 1.4 needs slack examples Check each team's slack channel for examples

Comments

@lasryariel
Copy link
Member

lasryariel commented Sep 20, 2024

Overview

We need to standardize certain types of labels across teams, so that there is more consistency when looking at issues across GitHub projects (for example standardizing the "role:" label helps the hfla Open Roles project.
We will create a spreadsheet of standardized labels based on guidance to be outlined by Bonnie.

Action Items

  • Bonnie to add guidance on standardized labels to this issue
  • Ariel to prep initial spreadsheet
  • Bonnie to review
  • Make changes as needed based on Bonnie's feedback
  • Review with PM CoP

The phases in the guide-making process are listed below. Each phase displayed in blue is linked to a wiki page with instructions on how to complete that phase. Open the wiki page in a new tab, copy the instructions for each part into the section labeled 'Tasks' at the bottom of this issue, and complete each task listed.

Resources/Instructions

Guidance:

  • Labels should be all lowercase
  • Do not use hyphens for compound words that can use a space instead
  • [Bonnie to add additional guidance here]

Projects to Check

Tasks

  • This is where you will copy instructions from the wiki page for the step you are currently on.
@lasryariel lasryariel self-assigned this Sep 20, 2024
@lasryariel lasryariel changed the title Create updated GitHub Issue Label guide spreadsheet Create updated GitHub Standardized Issue Label guide spreadsheet Sep 20, 2024
@fchan218 fchan218 changed the title Create updated GitHub Standardized Issue Label guide spreadsheet Create updated GitHub Standardized Issue Label guide Oct 28, 2024
@fchan218 fchan218 changed the title Create updated GitHub Standardized Issue Label guide Create a Guide/Template: Using GitHub Labels on HfLA Projects Oct 28, 2024
@fchan218
Copy link
Member

Prior version of issue

Overview

We need to standardize certain types of labels across teams, so that there is more consistency when looking at issues across GitHub projects (for example standardizing the "role:" label helps the hfla Open Roles project.
We will create a spreadsheet of standardized labels based on guidance to be outlined by Bonnie.

Action Items

  • Bonnie to add guidance on standardized labels to this issue
  • Ariel to prep initial spreadsheet
  • Bonnie to review
  • Make changes as needed based on Bonnie's feedback
  • Review with PM CoP

Resources/Instructions

Guidance:

  • Labels should be all lowercase
  • Do not use hyphens for compound words that can use a space instead
  • [Bonnie to add additional guidance here]

@fchan218
Copy link
Member

Assignee, Labels, Project Board Placement, and Milestones for this issue in the PRODUCT Repo:

Screenshot 2024-10-30 at 5 00 01 PM

@fchan218
Copy link
Member

fchan218 commented Oct 30, 2024

Files in this Issue:

Speadsheet Standardized Github Labels

  • This file will need to be moved to the knowledgebase-content Google Drive
  • This files has been moved to the knowledgebase-content Google Drive

@fchan218
Copy link
Member

@lasryariel This guide issue is moving to the knowledgebase-content repo. If you would like to maintain edit access to the issue and its associated files, please fill out the Google Drive Access Form.

@fchan218 fchan218 transferred this issue from hackforla/product-management Oct 30, 2024
@fchan218 fchan218 added Phase: 1 - Gather Examples Solo status: 1.1 needs wiki examples Gathering examples by checking each team's wiki status: 1.3 needs project board examples Gathering examples by checking each team's project board cards status: 1.2 needs issues examples Gathering examples by checking each team's issues status: 1.4 needs slack examples Check each team's slack channel for examples size: missing milestone: missing Complexity: Missing feature : guide creation labels Oct 30, 2024
@fchan218 fchan218 moved this to Needs to be Triaged in P: Guides: Knowledgebase Content Tracker Oct 30, 2024
@fchan218 fchan218 added the drive: knowlegebase ALL the files are moved into the knowledgebase content repo drive label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Missing CoP: Product drive: knowlegebase ALL the files are moved into the knowledgebase content repo drive feature : guide creation milestone: missing Phase: 1 - Gather Examples Solo size: missing status: 1.1 needs wiki examples Gathering examples by checking each team's wiki status: 1.2 needs issues examples Gathering examples by checking each team's issues status: 1.3 needs project board examples Gathering examples by checking each team's project board cards status: 1.4 needs slack examples Check each team's slack channel for examples
Projects
Status: In progress (actively working)
Status: Needs to be Triaged
Status: Needs to be Triaged
Development

No branches or pull requests

2 participants