-
-
Notifications
You must be signed in to change notification settings - Fork 777
Issues: hackforla/website
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Create wiki page "how to cancel meetings"
Complexity: Medium
Feature: Wiki
Ready for Prioritization
role: back end/devOps
Tasks for back-end developers
role: front end
Tasks for front end developers
size: 1pt
Can be done in 4-6 hours
#7690
opened Nov 5, 2024 by
roslynwythe
3 tasks
ER: Issues to examine new wins data will be posted to the old project board
Complexity: Large
Draft
Issue is still in the process of being created
ER
Emergent Request
P-Feature: Wins Page
https://www.hackforla.org/wins/
role: back end/devOps
Tasks for back-end developers
size: 2pt
Can be done in 7-12 hours
local testing of new dockerhub image
Complexity: Small
Take this type of issues after the successful merge of your second good first issue
Feature: Docker
role: back end/devOps
Tasks for back-end developers
size: 0.5pt
Can be done in 3 hours or less
Updates to CONTRIBUTING.md to reflect changes in the Project Board and Skills Issue
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
Complexity: Small
Take this type of issues after the successful merge of your second good first issue
epic
Feature: Onboarding/Contributing.md
Ready for Prioritization
role: back end/devOps
Tasks for back-end developers
role: front end
Tasks for front end developers
size: 0.5pt
Can be done in 3 hours or less
Recruit volunteers for team open roles
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Complexity: Small
Take this type of issues after the successful merge of your second good first issue
epic
feature: recruitment
role missing
size: 0.25pt
Can be done in 0.5 to 1.5 hours
To Update !
No update has been provided
Resolve CodeQL Alert #48 - Generated by GHA
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Complexity: Medium
Feature: Code Alerts
P-Feature: Wins Page
https://www.hackforla.org/wins/
role: back end/devOps
Tasks for back-end developers
size: 1pt
Can be done in 4-6 hours
ER: Update Prework Template
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
Complexity: Small
Take this type of issues after the successful merge of your second good first issue
ER
Emergent Request
Feature: Onboarding/Contributing.md
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
Create wiki page to guide developers how to manage CodeQL alerts
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Complexity: Medium
Feature: Code Alerts
Feature: Wiki
role: back end/devOps
Tasks for back-end developers
role: front end
Tasks for front end developers
size: 1pt
Can be done in 4-6 hours
Epic: Create GitHub Action Wiki pages
Complexity: Medium
Draft
Issue is still in the process of being created
epic
Feature: Wiki
Issue Making: Level 1
Make issues from a template and a spreadsheet
role: back end/devOps
Tasks for back-end developers
size: 1pt
Can be done in 4-6 hours
Create wiki pages describing merge team/dev lead tasks
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Complexity: Small
Take this type of issues after the successful merge of your second good first issue
Feature: Onboarding/Contributing.md
role: dev leads
Tasks for technical leads
size: 0.5pt
Can be done in 3 hours or less
Implement "Keep-Alive" for Daniel Ridge bot so that Docker image will be updated
Complexity: Large
Feature: Docker
Ready for Prioritization
role: back end/devOps
Tasks for back-end developers
size: 2pt
Can be done in 7-12 hours
End to end testing of display of events using Selenium
Complexity: Large
Draft
Issue is still in the process of being created
Feature: Infrastructure
For changes on site technical architecture
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
size: 2pt
Can be done in 7-12 hours
HfLA: Dev Lead Team (Merge Team) Agenda
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Complexity: Small
Take this type of issues after the successful merge of your second good first issue
Feature: Administrative
Administrative chores etc.
feature: agenda
role: dev leads
Tasks for technical leads
size: 0.25pt
Can be done in 0.5 to 1.5 hours
Epic: Create issues to add github-handle to leadership teams
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Complexity: Medium
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
epic
Issue Making: Level 2
Make issue(s) from an ER or Epic
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
Epic: Create issues to add false positives to cspell.json
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
epic
Feature: Infrastructure
For changes on site technical architecture
feature: spelling
good first issue
Good for newcomers
Issue Making: Level 2
Make issue(s) from an ER or Epic
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
Epic: Create template, spreadsheet and list of issues for spellcheck audit
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
epic
feature: spelling
Issue Making: Level 2
Make issue(s) from an ER or Epic
role: back end/devOps
Tasks for back-end developers
size: 1pt
Can be done in 4-6 hours
To Update !
No update has been provided
Epic: Create issues to resolve CodeQL alerts 1- 24, 98 "Potentially unsafe external link"
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Added to dev/pm agenda
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
epic
Feature: Code Alerts
good first issue
Good for newcomers
Issue Making: Level 2
Make issue(s) from an ER or Epic
role: front end
Tasks for front end developers
size: 0.25pt
Can be done in 0.5 to 1.5 hours
ER: Fix needed for conflicts scss-lint.yml and .stylelint.json
Added to dev/pm agenda
Bug
Something isn't working
Complexity: Large
Draft
Issue is still in the process of being created
ER
Emergent Request
Feature: Refactor CSS
Page is working fine - CSS needs changes to become consistent with other pages
role: back end/devOps
Tasks for back-end developers
size: 0.25pt
Can be done in 0.5 to 1.5 hours
size: 3pt
Can be done in 13-18 hours
Epic: Manage CodeQL deployment
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
Feature: Code Alerts
Issue Making: Level 2
Make issue(s) from an ER or Epic
role: back end/devOps
Tasks for back-end developers
role: front end
Tasks for front end developers
size: 2pt
Can be done in 7-12 hours
Update Wiki page "How to Create Issues" to include Emergent Request issues and procedures
Complexity: Small
Take this type of issues after the successful merge of your second good first issue
Draft
Issue is still in the process of being created
Feature: Wiki
role: dev leads
Tasks for technical leads
size: 0.5pt
Can be done in 3 hours or less
Create wiki page to document merge team responsibilities
Complexity: Medium
Draft
Issue is still in the process of being created
Feature: Wiki
role: dev leads
Tasks for technical leads
size: 1pt
Can be done in 4-6 hours
Roll Out plan: Make issues required to change all the places that Good Second Issues appears with Good First Issue
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Added to dev/pm agenda
Complexity: Medium
epic
Feature: Board/GitHub Maintenance
Project board maintenance that we have to do repeatedly
Issue Making: Level 5
Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies
role: dev leads
Tasks for technical leads
size: 0.5pt
Can be done in 3 hours or less
Create a Roll Out Plan for adding Code Spell Checker VS Code Extension
2 weeks inactive
An issue that has not been updated by an assignee for two weeks
Added to dev/pm agenda
Complexity: Large
Dependency
An issue is blocking the completion or starting of another issue
Draft
Issue is still in the process of being created
Feature: Onboarding/Contributing.md
feature: spelling
Feature: Wiki
GHA New Project Board compatible
This GitHub Action issue does not reference columns and will work with the new board
role: back end/devOps
Tasks for back-end developers
role: dev leads
Tasks for technical leads
size: 3pt
Can be done in 13-18 hours
Epic: Refactor website header to provide accessible navigation
Complexity: Large
Draft
Issue is still in the process of being created
epic
Feature: Accessibility
Issues that would broaden website accessibility
Issue Making: Level 2
Make issue(s) from an ER or Epic
role: front end
Tasks for front end developers
size: 2pt
Can be done in 7-12 hours
ER: Wins randomizer content management
Added to dev/pm agenda
Complexity: Large
Dependency
An issue is blocking the completion or starting of another issue
ER
Emergent Request
P-Feature: About Us
https://www.hackforla.org/about/
P-Feature: Home page
https://www.hackforla.org/
role: back end/devOps
Tasks for back-end developers
role: front end
Tasks for front end developers
size: 2pt
Can be done in 7-12 hours
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-11-22.