Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ER: Add start dates and end dates to projects #6820

Open
3 of 9 tasks
KwameTaylor opened this issue May 5, 2024 · 4 comments
Open
3 of 9 tasks

ER: Add start dates and end dates to projects #6820

KwameTaylor opened this issue May 5, 2024 · 4 comments
Assignees
Labels
Complexity: Large Complexity: Medium Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours

Comments

@KwameTaylor
Copy link
Member

KwameTaylor commented May 5, 2024

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

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

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
@KwameTaylor KwameTaylor added Feature Missing This label means that the issue needs to be linked to a precise feature label. Draft Issue is still in the process of being created size: 0.25pt Can be done in 0.5 to 1.5 hours ER Emergent Request role missing Complexity: Missing labels May 5, 2024
@KwameTaylor KwameTaylor self-assigned this May 5, 2024
Copy link

github-actions bot commented May 5, 2024

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:

@ExperimentsInHonesty ExperimentsInHonesty added this to the x. Technical debt milestone May 6, 2024
@ExperimentsInHonesty ExperimentsInHonesty added P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers Complexity: Medium ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing Complexity: Missing labels May 6, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Issue Making: Level 2 Make issue(s) from an ER or Epic and removed Draft Issue is still in the process of being created ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization labels May 7, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this to ERs and epics that are ready to be turned into issues in P: HfLA Website: Project Board Jun 23, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Complexity: Small Take this type of issues after the successful merge of your second good first issue Complexity: Medium and removed Complexity: Medium Issue Making: Level 2 Make issue(s) from an ER or Epic labels Jul 30, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues label Jul 30, 2024
@JessicaLucindaCheng JessicaLucindaCheng added role: back end/devOps Tasks for back-end developers P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 0.25pt Can be done in 0.5 to 1.5 hours ER Emergent Request and removed role: back end/devOps Tasks for back-end developers Complexity: Medium P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 0.25pt Can be done in 0.5 to 1.5 hours ER Emergent Request labels Jul 30, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Complexity: Medium Complexity: Large and removed Complexity: Small Take this type of issues after the successful merge of your second good first issue labels Jul 30, 2024
@t-will-gillis
Copy link
Member

t-will-gillis commented Jul 30, 2024

@ExperimentsInHonesty your thoughts?

Following is one way to find a project start date using a GitHub Action:

  • The GitHub REST API (version 2022-11-18) to access information about a project's GitHub repo is here. Note that the created_at date is returned with the "Example response".
  • The API's owner variable is 'hackforla', and the repo variable is the repo for the project, for example 'website'.
  • With this info, a .yml can be written to trigger a small workflow that returns the created_at date for a project's repo. Continuing with the example for the 'website' repo:
    # https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#get-a-repository
    # Example workflow to query REST API to find start date given a repo's name
    name: Find Start Date
    
    on:
      workflow_dispatch:
    
    jobs:
      Find_Start_Date:
        runs-on: ubuntu-latest
        steps:
          - name: Retrieve Repo
            id: retrieve-repo
            uses: actions/github-script@v7
            with:
              script: |
                const OWNER = 'hackforla';
                const REPO = 'website';
                results = await github.request('GET /repos/{owner}/{repo}', {
                  owner: OWNER,
                  repo: REPO
                });
                const START_DATE = results.data.created_at
                console.log(`The repo for project "${REPO}" created on: ${START_DATE.slice(0,10)}`);
    

@HackforLABot
Copy link
Contributor

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

@ExperimentsInHonesty ExperimentsInHonesty moved this from ERs and epics that are ready to be turned into issues to In progress (actively working) in P: HfLA Website: Project Board Nov 17, 2024
@k-cardon
Copy link
Member

Availability: usually evenings / weekends
ETA: end of week

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large Complexity: Medium Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
Status: In progress (actively working)
Development

No branches or pull requests

6 participants