Wiki: Create a wiki for milestone information

[Aveline-art]

Dependency

• Use Jekyll Doc or MkDocs for Hack for LA project documentation #1534
• Updating Wiki: Move Current Wiki to New Repository #3636

Overview

As a member of the team, we need to have a basic understanding about our project board. For this issue, we will create a milestone wiki that will provide basic information about how our milestone system works.

Action Items

• Create a wiki that notes all of our current milestones.
• We are currently in the process of moving the old wiki to the new website-wiki repo, so we will not be making any changes or additions to the old wiki at this time. Thus, we will be adding wiki content through a different process now. Please refer to How to Contribute to the Wiki for instructions about where to place "Content to be Added/Edited in the New website-wiki Repo."

Resources/Instructions

• BETA Milestone wiki page
• HfLA Website Milestone page
• All the issues with no milestones
• link to the issue table to display issues with no milestone

[ExperimentsInHonesty]

Wiki page draft

Milestones at Hack for LA serve as crucial stages or goals within a project, enabling progress tracking and guiding task completion. They effectively break down the work, align with objectives, and ensure efficient project management.

To identify and categorize milestones for issues, it is vital to consider the issue's primary objective and desired outcome. It is important to think beyond the surface-level appearance of the issue and focus on what it is ultimately trying to achieve.

Compliance

This milestone is complete when there are no outstanding issues that potential could cause us to loose access to resources (e.g., images we are licensing) and that we are up to date on any legal documents that must appear on the site.
The specific pages most used within the "Compliance" milestone are:

• Credits page
• Privacy Policy
• Know HFLA

Security

Focuses on identifying, addressing, and mitigating security vulnerabilities and risks associated with the Hack for LA platform.

Roadmaps

Serve as a guiding document for the website or project teams, helping them prioritize tasks, allocate resources, and track progress towards their objectives. All milestones are made during roadmap sessions.
This is all the large scale planning for the website

• Design
• Research
• Product

Onboarding flow

Contains issues that affects new HfLA volunteers who have not yet joined a project and include several key features/issues that facilitate the onboarding process and familiarize new volunteers with the HfLA community. Any issues that are concerning onboarding but that only affect people on the website team, use the milestone Team Workflow.
The onboarding flow includes several key features that facilitate the onboarding process and familiarize new volunteers with the HfLA community:

• Project pages
• Project's page
• Join Us
• Getting started
• 404 page
• Team meeting times
• Community of Practice

Donation Flow

Focuses on providing a seamless and user-friendly experience for individuals who wish to make donations to support the organization's initiatives.
The specific features within the "Donation Flow" milestone are:

• Home page (anything that make it clear how to donate, other homepage changes are likely under Homepage Launch)
• About us (where it has donate information)
• Donate

Know Hack for LA

Provides users with comprehensive information about Hack for LA's overarching value, achievements, and ways to engage with the organization. It aims to educate and engage users by offering a clear understanding of Hack for LA's mission, impact, and opportunities for involvement (except where it falls into onboarding)

• About us
• Website Homepage (after relaunch)
• Sitemap
• Wins

Data Strategy

It focuses on implementing and utilizing effective data management and analytics practices to support the organization's goals and initiatives.
Feature:

• Google analytics

Homepage launch

We are rebuilding the homepage to highlight all the sections of the website (including hidden new sections)
The pages involved are

• Home page
• Impact
• Toolkit
• CoP
• Program areas

Team Work Flow

Focuses on optimizing the collaboration and efficiency of the HfLA website team. It encompasses various initiatives and processes aimed at streamlining project management, improving communication, and fostering a productive work environment. Some the most common labels used are:

• Good first issues
• Pre-works
• Process for board maintenance
• Github automation
• Design system

Program Area Visibility

Focuses on enhancing the visibility and accessibility of program areas within the organization's website.
The specific features within the "Program Area Visibility" milestone are:

• Program areas
• Project page (program areas filter++)

Frameworks

This milestone might get depreciated. Have not decided. Before assigning any issue to this milestone, discuss with the Product Team.

• A plan to do a major feature
  • where we are storing things
  • how we will maintain

HFLA impact

The "HfLA" milestone at Hack for LA focuses on showcasing the organization's achievements, impact, and success stories. It aims to highlight the positive outcomes and contributions of projects and members within the Hack for LA community. The milestone is centered around providing a platform to celebrate wins, demonstrate the global impact of projects, and recognize the excellent work of members.
Features:

• Wins page
• Global impact (rename impact page)
• (excellent => member feature page)

Toolkit relaunch

issues that go into the relaunch

Ongoing

Issues that never close, because we just reuse them. Usually they will have instructions on how to do the thing. We might also use the issue for tracking having done it

• Agendas (each agenda appears as a comment)
• label checks (each week, the next audit is added to a comment)
• onboarding and offboarding (each person who is onboarded, has a checklist in a comment. Later, their offboarding also happens in the same issue on a new comment, and then both comments are hidden).

Accessibility

Aims to remove barriers and create an inclusive user experience for individuals with disabilities. This can involve considerations such as providing alternative text for images, ensuring proper color contrast, implementing keyboard navigation support, screen readers, all texts, providing captions and transcripts for multimedia content, and following web accessibility standards and guidelines, such as the Web Content Accessibility Guidelines (WCAG).

Technical Debt

Issues for code that functions correctly but is not optimized for long-term development and maintenance. It may be poorly structured, contain redundant or inefficient code, lack proper documentation, or deviate from coding best practices. The Technical Debt milestone aims to address these issues and improve the quality, readability, and maintainability of the codebase.
The milestone emphasizes refactoring and improving the codebase to enhance maintainability, efficiency, and ease of editing.

Excellent Level

Focuses on enhancing features and initiatives that are already functioning well but have room for improvement. This milestone recognizes that while these features or initiatives are not considered critical or high-priority, there is still value in refining and optimizing them to achieve a higher level of excellence.
"It works well, but could be improved, because it’s not crucial, there might be negligible value."

Ignore Test

Issues that are using in the process of testing Automations. They should be excluded from Metrics and Analysis (unless the metrics/analysis are about how many test issues we create)

[ExperimentsInHonesty]

I am signing off on the milestone descriptions and they are ready to add to wiki

@Josiah-O has some additional guidance to add re how to think about the objective of milestone.

[Josiah-O]

@ExperimentsInHonesty I have added the additional guidance on how to think about the objective of milestone.

[Josiah-O]

@ExperimentsInHonesty I have added the milestone descriptions link to How to Contribute to the Wiki page.