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

Update Project Profile: [name of project] #2473

Closed
2 tasks
daniellex0 opened this issue Jun 2, 2021 · 8 comments
Closed
2 tasks

Update Project Profile: [name of project] #2473

daniellex0 opened this issue Jun 2, 2021 · 8 comments
Labels
Complexity: Large feature: stakeholder updates P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: product Product Management size: missing

Comments

@daniellex0
Copy link
Member

daniellex0 commented Jun 2, 2021

Overview

We need to cleanup the current way for projects to do updates via new issues so that it can be easier for all involved

Action Items

  • Gather all the information about the various methods
  • Review the template provided by Danielle and Sihem below

Resources/Instructions

Current template
Suggestion: #2473 (comment)

@jbubar
Copy link
Member

jbubar commented Jun 2, 2021

@daniellex0 this is really great!
We should change it on website repo asap

@alexilee
Copy link

alexilee commented Jun 9, 2021

This is great, thanks for doing this. Two places where I got confused:

  1. Which project board should we create the issue? I think the answer is HfLA website team's board but it might be good to call it out explicitly.
  2. I got confused whether the Devs section was intended for a dev on my team or the HfLA website team. I see it described at the top but I think it could be clearer. Maybe something like 'Devs (for HfLA website dev)'

@Olivia-Chiong
Copy link
Member

I think this could be connected to a Google Form which would make filling it up easier.

@ggrrettcchhenn
Copy link
Member

I LOVE that you have directions at the top. I got confused every time I've submitted one of these cards in the past about how to get the team's attention.

  • Please add the correct image dimensions (this is something I've messed up in the past)
  • Might help to add where we can find what technologies and tools our team is using
  • Define status? Is it just Active or Inactive, or are there defined stages we should be using?

I think a google form could be helpful, esp for creating multiple choice questions where the possible answers are pre-defined

@Sihemgourou
Copy link
Contributor

To do : we need to create a list of standardized technologies

@ExperimentsInHonesty ExperimentsInHonesty transferred this issue from hackforla/product-management Nov 11, 2021
@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Nov 11, 2021
@ExperimentsInHonesty ExperimentsInHonesty added this to New Issue Approval in Project Board via automation Nov 11, 2021
@ExperimentsInHonesty
Copy link
Member

Suggestion for project update template

Update Project Profile: [name of project]


[ DELETE BEFORE SUBMITTING: Please fill this out and add comments with any up-to-date information about your project below, so that developers on the Hack for LA website team can update your project information. After you submit this new issue, post a link to it on #hfla-site slack channel with this message: "Please place this on the Hack for LA project board with the labels Good First Issue and Front-End"]

Overview

We need to update the information about the project [INSERT PROJECT NAME] so that it is up-to-date on the Hack for LA website

Project card

[ Insert url of your project card here before sending - all of their project cards can be found in this folder: https://github.com/hackforla/website/tree/gh-pages/_projects ]

Action Items

Devs (from HfLA website team)

  • Update the project.md file linked above using the information and comments here and posted below (scroll down)
    • Reference the project.md file template for guidance
    • Every section that is checked off should be left as-is. Any section that is unchecked should have up-to-date information you can add to the project.md file in comments below (scroll further down)

PMs

  • Please check off everything that is up-to-date or missing on purpose on your project page (to find your project page, click on your project card on the homepage). If any of this information is not correct or missing, please provide the updated information by adding comments on this issue, following the guidelines below:
    • Title [of project]

    • description [of project]

    • image

      Check Template

      image: insert image (png or jpg) here
      alt: 'description of the card image'
      Card image should be 600px wide x 400px high

    • image-hero

      Check Template

      image: insert image (png) here

      Card image should be 1500 px wide x800 px high

    • Current Project Team**

      Check Template

      name: First Last
      role: Product Manager or other
      slack: 'https://hackforla.slack.com/team/xxxxxx'
      github: 'https://github.com/githubusername'

    • links

      • Github
      • Slack
      • Test Site
      • Demo Site
      • Site
      • Overview [find your project's one-sheet here ]
      • Wiki
      • Readme
    • looking [roles project is looking to fill]

      Check Template

      category:
      skill:

    • technologies

    • partner

    • tools

    • status (Put false if the page should not be visible)

**Current Project Team:
The following details should be provided in a comment below about any project member who has been actively contributing on your team for at least 1 month, and who is not already listed under "Current Project Team":

**Slack:
To create a Slack link for each person, search for their slack profile, click on their name; this should give you a popup window with the user's picture, name, and a link to "View full profile". Click on "View full profile". That pane gives you the options message, call, and more. Click on "more" and you should be shown "Copy member ID" followed by the actual id. This is the id you need to use in the slack url, e.g. https://app.slack.com/team/<member_id_here

Resources

Template of a Project.md file

@ExperimentsInHonesty ExperimentsInHonesty added Feature: Standards P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: user research Complexity: Large feature: stakeholder updates role: product Product Management and removed role missing Feature Missing This label means that the issue needs to be linked to a precise feature label. Feature: Standards role: user research labels Nov 11, 2021
@ExperimentsInHonesty
Copy link
Member

Product needs to cleanup this issue so its clearer what to do next.

@ExperimentsInHonesty
Copy link
Member

I am closing this issue. The details have been recorded in the wiki https://github.com/hackforla/website/wiki/Decision-Records-on-Solutions-Not-Implemented

Project Board automation moved this from New Issue Approval to QA Mar 12, 2022
@ExperimentsInHonesty ExperimentsInHonesty moved this from QA to Done in Project Board Mar 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large feature: stakeholder updates P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: product Product Management size: missing
Projects
Project Board
  
Done
Development

No branches or pull requests

7 participants