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

EPIC: Create issues to Update Project Profile: VRMS #7407

Open
46 tasks
JackHaeg opened this issue Sep 6, 2024 · 3 comments
Open
46 tasks

EPIC: Create issues to Update Project Profile: VRMS #7407

JackHaeg opened this issue Sep 6, 2024 · 3 comments
Assignees
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level epic good first issue Good for newcomers Issue Making: Level 1 Make issues from a template and a spreadsheet P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours time sensitive Needs to be worked on by a particular timeframe

Comments

@JackHaeg
Copy link
Member

JackHaeg commented Sep 6, 2024

Overview

The project team from VRMS needs its project leadership variable information updated, so that the current team members can be properly displayed on the Hack for LA website

Action Items

  • Review the Project Update Data below and then follow the instructions for either adding or deleting team members from the project's .md
Adding new volunteers to team page
  • Create a new issue using the add new leader to project template
  • Customize the title with name of project and person to add
  • Customize the body
    • In the ER, go to the value under the line "Project Card URL"
      • Copy the file name
      • On the line that starts "- [ ] In your IDE…" replace brackets with the copy (the text we are expecting is a file name with the extension .md)
    • In the copy block below the line that starts, "Find the leadership variable and add the following profile." add all the information from the ER for the person you are adding.
    • On the checkbox line below, "- [ ] Verify the changes by viewing..." replace with name of project
    • to Resource 2, find the project on the https://www.hackforla.org/projects/ page
      • click on its link
      • copy link
      • replace brackets on resource 2 with the URL
    • Add link to the ER on resource 3
  • Choose Submit new issue button
  • Add milestone Onboarding flow
  • Review, and if ready, add label
Ready for Prioritization
  • Add the URL to a comment on this ER
    • if this is the first add leader issue to be created, paste this into a comment and add the URL of the issue you just created.
### Adding Leader issues
-

### Complete
- [ ] Check this when all the Add leader issues have been made
  • if the above comment already exists, just add your new issue URL to the list.
  • Check off the box, if it's the last one that needed to be created.
Removing volunteers from team page
  • Create a new issue using the remove new leader to project template
  • Customize the title with name of project and person to add
  • Customize the body
    • In the ER, go to the value under the line "Project Card URL"
      • Copy the file name
      • On the line that starts "- [ ] In your IDE…" replace brackets with the copy (the text we are expecting is a file name with the extension .md)
    • Go to https://github.com/hackforla/website/tree/gh-pages/_projects and find and click on the file
      • click on code view
      • copy the code block
      • highlight the text on your new issue where it says [Insert the lines of code to remove the specified leadership member] and delete it and replace with the copy block
    • On the checkbox line below, "- [ ] Verify the changes by viewing..." replace with name of project
    • to Resource 2, find the project on the https://www.hackforla.org/projects/ page
      • click on its link
      • copy link
      • replace brackets on resource 2 with the URL
    • Add link to the ER on resource 3
  • Choose Submit new issue button
  • Add milestone Onboarding flow
  • Review, and if ready, add label
Ready for Prioritization
  • Add the URL to a comment on this ER
    1. if this is the first remove leader issue to be created, paste this into a comment on this issue and add the URL of the issue you just created.
### Removing Leader issues
-

### Complete
- [ ] Check this when all the removal issues have been made
  • if the above comment already exists, just add your new issue URL to the list.
  • Check off the box, if it's the last one that needed to be created.
  • When you have completed making all the add and remove issues
    • move this issue into the Questions/Review column
    • add the ready for product label

Project Update Data


Project Name

VRMS

Project Card URL

vrms.md

Update the Title?

NO

Title

No response

Update the Description?

NO

Description

No response

Update the Hero Image?

NO

Hero Image

No response

Update the Image?

NO

Image

No response

Update the Technologies?

NO

Technologies (maximum 26 characters per technology name)

No response

Update the Partner(s)?

NO

Partners

No response

Update the Tools?

NO

Tools

No response

Update GitHub Link?

NO

GitHub Link

No response

Update Slack Link?

NO

Slack Link

No response

Update Test Site Link?

NO

Test Site Link

No response

Update Demo Site Link?

NO

Demo Site Link

No response

Update Site Link?

NO

Site link

No response

Remove person(s) and info from Leadership?

YES

If YES on remove person(s), edit the below to provide the information required. If NO, delete the template in the field below:

Name:

  • Judy Lee
  • Alex Lee
  • Amanda glover

Add person(s) and info to Leadership?

YES

If YES on add person(s), edit the below to provide the information required. If NO, delete the template in the field below:

Name: Jack Haeger
GitHub Handle: JackHaeg
Role: Lead Product Manager
Slack Member ID: U059005TN1L

Name: Stephanie Samuels
GitHub Handle: Steph112792
Role: Product Manager
Slack Member ID: U03SJS7LYCC

Name: Katiuska Alecea de Leon
GitHub Handle: chukalicious
Role: Developer
Slack Member ID: U0100R46ESC

Name: Brad Morgan
GitHub Handle: bkmorgan3
Role: Developer
Slack Member ID: U779QRX3Q

Name: Evan Yang
GitHub Handle: evanyang1
Role: Developer
Slack Member ID: U02APE3V4Q3

Name: Angela Lee
GitHub Handle: awlfccamp
Role: Developer
Slack Member ID: U062NB2CKMZ

Name: Nikhil Trehan
GitHub Handle: ntrehan
Role: Developer
Slack Member ID: U078NLYGWRK

Name: Nora Zajzon
GitHub Handle: nora-zajzon
Role: Developer
Slack Member ID: U078JUC959C

Name: Mudassir Hussain
GitHub Handle: hussainmudassir
Role: Developer
Slack Member ID: U07GAGE89TJ

Also, please change the following user's GitHub Handle & Role:
(the Name and Slack ID remain the same but he updated GitHub handle and Title)

  • Name: Trillium Smith
  • GitHub Handle: trillium
  • Role: Lead Developer
  • Slack Member ID: U010G9864Q1

Project Status

Active

@JackHaeg JackHaeg added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) time sensitive Needs to be worked on by a particular timeframe Complexity: Small Take this type of issues after the successful merge of your second good first issue ready for dev lead Issues that tech leads or merge team members need to follow up on size: 0.5pt Can be done in 3 hours or less labels Sep 6, 2024
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: HfLA Website: Project Board Sep 6, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the ER Emergent Request label Sep 13, 2024
@ExperimentsInHonesty ExperimentsInHonesty changed the title Update Project Profile: VRMS ER: Update Project Profile: VRMS Sep 13, 2024
@ExperimentsInHonesty ExperimentsInHonesty added ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Sep 13, 2024
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 17, 2024

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 17, 2024

Adding Leader issues

Complete

  • Check this when all the Add leader issues have been made

@ExperimentsInHonesty ExperimentsInHonesty added good first issue Good for newcomers size: 0.25pt Can be done in 0.5 to 1.5 hours epic and removed Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 0.5pt Can be done in 3 hours or less ER Emergent Request labels Sep 18, 2024
@ExperimentsInHonesty ExperimentsInHonesty changed the title ER: Update Project Profile: VRMS Create issue to Update Project Profile: VRMS Sep 18, 2024
@ExperimentsInHonesty ExperimentsInHonesty removed the ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization label Sep 18, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the Issue Making: Level 1 Make issues from a template and a spreadsheet label Sep 18, 2024
@ExperimentsInHonesty ExperimentsInHonesty changed the title Create issue to Update Project Profile: VRMS Create issues to Update Project Profile: VRMS Sep 18, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level label Sep 18, 2024
@ExperimentsInHonesty ExperimentsInHonesty changed the title Create issues to Update Project Profile: VRMS EPIC: Create issues to Update Project Profile: VRMS Oct 29, 2024
@mademarc mademarc self-assigned this Nov 13, 2024
@HackforLABot
Copy link
Contributor

Hi @mademarc, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level epic good first issue Good for newcomers Issue Making: Level 1 Make issues from a template and a spreadsheet P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours time sensitive Needs to be worked on by a particular timeframe
Projects
Status: ERs and epics that are ready to be turned into issues
Development

No branches or pull requests

4 participants