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 issues to update Project Profile: Website #7317

Closed
24 of 46 tasks
mayankt153 opened this issue Aug 19, 2024 · 8 comments
Closed
24 of 46 tasks

Create issues to update Project Profile: Website #7317

mayankt153 opened this issue Aug 19, 2024 · 8 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) ready for product 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

@mayankt153
Copy link
Member

mayankt153 commented Aug 19, 2024

Overview

The project team from website 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 Update comment 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 Update comment 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

Hackforla.org Website

Project Card URL

website.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?

NO

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

Name:

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: Samhitha Kamma
GitHub Handle: Samhitha444
Role: Product Manager
Slack Member ID: U07FF529MU6

Name: Mayank Tibrewal
GitHub Handle: mayankt153
Role: Product Manager
Slack Member ID: U07FF4G9D0W

Name: Venkatasai Poorna Tushara Chada
GitHub Handle: Tusharachada1406
Role: Product Manager
Slack Member ID: U07FF4FALT0

Project Status

Active

@mayankt153 mayankt153 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 size: 0.5pt Can be done in 3 hours or less ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization labels Aug 19, 2024
@ExperimentsInHonesty
Copy link
Member

This addition looks good to me. This issue is ready to be made into a small issue.

@JessicaLucindaCheng JessicaLucindaCheng changed the title Update Project Profile: Website ER: Update Project Profile: Website Aug 20, 2024
@JessicaLucindaCheng JessicaLucindaCheng added the ER Emergent Request label Aug 20, 2024
@ExperimentsInHonesty ExperimentsInHonesty added good first issue Good for newcomers epic size: 0.25pt Can be done in 0.5 to 1.5 hours Issue Making: Level 1 Make issues from a template and a spreadsheet 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 ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization labels Sep 18, 2024
@ExperimentsInHonesty ExperimentsInHonesty changed the title ER: Update Project Profile: Website Create issues to update Project Profile: Website 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
@siyunfeng siyunfeng self-assigned this Oct 21, 2024
@HackforLABot
Copy link
Contributor

Hi @siyunfeng, 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 :)

@siyunfeng siyunfeng moved this from ERs and epics that are ready to be turned into issues to In progress (actively working) in P: HfLA Website: Project Board Oct 21, 2024
@siyunfeng
Copy link
Member

Availability: 6:00 PM - 10:00 PM Weekdays (EDT)
ETA: 10/24/2024 Thursday

@siyunfeng
Copy link
Member

siyunfeng commented Oct 22, 2024

@siyunfeng
Copy link
Member

Hi, @mayankt153 !

I could not find the Update comment button mentioned in the action list above Add milestone Onboarding flow.
Does it mean to click the Submit new issue button instead?

@daras-cu
Copy link
Member

@siyunfeng thank you for bringing your question up at the meeting tonight, I'm confirming you should use the Submit new issue button. If you don't have any other questions about this issue you can move it back to In Progress status and remove the ready for product label.

@siyunfeng
Copy link
Member

@siyunfeng thank you for bringing your question up at the meeting tonight, I'm confirming you should use the Submit new issue button. If you don't have any other questions about this issue you can move it back to In Progress status and remove the ready for product label.

Thank you for clarifying, @daras-cu !

The following actions after creating all the issues from this ER required me to do these:

  • 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

I'm still waiting for someone to review this issue. Should I still move this issue back to In Progress status and remove the ready for product label as you suggested?

@roslynwythe
Copy link
Member

Thank you @siyunfeng for creating these good first issues

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) ready for product 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
Development

No branches or pull requests

7 participants