ER: Fix mail links in "Privacy Policy"

[t-will-gillis]

Emergent Requirement - Problem

The mail links on the "Privacy Policy"¹ page are broken, and send users to a "something went wrong" page. We need to fix three links on this page so that we receive emails from visitors.

Result of clicking on mail link

### Issue you discovered this emergent requirement in - #7107

Date discovered

7/14/24

Did you have to do something temporarily

• YES
• NO

Who was involved

@t-will-gillis, @ anitahammer (outside HfLA)

What happens if this is not addressed

The page is asking for the reader to send an email to notify us of potential problems, but the link does not work. We might not be receiving emails from readers of this page.

Recommended Action Items

• Make a new issue
• Discuss with team
• Let a Team Lead know

Potential solutions [draft]

In the privacy-policy.yml² document, there are three locations (around lines 70, 80, and 92) where we indicate that users can contact us by email.

• For each location, replace:

  [privacy@hackforla.org](privacy@hackforla.org)
  

  with:

  [privacy@hackforla.org](mailto: privacy@hackforla.org)
  

• Using Docker, verify that the links direct users to their default email.

Resources

Footnotes

1. Privacy Policy ↩

2. privacy-policy.yml ↩

[HackforLABot]

Hi @dcotelessa, 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 :)

[dcotelessa]

Availability: Sun 11:00-3pm, Tue-Wed: 3-5
ETA: 2 hours

[dcotelessa]

Issue Created:

#7410
#7411
#7412

[t-will-gillis]

Hey @dcotelessa! Woohoo thanks for working on these- they look good. Just a couple suggestions:

• I think the issue titles will read better if the "7108: " is removed for each
• I like to give the link to the actual file, either in the body of the issue or in "Resources/Instructions", e.g. "- privacy-policy.yml" Just to make it easier for whoever works on it
• Could you capitalize "Docker" ?
• I like that you are emphasizing the location of the change and that the change applies only to the section noted

[jphamtv]

Hi @dcotelessa -

Additional suggestions:

• Fix typo: 'privacy-policy.yml.file' should be 'privacy-policy.yml file'
• Add project webpage URL under Resources (as per last action item)

Once you've made these and @t-will-gillis's edits:

1. Remove 'Draft' label
2. Add 'ready for merge team' label

The team will then re-review. Thanks!

--

@t-will-gillis - Since these are split into three separate issues in the same file, should we relabel them as 'good first issues'? Or consolidate them into one issue if we want to keep it as a small complexity issue? Thoughts?

[dcotelessa]

Hey @dcotelessa! Woohoo thanks for working on these- they look good. Just a couple suggestions:

• I think the issue titles will read better if the "7108: " is removed for each
  Updated titles.
• I like to give the link to the actual file, either in the body of the issue or in "Resources/Instructions", e.g. "- privacy-policy.yml" Just to make it easier for whoever works on it
  Added footnotes.
  Sounds good!
• Could you capitalize "Docker" ?
  Updated
• I like that you are emphasizing the location of the change and that the change applies only to the section noted

[t-will-gillis]

@dcotelessa looks good- thanks for making all of the changes.
@jphamtv about these issues' complexities: I agree that split into three, this is more like good first issues and that as one issue it would be Complexity: Small.

Ugh- the (not great) counter argument is to leave these as Complexity: Small since we need more small issues.

[dcotelessa]

Let me know if we want to label as good first issues, but for now they are set to Complexity: Small and close this IM.

[t-will-gillis]

Hey @dcotelessa Thanks, the issues look great and are prioritized-

Closing this issue as successfully completed.