Overview

We need to track existing issues and make new issues to deliver Project Meetings page complete enough for the Homepage launch

Details

We need to track and support the final wrap up items for the homepage launch, so that it can be completed.

Action Items

[x] List all the issues related to the label
[x] Identify what open issues have to be resolved before launch, by classifying the issues into the following categories using MoSCoW method in a comment.
- Must Have
- Should Have
- Could Have
- Won't Have this time

[x] Add the following details under each issue

- why: [ADD WHY ITS IMPORTANT TO TO THE LAUNCH]
- status: [ADD STATUS e.g., Icebox, Emergent Requests, New Issue Approval, ERs and epics that are ready to be turned into issues, Prioritized Backlog, In Progress (actively working), Questions / In Review]
   - draft: [true OR false]
   - responsible: [ADD GITHUB HANDLES WITHOUT @]
- role: [ADD ROLE e.g. data scientist, infrastructure, design, design lead, user research, Research Lead, dev leads, data analyst, BA, hfla leadership, back end/devOps, writing, front end, merge team, technical writer]

[x] Once you receive sign-off from Staff PM add to ## Relevance of the issues to the Homepage launch
[ ] Review comments with Notes carried forward from epic if it exists, and make sure all previous items are addressed in the top of the issue.
- If it specifies new issues to make then add explicit action items for making those issue in a new comment on this issue
  - get sign-off on those new issues to make by Staff PM
[ ] Identify items that need issues opened by looking at the page and features and seeing what is not already addressed by the existing issues or new issues to make list.
[ ] Make the issues specified
[ ] Link them as sub issues to this issue
[ ] Classify them using MoSCoW and add the details (why, status, draft, responsible, role)
[ ] Get Sign-off and prioritization of the issues by Staff PM
[ ] If this page has content that must be checked for accuracy before homepage launch, add the detail to the epic for tracking that (resource 1.05)

Resources/Instructions

Parent Epic: https://github.com/hackforla/website/issues/2481

Used for creating this issue

1.01 Label name: P-Feature: Project Meetings
- 1.01.01 Issue Tab: P-Feature: Project Meetings
- 1.01.02 Project Board: P-Feature: Project Meetings
1.02 URL of page on Hack for LA website: https://www.hackforla.org/project-meetings
1.03 URL of link to code search: repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// project-meetings
1.04 URL of WIKI page: none (should be added and linked from this page https://github.com/search?q=repo%3Ahackforla%2Fwebsite+project-meetings&type=wikis)
- 1.04.01 URL of future edits to wiki pages: https://github.com/hackforla/website/wiki/How-to-Contribute-to-the-Wiki (check this page to see if there are any other new edits in the queue.
1.05 Issue for adding items to a final checklist: #8417

Created by this issue

2.01 [EXAMPLE would be a link to an issue related to delivering this page]

Issues to write

Must Have

TBD

Should Have

TBD

Could Have

TBD

last updated: 2025-10-13 Highest number found: 7904

Relevance of the issues to the Homepage launch

Must Have

[ ] #7904
- why: It is the epic for this page (this issue)
- status: In Progress
  - draft: False
  - responsible: None
- role: Product

Should Have

[ ] #3527
- why: We need to audit the Project Team Meetings to know which text elements are missing text components so that we can fix them in Figma, and ensure consistency with the Design System and Implementation by the website team.
- status: Prioritized Backlog
  - draft: False
  - responsible: None
- role: Design

Could Have

List of all could have issues

#6321
- why: We need to add info to the wiki under the pages details, that make it easy for future team members to edit and know which pages use which files
- status: Ice Box
  - draft: False
  - responsible: None
- role: Front End

Won't have this time

List of all won't have issues

Template

- [ ] #
   - why: 
   - status: 
      - draft: 
      - responsible: 
   - role:

List of all issue by number

[ ] #
[ ] #

Feb 12 '25 19:02 ExperimentsInHonesty

List of all issues

[ ] #7904
[ ] #7524
[ ] #6321
[ ] #3527

Relevance of the issues to the Homepage launch

Must Have

[ ] #7904
- why: It is the epic for this page (this issue)
- status: New Issue Approval
  - draft: False
  - responsible: None
- role: Product

Should Have

[ ] #3527
- why: We need to audit the Project Team Meetings to know which text elements are missing text components so that we can fix them in Figma, and ensure consistency with the Design System and Implementation by the website team.
- status: Prioritized Backlog
  - draft: False
  - responsible: None
- role: Design

Could Have

[ ] #7524
- why: To protect data privacy and security, we should only receive the necessary data required for page creation.
- status: In Progress
  - draft: False
  - responsible: @Khinememe-Kyaw
- role: Back End/DevOps
[ ] #6321
- why: We need to add info to the wiki under the pages details, that make it easy for future team members to edit and know which pages use which files
- status: Ice Box
  - draft: False
  - responsible: None
- role: Front End

Won't have this time

[ ] #
- why:
- status:
  - draft:
  - responsible:
- role:

Templates

   - [ ] # 
   - why: 
   - status: 
      - draft
      - responsible: 
   - role:

### Issues list associated with this epic
last updated: 
Highest number found:

Mar 28 '25 10:03 priyanka02art

@pm-daniel7 Please provide update

Instructions

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

You can use this template

1. Progress: 
2. Blockers: 
3. Availability:
4. ETA:
5. Pictures (if necessary):

May 28 '25 20:05 ExperimentsInHonesty

@pm-daniel7

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, May 27, 2025 at 12:05 AM PST.}