ER: Build a tool to verify activities of HfLA members

[JessicaLucindaCheng]

Note: This issue came from the Task List Dev Leads.

Emergent Requirement - Problem

Issue Description
Write an issue to build a tool to be used for verification of activity of the HfLA members (might use GHA to build the tool). This tool would search all HackforLA projects for user activity and it can be used for verification requests for a HfLA member from potential employers.

Who was involved

GitHub Handle(s):

• ExperimentsInHonesty
• JessicaLucindaCheng
• SAUMILDHANKAR

What happens if this is not addressed

Nothing changes and we continue manually checking each person for background checks and verification requests.

Resources

Action Items

• Check with the Stakeholder Rep (Bonnie) if this is something we still want to do within the Website Team repo
• Discuss with team
• In the 100 Automations repo,
  • Search and check
    • If an open issue exists that addresses this ER
    • If a closed issue exists that has already addressed this ER
  • If an open issue doesn't exist and this ER wasn't already fixed by a closed issue, make a new issue

Potential solutions [draft]

[ExperimentsInHonesty]

@JessicaLucindaCheng This should get moved to another repo. We have one for org wide automations (.github) but I think that is meant to be used for automations that are used on repos. So then the question is where do we put automations that are not for project but instead for the organization. Perhaps a repo called admin-automations? Let me know if this sounds good.

[JessicaLucindaCheng]

@ExperimentsInHonesty

@JessicaLucindaCheng This should get moved to another repo. We have one for org wide automations (.github) but I think that is meant to be used for automations that are used on repos. So then the question is where do we put automations that are not for project but instead for the organization. Perhaps a repo called admin-automations? Let me know if this sounds good.

I think it is a good idea for the automation to be in a separate repo, though not sure what we call it yet. However, for moving the issue itself, I was thinking either
A) The issue would be part of the repo where the automation will be made. Then, in terms of project management, there can be a project board (using the new GitHub projects) because the new projects can have issues from multiple repos.
B) 100 Automations board might be a good place for the issue since it is an automation issue but I know the 100 Automations project is on hold.

Let me know what you think. I'll put this on our Dev/PM agenda so we can discuss it.

Edit:
Answer from Bonnie

• Yes, put it in the issue in 100 Automations repo/project board using the Google Form on the board.