ER: Add start dates and end dates to projects

[KwameTaylor]

Emergent Requirement - Problem

For a future feature, we need to have the start date of a project

Details

1. In the future, when we add start and end dates in the sponsor-partner.yml file, we will be able to tell if someone is a founding partner/sponsor if we also have a start date on the project.
2. When we move the information to the People Depot project, it will require project start dates.

Issue you discovered this emergent requirement in

• ER: Sponsor section on About Us page is hardcoded  #5948

Date discovered

2024-05-05

Did you have to do something temporarily

• YES
• NO

Who was involved

@bonniewolfe @roslynwythe @KwameTaylor

What happens if this is not addressed

Needing to refer back into the past manually to recall this information on older projects

Resources

• https://github.com/hackforla/website/blob/gh-pages/_data/external/github-data.json
• https://github.com/hackforla/website/tree/gh-pages/_projects

Recommended Action Items

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

Potential solutions [draft]

• Create issue to create instructions on how to find the date using a github action (large issue)
• Create Epic issue (which is dependent on the instructions being done and has a medium label and issue making level 3)
  • Create issue template for medium issues where the person working on this issue follows the instructions and finds the date on the repo
• Make an issue from the epic to test it.

We need to store the date a repo started. We probably don't need to ever pull this twice (unlike languages, etc), although we will need it for any new repos we add

• to get the date
  • look at the first commit to a project repo
  • If there are multiple repos for the same project, we should use the repo that has the oldest start date
• where to store it?
  • store it in the project.md files

[github-actions]

Hi @KwameTaylor.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels