search

hackforla / website

Hack for LA's website
https://www.hackforla.org
GNU General Public License v2.0
292 stars 724 forks source link

Rollout Plan: Refactor code with img HTML tags to end without a slash #4362

Open JessicaLucindaCheng opened 1 year ago

JessicaLucindaCheng commented 1 year ago

Dependency

Overview

We want to change img HTML tags ending with a slash () to an img tag without an ending slash () so that the codebase is consistent with how we use img HTML tags.

Details

Action Items

Resources/Instructions

[^1]: DR: img tag documentation comment

[^2]: Roll out plan

[^3]: HfLA-Website: img Tag Audit spreadsheet

[^4]: To understand the Issue Making labels, refer to the Resources section of this ER: #4678

[^5]: Issue Template 1: img Tag Refactor on Website and its associated Markdown file .github/ISSUE_TEMPLATE/img-tag-refactor-on-website.md. This template works for any pages that are marked with Template 1 in the Template to use if <img.../> found column on the Page Audit tab. Template 1 works if the img tag is on the website.

JessicaLucindaCheng commented 1 year ago

Awaiting approval before writing more issues: https://github.com/hackforla/website/issues/4366#issuecomment-1493273041

JessicaLucindaCheng commented 1 year ago

Issue making ladder

JessicaLucindaCheng commented 1 year ago

Original content of issue before changing it to a roll out plan

Overview

We want to change img HTML tags ending with a slash () to an img tag without an ending slash () so that the codebase is consistent with how we use img HTML tags.

Details

See the write-up for DR: img tag documentation comment {See 1 in Resources/Instructions below}

Action Items

Audit

Write issues

Instructions for issue writers if "Link to page on website (if applicable)" column is filled out
Instructions for issue writers if "Link to page on website (if applicable)" column is not filled out

Dev Lead

Resources/Instructions

  1. DR: img tag documentation comment
  2. HfLA-Website: img Tag Audit spreadsheet

    For issues where "Link to page on website (if applicable)" column is filled out

  3. img Tag Refactor issue template
  4. Example issue: https://github.com/hackforla/website/issues/4445
JessicaLucindaCheng commented 1 year ago

Notes for dev lead picking up this epic (OUTDATED)

Progress

I audited some of the pages and wrote some of the issues.

Audit
Write issues
JessicaLucindaCheng commented 1 year ago

Notes for dev lead picking up this epic

JessicaLucindaCheng commented 1 year ago

@hackforla/website-pm

JessicaLucindaCheng commented 1 year ago

To Dos

ExperimentsInHonesty commented 1 year ago

@JessicaLucindaCheng I took off the ready for product label because I think you got the feedback you needed from me last Monday

jiyanpatil07 commented 1 year ago

Hello @JessicaLucindaCheng , I would like to work on the issue mentioned above.

JessicaLucindaCheng commented 1 year ago

@jiyanpatil07 In order to work on an issue, you need to be a member of Hack for LA. (There are no fees to join.) Please follow the steps on our Getting Started page and attend an onboarding session.

JessicaLucindaCheng commented 1 year ago

Roll Out Plan

Epic 1

1A: Template for auditing

1B: Audit issue writing session

Epic 2

2A: Template(s) for good first issues to change the img tag

2B: Good first issue writing session

Resources/Instructions

[^1]: HfLA-Website: img Tag Audit spreadsheet [^2]: HfLA-Website: img Tag Audit spreadsheet's Page Audit tab [^3]: HfLA-Website: img Tag Audit spreadsheet's img with Ending Slash tab [^4]: Issue Template 1: img Tag Refactor on Website and its associated Markdown file .github/ISSUE_TEMPLATE/img-tag-refactor-on-website.md. This template works for any pages that is marked with Template 1 in the Template to use if <img.../> found column on the Page Audit tab . Template 1 works if the img tag is on the website.

JessicaLucindaCheng commented 1 year ago
JessicaLucindaCheng commented 1 year ago

@hackforla/website-merge Can someone read through and review this issue and its roll out plan to see if it is ready for prioritization? If you are interested, please leave your issue review availability and ETA in a new comment below. Thank you.

roslynwythe commented 1 year ago

@JessicaLucindaCheng Availability: 5/26 1 hr, 5/27 1 hr, 5/28 1 hr ETA 5/28 EOD

Is there any documentation I could reference to understand the meaning of the various "Issue Making" labels?

JessicaLucindaCheng commented 1 year ago

@roslynwythe Thanks for reviewing this roll out plan!

Is there any documentation I could reference to understand the meaning of the various "Issue Making" labels?

roslynwythe commented 1 year ago

Hi @JessicaLucindaCheng This looks good and it was interesting to see how you structured this Roll Out Plan into two child Epics. Your instructions are quite clear and I would feel comfortable working on this epic (or the child epics).

JessicaLucindaCheng commented 1 year ago

@roslynwythe Thanks for reviewing the roll out plan!

JessicaLucindaCheng commented 1 year ago

Questions for PM(s) and the answers:

Since Issue Making and Complexity issues are done in intertwined, parallel growth paths:

  1. Since this issue is for any front-end or back-end dev, will putting an existing Complexity label (good first, small, medium, or large) on this be confusing?
    Ans: Yes, it is confusing using those labels.

    Click here to see an example of how it can be confusing:
    • Let's say this rollout plan has a Complexity: Large.
    • Let's say a junior front-end developer is looking for a Large issue to work on.
      • They have finished working on 2 good first issues, Small, and Medium issues.
      • They have never written any issues, so they haven't completed an Issue Making Level 1 nor Level 2.
    • They filter the issues by complexity (Large) and roles (front end), and they see this issue fits the criteria. They may choose it without ever having written an issue.

  2. If we are adding a complexity label, I suggest we make a new label Complexity: Issue Making to indicate to look at the Issue Making labels. Is that okay? Ans: Bonnie said yes, but word it Complexity: See issue making label

ExperimentsInHonesty commented 1 year ago

@JessicaLucindaCheng that seems like a reasonable suggestion

github-actions[bot] commented 1 year ago

Hi @roslynwythe, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

github-actions[bot] commented 11 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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, July 25, 2023 at 12:15 AM PST.

roslynwythe commented 11 months ago

Update:

This Roll Out plan is in progress, and will remain open until all of the issues created as a result of #4922 and #5040 are closed.

github-actions[bot] commented 11 months ago

@roslynwythe

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.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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, August 8, 2023 at 12:06 AM PST.

fyliu commented 11 months ago

@roslynwythe Someone was asking about one of the issues that came out of this issue and I was thinking this could be done with a processing script.

Anyway, it seems like an opportunity for me to work on my commandline tools skills so I came up with this one-liner that runs from the project root.

It’s not entirely correct but I guess I don’t want to spend more time on it right now. It does what it’s supposed to but also has the side effect of removing extra spaces in all tags.

find . -name "*.html" -exec sed -i -e "s/<img\(.*\)\/>/<img\1>/g" -e "s/\s*>/>/g" {} +

  1. find all the html files and pass their paths to sed to process them
  2. sed edit files in-place (-i flag) with 2 edit commands. {} is a placeholder for the file path and + is the ending
  3. remove slash from closing bracket in img tags
  4. remove spaces before closing brackets in all tags

Here is the one to process just one file that I originally worked on.

sed -i -e "s/<img\(.*\)\/>/<img\1>/g" -e "s/\s*>/>/g" ./_includes/about-page/about-card-executive-letter.html

Another major problem is it doesn't match img tags spread across multiple lines. So it didn't catch this file, which I used the "/>" regex to find all self-closing tags and manually went through the results.

Anyway, the commands might be good for checking purposes or if you ever need to remove extra spaces in all tags. I just want to leave this here since it's related to this issue.

roslynwythe commented 11 months ago

Hi @fyliu that sed command is really impressive!! As you may know, we are always looking for good first issues for our junior developers on the website project. So I'd like to generate a list of files with html tags with extra spaces that I could use for creating good first issues. If you have a suggestion for that, please let me know. If you would like, I'll create an issue..

github-actions[bot] commented 10 months ago

@roslynwythe

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.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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, August 22, 2023 at 12:06 AM PST.

fyliu commented 10 months ago

@roslynwythe Here's some commands to find extra spaces within tag brackets.

Run these from the project root:

  1. This one finds tags that have extra ending spaces

    find . -name "*.html" -exec grep -lrP "<[^>]+\s+>" {} + | sort -u
find . -name "*.html" -exec grep -nrP --color=always "<[^>]+\s+>" {} + | sort -u | less -r
    • That's matching both the < and the >, with the middle having characters that are not the closing bracket ([^>]) and having at least one space character (\s).
    • It returns false positives for cases where the > is used as a less-than operator.
    • The --color option is just to highlight the match within a line.
    • It sorts the lines and filters for uniqueness (| sort -u).
    • The | less -r displays the results in a scrollable buffer. You can do page-scroll forward and back as well as use arrow keys for single lines. q to quit
    • Change the -l (show filenames only) flag into -n (show line numbers) to check manually for false positives.
    • You can also redirect the output to a file by adding > extra-spaces.txt at the end of the command. The color might show up as code so it's best to not have colors when saving to file.

  2. Here's another one that finds multiple consecutive spaces inside tags

    find . -name "*.html" -exec grep -lrP "<[^>]+\s{2,}[^>]+>" {} + | grep -v -e "-->" | sort -u
find . -name "*.html" -exec grep -nrP --color=always "<[^>]+\s{2,}[^>]+>" {} + | grep -v -e "-->" | less -r
    • It finds multiple whitespaces (\s{2,})
    • Then it filters out html comment tags in the second grep command (-->)
github-actions[bot] commented 10 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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, August 29, 2023 at 12:06 AM PST.

github-actions[bot] commented 10 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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, September 5, 2023 at 12:05 AM PST.

github-actions[bot] commented 10 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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, September 12, 2023 at 12:06 AM PST.

github-actions[bot] commented 9 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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, September 19, 2023 at 12:06 AM PST.

roslynwythe commented 9 months ago

Now that we have a template for updates to CONTRIBUTING.md, I'm planning to create the img tag refactoring issues targeting CONTRIBUTING.md

github-actions[bot] commented 8 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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, October 31, 2023 at 12:06 AM PST.

github-actions[bot] commented 8 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, November 6, 2023 at 11:05 PM PST.

github-actions[bot] commented 8 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, November 13, 2023 at 11:06 PM PST.

github-actions[bot] commented 7 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, November 20, 2023 at 11:06 PM PST.

github-actions[bot] commented 7 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, November 27, 2023 at 11:06 PM PST.

github-actions[bot] commented 7 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, December 4, 2023 at 11:06 PM PST.

github-actions[bot] commented 7 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, December 11, 2023 at 11:06 PM PST.

github-actions[bot] commented 6 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, December 18, 2023 at 11:06 PM PST.

github-actions[bot] commented 6 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, December 25, 2023 at 11:06 PM PST.

github-actions[bot] commented 6 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, January 1, 2024 at 11:06 PM PST.

github-actions[bot] commented 6 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, January 8, 2024 at 11:05 PM PST.

github-actions[bot] commented 5 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, January 15, 2024 at 11:06 PM PST.

github-actions[bot] commented 5 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, January 22, 2024 at 11:05 PM PST.

github-actions[bot] commented 5 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, January 29, 2024 at 11:06 PM PST.

github-actions[bot] commented 5 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, February 5, 2024 at 11:06 PM PST.

github-actions[bot] commented 5 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, February 12, 2024 at 11:05 PM PST.

github-actions[bot] commented 4 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, February 19, 2024 at 11:06 PM PST.

github-actions[bot] commented 4 months ago

@roslynwythe

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

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. 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 Monday, February 26, 2024 at 11:06 PM PST.