Update Communities of Practice: Engineering (Remove Chelsey Beck, Add Adam Abundis)

[JessicaLucindaCheng]

Prerequisites

1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
2. You have already read our How to Contribute to Hack for LA Guide.

Overview

We need to keep communities of practice information up to date so that visitors to the website can find accurate information.

Action Items

• In your IDE, open the _data/internal/communities/engineering.yml file
• Observe the existing syntax of the front matter block ¹ in the file
• Find the leadership variable and remove the following:

  - name: Chelsey Beck
    role: Co-Lead
    links:
      slack: https://hackforla.slack.com/team/U01J93AQKSS
      github: https://github.com/chelseybeck
    picture: https://avatars.githubusercontent.com/chelseybeck

• Then, add the following person to the leadership variable as a new entry :

  - name: Adam Abundis
    role: Co-lead
    links:
      slack: https://hackforla.slack.com/team/UJML6CY49
      github: https://github.com/abuna1985
    picture: https://avatars.githubusercontent.com/abuna1985

• Verify the changes by viewing the following in your local environment and include before and after screenshots with your pull request: the Engineering section on the Communities of Practice page ²
• Once your pull request is merged, go to ER: Communities of Practice information updates: Engineering #6160 and
  • Check off this issue under the Dependency section
  • If all the issues in the Dependency section are checked off, move ER: Communities of Practice information updates: Engineering #6160 to Questions / In Review column and uncheck the Dependency label.
    • Click here to see how to uncheck the Dependency label

      

Resources/Instructions

• This issue was initiated by ER: Communities of Practice information updates: Engineering #6160

Footnotes

1. Info about the front matter block ↩

2. Communities of Practice page URL: https://www.hackforla.org/communities-of-practice ↩

[github-actions]

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

[sornekian]

availability: weeknights 7-11pm
eta: 01/31/23 by 11pm

[LRenDO]

Hi @sornekian!

Thanks for taking on this issue! I am going to move this issue back the automated column it should have been moved to when the PR was created since there is a PR waiting for review and there doesn't appear to be a question about the issue. The Questions / In Review column is generally for issues that don't have an associated pull requests or for questions about an issue. Generally, the issue will explicitly say to move it to the Questions / In Review column and to add the label Ready for Dev Lead in the instructions. If there is an associated PR, the issue stays in In Progress (actively working) until the pull request is merged.

Please feel free to ping me here or on Slack if you have any questions or need help with resolving the current merge conflict as mentioned in #6204.

Thanks!