Overview

We need to track existing issues and make new issues to deliver Events 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: Events
- 1.01.01 Issue Tab: P-Feature: Events
- 1.01.02 Project Board: P-Feature: Events
1.02 URL of page on Hack for LA website: https://www.hackforla.org/events/
1.03 URL of link to code search: repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// Events
1.04 URL of WIKI page: https://github.com/search?q=repo%3Ahackforla%2Fwebsite+Events&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: 7674

Relevance of the issues to the Homepage launch

Must Have

[ ] #7674
- why: It is the epic for this page (this issue)
- status: In Progress
  - draft: True
  - responsible: None
- role: Product
[ ] #8433
- why: We no longer do happy hours. We do an in person summer get together.
- status: New Issue Approval
  - draft: False
  - responsible: None
- role: TBD
[ ] #8432
- why: We are no longer an in person organization and have moved remote.
- status: New Issue Approval
  - draft: False
  - responsible: None
- role: TBD
[ ] #8431
- why: we can move this information to the About page to highlight that we were an active in person organization that moved remote
- status: New Issue Approval
  - draft: False
  - responsible: None
- role: TBD
[ ] #6140
- why: Civic Tech Structures full name is Civic Tech Structure, Inc. and sometimes it makes sense to say Civic Tech Structure, Inc. 501(c)(3) or even Civic Tech Structure, Inc. a non profit 501(c)(3). Different pages have different listings
- status: Emergent Requests
  - draft: False
  - responsible: @ExperimentsInHonesty
- role: Product
[ ] #4370
- why: The client intermittently triggers POST requests for the Jennifer Pahlka video on the events page, causing the loading circle to spin for several minutes. This problem appears to occur only on MacOS.
- status: ERs and epics that are...
  - draft: False
  - responsible: None
- role: Front end

Should Have

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
#3289
- why: Ensure consistent text elements on the Events page
- status: New Issue Approval
  - draft: False
  - responsible: None
- role: Design

Won't have this time

List of all won't have issues

Templates

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

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

List of all issue by number

[ ] #
[ ] #

Oct 31 '24 02:10 priyanka02art

Hi @priyanka02art.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

Oct 31 '24 02:10 github-actions[bot]

URL: https://www.hackforla.org/events
[ ] Events Issues on the project board
[ ] [https://github.com/hackforla/website/issues/6320 (this issue is also relevant to Project info and Project meetings pages]
[ ] [https://github.com/hackforla/website/issues/6749]
[ ] [https://github.com/hackforla/website/issues/6369]

Oct 31 '24 02:10 priyanka02art

List of all issues

[ ] #7674
[ ] #7524
[ ] #6321
[ ] #6140
[ ] #4370
[ ] #3289

Relevance of the issues to the Homepage launch

Must Have

[ ] #7674
- why: It is the epic for this page (this issue)
- status: New Issue Approval
  - draft: True
  - responsible: None
- role: Product
[ ] #4370
- why: The client intermittently triggers POST requests for the Jennifer Pahlka video on the events page, causing the loading circle to spin for several minutes. This problem appears to occur only on MacOS.
- status: ERs and epics that are...
  - draft: False
  - responsible: None
- role: Front end

Could Have

[ ] #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
[ ] #6140
- why: Civic Tech Structures full name is Civic Tech Structure, Inc. and sometimes it makes sense to say Civic Tech Structure, Inc. 501(c)(3) or even Civic Tech Structure, Inc. a non profit 501(c)(3). Different pages have different listings
- status: Emergent Requests
  - draft: False
  - responsible: @ExperimentsInHonesty
- role: Product
[ ] #3289
- why: Ensure consistent text elements on the Events page
- status: New Issue Approval
  - draft: False
  - responsible: None
- role: Design

Won't have this time

[ ] #7524
- why: Refactor issue
- status: In Progress
  - draft: False
  - responsible: @Khinememe-Kyaw
- role: Back end/DevOps

Templates

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

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

Mar 24 '25 21:03 priyanka02art

@charmainemak09 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

2025-12-16 Using this search state:open label:"P-Feature: Events" is:issue

This is the highest issue number found 8433 it is addressed at the top of this issue.

Oct 13 '25 22:10 kimberlyvaldez07

EPIC: Prepare the Events page for Homepage Launch

Overview

Details

Action Items

Resources/Instructions

Used for creating this issue

Created by this issue

Issues to write

Must Have

Should Have

Could Have

Relevance of the issues to the Homepage launch

Must Have

Should Have

Could Have

Won't have this time

Templates

List of all issues

Relevance of the issues to the Homepage launch

Must Have

Could Have

Won't have this time

Templates