website icon indicating copy to clipboard operation
website copied to clipboard
verified publisher icon hackforla

Update Project Profile: remove Gayle Martin from HackforLA.org Website

Open roslynwythe opened this issue 1 year ago • 8 comments

Prerequisite

  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.
  2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

The Hackforla.org Website project page needs to be updated so that the project information is up to date.

Action Items

  • [x] Observe the existing syntax of the front matter block inside of the _projects/website.md file and find the leadership variable.
  • [x] Delete the following lines from the file:
  - name: Gayle Martin
    github-handle: gaylem
    role: Merge Team
    links:
      slack: 'https://hackforla.slack.com/team/U06HC3A0DM0'
      github: 'https://github.com/gaylem'
    picture: https://avatars.githubusercontent.com/gaylem

Resources

roslynwythe avatar Jun 10 '24 19:06 roslynwythe

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

  • Complexity, Role, Feature, Size

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:

github-actions[bot] avatar Jun 10 '24 19:06 github-actions[bot]

Hi @mSharifHub, HfLA appreciates your interest in this issue, but please note that it is in the "New Issue Approval" column of the Project Board because it has not been finalized, approved, or prioritized, and so it is not ready for assignment. For this reason, you have been unassigned from this issue. Please remember to assign issues only from the "Prioritized Backlog" column.

The only exceptions to this rule are if you are writing an issue and the Draft label is applied, or if you are self-assigning to your "Pre-work Checklist" (the issue includes the Complexity: Prework label).

github-actions[bot] avatar Jun 13 '24 19:06 github-actions[bot]

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

github-actions[bot] avatar Jun 13 '24 19:06 github-actions[bot]

Hey @mSharifHub

As mentioned in the PR, developers aren't permitted to work on more than one issue at once. Your other PR is mostly complete, you'll just need to delete the screenshots of the code and replace them with 'No visual changes to the website', and provide a brief description of why the changes were necessary. For first issues, summarizing the overview of the linked issue is a good place to start.

Also, when your PR is merged, you'll have to assign your next issue from only the prioritized backlog, not from any other column/category.

If anything here is confusing, or you need help with anything, feel free to reach out.

ajb176 avatar Jun 13 '24 22:06 ajb176

Got it thank you

On Thu, Jun 13, 2024 at 3:15 PM Ajay @.***> wrote:

Hey @mSharifHub https://github.com/mSharifHub

As mentioned in the PR, developers aren't permitted to work on more than one issue at once. Your other PR is mostly complete, you'll just need to delete the screenshots of the code and replace them with 'No visual changes to the website', and provide a brief description of why the changes were necessary. For first issues, summarizing the overview of the linked issue is a good place to start.

Also, when your PR is merged, you'll have to assign your next issue from only the prioritized backlog, not from any other column/category.

If anything here is confusing, or you need help with anything, feel free to reach out.

— Reply to this email directly, view it on GitHub https://github.com/hackforla/website/issues/6981#issuecomment-2166881453, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAIFC5BYRSKDMCVWEGZCT23ZHIKWRAVCNFSM6AAAAABJC5UUPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRWHA4DCNBVGM . You are receiving this because you were mentioned.Message ID: @.***>

mSharifHub avatar Jun 13 '24 22:06 mSharifHub

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

github-actions[bot] avatar Jun 18 '24 22:06 github-actions[bot]

i. Availability: Tuesday and weekends ii. ETA: If I don't ran into any issue. I can complete this by next Tuesday.

naveentata avatar Jun 18 '24 22:06 naveentata

@naveentata

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, June 25, 2024 at 12:06 AM PST.

github-actions[bot] avatar Jun 28 '24 07:06 github-actions[bot]

@naveentata

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, July 2, 2024 at 12:06 AM PST.

github-actions[bot] avatar Jul 05 '24 07:07 github-actions[bot]

Hi @naveentata! Thanks for working on this issue. If you're still working, please add an update. If you're not able to continue to working on it, leave us a comment to let us know. If we don't hear from you soon, we will remove you from the issue. Thanks!

LRenDO avatar Jul 10 '24 18:07 LRenDO

@naveentata

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, July 9, 2024 at 12:07 AM PST.

github-actions[bot] avatar Jul 12 '24 07:07 github-actions[bot]

@naveentata

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, July 30, 2024 at 12:05 AM PST.

github-actions[bot] avatar Aug 02 '24 07:08 github-actions[bot]

@naveentata

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Tuesday, August 6, 2024 at 12:04 AM PST.

github-actions[bot] avatar Aug 09 '24 07:08 github-actions[bot]

Hello @Rajwinder35, we appreciate you taking on this issue, however it looks like you're already working on another issue at this time. Please wait until your current issue is merged before taking on another issue. :)

We are going to unassign you from this issue so you can focus on your current issue.

Hfla appreciates you! :)

HackforLABot avatar Aug 20 '24 12:08 HackforLABot

Hello @santisecco, we appreciate you taking on issue #6981, however it looks like you've already worked on enough issues of this complexity. Try checking out some of the issues of the next complexity from the Prioritized Backlog :)

We are going to unassign you from this issue so you can take on another issue.

Hfla appreciates you! :)

P.S. There is one exception to this rule/automation, and that is if you were away for a long time, and need to do the issue ladder again. If that is the case, please post the following note on the issue and on your Skills Issue (Pre-work Checklist). A Merge team member will reassign you to this issue, and will help you get assigned to subsequent issues up to medium size.

I am returning after a significant time away, and need to do the issue ladder again. Please assign me back to this issue.

HackforLABot avatar Sep 23 '24 18:09 HackforLABot

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

HackforLABot avatar Nov 10 '24 05:11 HackforLABot

i. Availability: I am available to work on this issue from 11/11/24-11/15/24 around 5pm-9pm. ii. ETA: This issue should be completed by Friday, 11/15/24.

katiejnete avatar Nov 10 '24 06:11 katiejnete

  1. Progress: Waiting for updated PR with changes to be reviewed.
  2. Blockers: None
  3. Availability: Weekday nights
  4. ETA: Pending updated PR review.

katiejnete avatar Nov 15 '24 00:11 katiejnete