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

People Depot: Accomplishment Summary for HfLA Website 2020-2024 #416

Open
1 of 11 tasks
shmonks opened this issue Aug 15, 2024 · 3 comments
Open
1 of 11 tasks

People Depot: Accomplishment Summary for HfLA Website 2020-2024 #416

shmonks opened this issue Aug 15, 2024 · 3 comments
Assignees
Labels
complexity: large Many parts are unexplained and up to the implementer to figure out. documentation Improvements or additions to documentation p-feature: accomplishments ready for product role: product s: org stakeholder: the org (includes stats) size: 3pt Can be done in 13-18 hours time sensitive

Comments

@shmonks
Copy link
Member

shmonks commented Aug 15, 2024

Overview

We need to write brief summaries of project accomplishments for each year of the project's life, to go on the website's accomplishments page.

Action Items

  • Review the accomplishments on resource 1.02 to see how they are worded, and note the following: Accomplishments on the Hack for LA website are:
    • readable even if you don't know anything about the project
    • short
    • clearly articulated achievements that funders would care about
    • list partners if available
  • Find and review all previous onesheets
    • Find all the one sheets (check Project's Google Drive resource 1.03) and link the folder to resource 1.04.03. If there are multiple folders, create 1.04.03.01, 1.04.03.02, etc. indented under 1.04.03)
    • Review all previous project onesheet drafts under 1.04 (including edit history)
  • Search the project's repo for any accomplishment issues, add any links you find to a comment
    • Go to the project repo issue tab (resource 1.05)
    • review all closed issues, looking for details of your project's progress that you could use in your accomplishment summary, noting the accomplishment and date of completion
    • Put the links relevant to that search under the below heading in chronological order
    ### Project or CoP's repo issue searches
    
  • for each search you perform, indicate what you searched in the filter bar to get the result and link it to the URL (e.g.,)
    #### Searches
    - [Replace with what you searched for in the Filter bar]
    - [Replace with what you searched for in the Filter bar]
    - [Replace with what you searched for in the Filter bar]
    
  • Draft a brief paragraph describing what the project accomplished for each year
  • Update the epic issue (resource 1.01)
    • Add the following comment
    We have completed the accomplishments for 2020-2024
    
    • Add the label updated
    • Add the label ready for org rep
    • Move to the questions/review column on the Team Tasks project board

Resources/Instructions

@shmonks shmonks self-assigned this Aug 15, 2024
@shmonks shmonks added the documentation Improvements or additions to documentation label Aug 15, 2024
@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty transferred this issue from hackforla/peopledepot Oct 1, 2024
@github-project-automation github-project-automation bot moved this to 🆕New Issue Review in P: PD: Project Board Oct 10, 2024
@Rabia2219 Rabia2219 transferred this issue from hackforla/admin-accomplishments Oct 10, 2024
@shmonks shmonks removed their assignment Oct 10, 2024
@Rabia2219 Rabia2219 changed the title Write summaries of annual accomplishments for website [PROJECT NAME]: Accomplishment Summary for HfLA Website 2020-2024 Oct 10, 2024
@Rabia2219 Rabia2219 changed the title [PROJECT NAME]: Accomplishment Summary for HfLA Website 2020-2024 People Depot: Accomplishment Summary for HfLA Website 2020-2024 Oct 10, 2024
@Rabia2219 Rabia2219 added size: 3pt Can be done in 13-18 hours role: product complexity: large Many parts are unexplained and up to the implementer to figure out. time sensitive labels Oct 10, 2024
@Rabia2219 Rabia2219 added this to the 03. Org Requirements milestone Oct 10, 2024
@Rabia2219 Rabia2219 moved this from 🆕New Issue Review to 📋Prioritized Backlog in P: PD: Project Board Oct 10, 2024
@Rabia2219 Rabia2219 moved this from New Issue Approval to Prioritized Backlog in HfLA: Project Team Tasks Oct 10, 2024
@shmonks shmonks added the s: org stakeholder: the org (includes stats) label Oct 10, 2024
@shmonks shmonks self-assigned this Oct 18, 2024
@shmonks shmonks moved this from 📋Prioritized Backlog to 🏗In progress-actively working in P: PD: Project Board Oct 18, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from 🏗In progress-actively working to 📋Prioritized Backlog in P: PD: Project Board Oct 23, 2024
@shmonks shmonks self-assigned this Nov 7, 2024
@shmonks shmonks moved this from 📋Prioritized Backlog to 🏗In progress-actively working in P: PD: Project Board Nov 7, 2024
@shmonks shmonks moved this from Prioritized Backlog to In Progress in HfLA: Project Team Tasks Nov 7, 2024
@shmonks

This comment was marked as outdated.

@shmonks
Copy link
Member Author

shmonks commented Nov 14, 2024

Please provide update

  1. Progress: Still getting going with this
  2. Blockers: None so far
  3. Availability: Tomorrow and then Tues + Thurs next week
  4. ETA: Possibly next week
  5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."
  • remember to add links to the top of the issue if they are going to be needed again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: large Many parts are unexplained and up to the implementer to figure out. documentation Improvements or additions to documentation p-feature: accomplishments ready for product role: product s: org stakeholder: the org (includes stats) size: 3pt Can be done in 13-18 hours time sensitive
Projects
Status: In Progress
Status: 🏗In progress-actively working
Development

No branches or pull requests

3 participants