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.

Sign up for GitHub

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

Jump to bottom

VS Code Spell Checker Extension: Meeting Messaging #4470

Closed
2 of 14 tasks
Tracked by #4349
jdingeman opened this issue Apr 11, 2023 · 5 comments
Closed
2 of 14 tasks
Tracked by #4349

VS Code Spell Checker Extension: Meeting Messaging #4470

jdingeman opened this issue Apr 11, 2023 · 5 comments
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Onboarding/Contributing.md feature: spelling P-Feature: Project Meetings https://www.hackforla.org/project-meetings role missing size: 5pt Can be done in 19-30 hours time sensitive Needs to be worked on by a particular timeframe
Milestone
05. Know HFLA

Comments

@jdingeman
Copy link
Member

jdingeman commented Apr 11, 2023 •
edited by roslynwythe
Loading

Dependencies

Overview

As dev leads, we need to notify developers that we are adding the VS Code Spell Checker Extension across local environments so that everyone gets a chance to install the extension.

Action Items

  • Review the slides or instructions used during meetings, if any, and create additions or new materials to share the messaging that will support the rollout plan
  • Notify developers during the following meetings:
    • Sun. Oct 8, 2023
    • Tues. Oct 10, 2023
    • Thurs. Oct 12, 2023
    • Sun. Oct 15, 2023
    • Tues Oct 17, 2023
    • Thurs Oct 19, 2023
    • Sun. Oct 22, 2023
    • Tues Oct 24, 2023
    • Thurs Oct 26, 2023
  • When all meetings have been addressed, release dependency on Create a Roll Out Plan for adding Code Spell Checker VS Code Extension #4349. If all dependencies have been satisfied, move that issue into the New Issue Approval column with the ready for dev lead or ready for product label for review and a note about where to find the finished plan.

Resources
@jdingeman jdingeman added Feature: Onboarding/Contributing.md Complexity: Small Take this type of issues after the successful merge of your second good first issue P-Feature: Project Meetings https://www.hackforla.org/project-meetings size: 5pt Can be done in 19-30 hours role: dev leads Tasks for technical leads labels Apr 11, 2023
@jdingeman jdingeman added this to the 05. Know HFLA milestone Apr 11, 2023
@jdingeman jdingeman mentioned this issue Apr 11, 2023
Open
17 tasks
@ExperimentsInHonesty
Copy link
Member

@hackforla/website-merge sorry I missed this. can we revise the dates and then get this issue out.

Open
2 tasks
@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on time sensitive Needs to be worked on by a particular timeframe and removed ready for product labels May 14, 2023
@roslynwythe
Copy link
Member

roslynwythe commented Jul 23, 2023 •
edited
Loading

@roslynwythe roslynwythe mentioned this issue Oct 3, 2023
Open
@ExperimentsInHonesty ExperimentsInHonesty added feature: spelling Dependency An issue is blocking the completion or starting of another issue and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Oct 8, 2023
@ExperimentsInHonesty
Copy link
Member

@roslynwythe I moved this into the new issue review column because the dependency is resolved. Please add a ready for prioritization label if its ready.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Dependency An issue is blocking the completion or starting of another issue labels Jan 24, 2024
@ExperimentsInHonesty
Copy link
Member

Or we can close this if everyone already knows.

@roslynwythe
Copy link
Member

roslynwythe commented Mar 11, 2024 •
edited
Loading

@ExperimentsInHonesty I believe most everyone knows because the instructions have been in CONTRIBUTING.md for awhile, but if there is still a desire to do messaging in meetings, I suggest that we rewrite this issue to add an item to the Tuesday or Sunday meeting agendas. But in that case we should add dependencies on #6446 and/or on a proposed wiki page "How to manage spell check warnings"

@ExperimentsInHonesty ExperimentsInHonesty removed the ready for dev lead Issues that tech leads or merge team members need to follow up on label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Onboarding/Contributing.md feature: spelling P-Feature: Project Meetings https://www.hackforla.org/project-meetings role missing size: 5pt Can be done in 19-30 hours time sensitive Needs to be worked on by a particular timeframe
Projects
P: HfLA Website: Project Board
Status: Done
Milestone
05. Know HFLA
Development

No branches or pull requests
3 participants
@roslynwythe @ExperimentsInHonesty @jdingeman