[EPIC] Review old Engineering and Engineering Hiring Guides issues

[christophermather]

We have a number of old issues that have recently been pulled over from the old Engineering and Engineering Hiring guide repos.

We need to review them and decide:

1. If they are still relevant and should be refined + prioritized
2. Or if they are no longer relevant and should be closed

Recommended steps:

• Engineering/Engineering Hiring Guide code owner takes a pass on the issues
• Engineering/Engineering Hiring code owner makes quick decisions
• Adds a 🟢, 🟡 or 🔴 to the issue in the Title field

🟢 means yes, this is still relevant
🔴 means no, this is no longer relevant
🟡 means needs more information/time to make a decision

Following these quick decisions, we should do a few follow-on steps, including: close out all 🔴s, pull all 🟢s and 🟡s into the TLC project backlog and tag all 🟡s with needs refinement.

Note: the issues are organized based on the repos they came from. One list is all Engineering Hiring issues and one list is Engineering issues.

Engineering Hiring

Beta Give feedback

1. 🟡 Add info about notes retention #339
   Engineering Hiring Guides Initiative 2 enhancement +4
2. 🟡 Add information or links to merit system principles and prohibited personnel practices #338
   Engineering Hiring Guides Initiative 2 enhancement +4
3. 🟡 Find out if there's a new/better Hiring Training deck to link to #337
   Engineering Hiring Guides Initiative 2 enhancement +4
4. 🟢 Use clearer name for pre-work #336
   Engineering Hiring Guides Initiative 2 enhancement +4
   
5. 🟢 Make it clearer that links in "Step by Step Process" point to further guides and resources #333
   Engineering Hiring Guides Initiative 2 enhancement +4
6. 🟡 Bring back /unconscious-bias page? #334
   Engineering Hiring Guides Initiative 2 +3
7. 🟢 Add guidance about proper handling of candidate PII #335
   Engineering Hiring Guides Initiative 2 +3
8. 🟢 fetch homework doesn't work with the provided files #332
   Engineering Hiring Guides Initiative 2 bug +4

Engineering

Beta Give feedback

1. 🟢 Recommending npm install --ignore-scripts might provide a false sense of security #320
   Engineering Guides Initiative 2 enhancement +4
2. 🟢 Ruby article is a stub (expand it) #321
   Engineering Guides Initiative 2 +3
3. 🟡 Document Credential management practices #322
   Engineering Guides Initiative 2 +3
4. 🟢 Make footnotes accessible across the site #323
   Engineering Guides Initiative 2 +3
5. 🟡 Update on-call recommendations for PHI/PII concerns #324
   Engineering Guides Initiative 2 +3
   
6. 🟡 Update with information related to Crypto #325
   Engineering Guides Initiative 2 +3
7. 🟡 Add post-incident response template #326
   Engineering Guides Initiative 2 good first issue +4
8. 🟢 Document various declarative, text-based diagram tools we use #327
   Engineering Guides Initiative 2 +3
   
9. 🟢 Add guidance on secret management for cloud.gov apps #329
   Engineering Guides Initiative 2 +3
   
10. 🟡 Create a new TTS engineer page #330
    Engineering Guides Initiative 2 +3
11. 🟢 Add content for Infrastructure as Code #331
    Engineering Guides Initiative 2 good first issue +4
    

[amymok]

@christophermather I took a pass on all of them. I am guessing you are taking the next step to pull those in TLC backlog?

[christophermather]

Excellent! Thanks so much, @amymok.

And yes, I'll work w/ the TLC crew to pull these into the backlog and get them prioritized.