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

Communities of Practice information updates: Data Science #3693

Closed
7 of 8 tasks
KarinaLopez19 opened this issue Nov 3, 2022 · 10 comments · Fixed by #3752
Closed
7 of 8 tasks

Communities of Practice information updates: Data Science #3693

KarinaLopez19 opened this issue Nov 3, 2022 · 10 comments · Fixed by #3752
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours time sensitive Needs to be worked on by a particular timeframe

Comments

@KarinaLopez19
Copy link

KarinaLopez19 commented Nov 3, 2022

Overview

We want to update the information in the Data Science CoP card so that the information is accurate.

Action Item

  • In _data/internal/communities/data-science.yml, update the file to reflect the information written below:
    • Remove person(s)
      • Ryan Swan
    • Add person(s)
      • Name: Karina López
        Title: Co-lead
        GitHub Handle: KarinaLopez19
        Slack Member ID: Karina Lopez
  • Once the pull request associated with this issue has been merged, please send this back to the Product Managers by
    • Adding a ready for product label and placing this issue in the New Issue Approval column

    • The bio information below is for Bonnie and Product Manager(s). The bio information below is not part of this issue, so the developer does not need to implement it as part of this issue.

      I would also like to add my bio to the website per Bonnie's request. I'm not sure which page exactly but I provided the blurb below. Thanks!

      Karina (she/they) combines her passions in activism, research, and art into her data pursuits.

      She holds a BA from Dartmouth College in neuroscience with a focus on computational social behaviors. In other words, she loves understanding how and why people behave the way they do translated from patterns in data.

      Keeping inclusivity and activism at the forefront, she enjoys supporting folks navigating their entry into a data science profession as well as building spaces for WOC in tech. When she's not on her laptop, you can find her adopting new creative hobbies or rollerskating on smooth pavement.

Resources/Instructions

@KarinaLopez19 KarinaLopez19 added P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice role: product Product Management labels Nov 3, 2022
@ExperimentsInHonesty ExperimentsInHonesty added size: 0.25pt Can be done in 0.5 to 1.5 hours time sensitive Needs to be worked on by a particular timeframe ready for dev lead Issues that tech leads or merge team members need to follow up on and removed size: missing role: product Product Management labels Nov 6, 2022
@ExperimentsInHonesty
Copy link
Member

I approve these changes. I will add the bio on a different page. Just send this back to product when finished.

@ExperimentsInHonesty ExperimentsInHonesty added the role: front end Tasks for front end developers label Nov 6, 2022
@JessicaLucindaCheng JessicaLucindaCheng added the Complexity: Small Take this type of issues after the successful merge of your second good first issue label Nov 8, 2022
@jdingeman jdingeman added ready for product and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Nov 11, 2022
@jdingeman

This comment was marked as resolved.

@jdingeman jdingeman changed the title Communities of Practice information updates: [Data Science] Communities of Practice information updates: Data Science Nov 11, 2022
@JessicaLucindaCheng

This comment was marked as outdated.

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Nov 14, 2022

@jdingeman I went ahead and edited this issue more because PMs wanted it to be more clear. See this issue as an example:

Also, I think Bonnie wanted this passed back to PMs after it was implemented, so I went ahead and added the ready for milestone label and removed ready for product label for now. Sorry for my confusion.

@github-actions

This comment was marked as outdated.

@Satenik-Ba

This comment was marked as outdated.

@jdingeman
Copy link
Member

@hackforla/product-managment, per item in issue, I am tagging this as ready for product and returning to new issue approval.

@Rabia2219
Copy link
Member

Rabia2219 commented Dec 6, 2022

@hackforla/product-managment, per item in issue, I am tagging this as ready for product and returning to new issue approval.

@jdingeman Hi there! Tagging 'hackforla/product-managment' sends this message to all the PMs across HackforLA. You need to tag the PM for your project only :)

@ExperimentsInHonesty
Copy link
Member

Product on the website team will need to draft an issue on this

@ExperimentsInHonesty
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours time sensitive Needs to be worked on by a particular timeframe
Projects
Development

Successfully merging a pull request may close this issue.

6 participants