Review Inactive Team Members

[t-will-gillis]

Review of Inactive Website Team Members

Inactive Members

Developers: If your name is on the following list, our team bot has determined that you have not been active with the Website team in the last 30 days. If you remain inactive or we don't hear back from you in the upcoming weeks, we will unassign you from any issues you may be working on and remove you from the 'website-write' team.

@aadilahmed
@adom2128
@aidenjlee4321
@amandaputney
@Carlos-A-P
@carlosm22700
@Chrisklangley
@chrjl
@elizabethhonest
@GinaCastromonte
@GioMogi
@gizmo572
@hfla-website-checklist
@howdyjessie
@jaasonw
@jenjenkayi
@johnBueno31
@kevin-421
@kimberlytanyh
@Kle012
@k-rewd
@KuanHsienYEH
@kwangric
@MattChau01
@max1million101
@mjshelton12
@mshirk2
@nssensalo
@quyson
@rankdjr
@salomenebiyu
@santisecco
@Shikha0428
@shi-kuang
@siddhanthiyer-99
@tesiahwang
@thisisdientran
@vraer
@YolandaHaynes
@zachmyu
@zkamenov

How you can remain active

The bot is checking for the following activity:

• If you are assigned to an issue, that you have provided an update on the issue in the past 30 days. The updates are due weekly.
• If your issue is a Draft in the "New Issue Approval" column, that you have added to it within the last 30 days.
• If you are reviewing PRs, that you have posted a review comment within the past 30 days.
• If you are newly onboarded, that you are assigned to your "Pre-work checklist" and you have cloned the HfLA website repo to your personal repo.

If you have been inactive in the last 30 days (using the above measurements), you can become active again by doing at least one of the above actions. If you do not do at least one of the above actions, the bot will automatically remove you from the 'website-write' team in the next 30 days.

Did we make a mistake?

If you were active during the last 30 days (using the above measurements) and the bot made a mistake, let us know: Copy the following message into a comment below, add the pertinent issue or PR number, then select "Comment". Next, select "...", then "Reference in a new issue". Watch demo

The Hack for LA website bot made a mistake!
I am responding to Issue #6554 because I have been active.
See my Issue #{_list issue_} or my review in PR #{_list PR_}

## Dev Leads
This member believes that the bot has made a mistake by placing them on the "Inactive Member" list. Please see the referenced issue.

After you leave the comment, please send us a Slack message on the "hfla-site" channel with a link to your comment.

Temporary leave

If you have taken a temporary leave, and you have been authorized to keep your assignment to an issue:

• Your issue should be in the "Questions/ In Review" column, with the ready for dev lead label and a note letting us know when you will be back.
• We generally encourage you to unassign yourself from the issue and allow us to return it to the "Prioritized backlog" column. However, exceptions are sometimes made.

Removed Members

Developers: If your name is on the following list, our team bot has determined that you have not been active with the Website team for over 60 days, and therefore you have been removed from the 'website-write' team.

@adrianang
@allison-truhlar
@anjolaaoluwa
@atbalaji
@blulady
@ChrisKildunne
@coding-yost
@crystallyyy
@dimiprousalis
@harimwoo
@jackyuan1
@james-aguirre
@JanineSooThow
@Jfong1218
@jlevot
@johnApale
@Josiah-O
@Joyce750526
@jtkabenni
@kevin31yu
@kianaeunice
@KyleA99
@liamtirney
@LukeLowrey2
@n2020h
@ndmoc
@nnr-nnr
@ortegaa32
@Ovando21
@ronaldpaek
@samuelkhong
@sopheak012
@tkozek
@Tomomi-K1
@wanyuguan

If this is a mistake or if you would like to return to the Hack for LA Website team, let us know: Copy the following message into a comment below then select "Comment". Next, select "...", then "Reference in a new issue". Watch demo

The Hack for LA website bot removed me!
I am responding to Issue #6554 because I want to come back.
Please add me back to the 'website-write' team, I am ready to work on an issue now.

## Dev Leads
This member was previously on the 'website-write' team and is now asking to be reactivated. Please see the referenced issue.

After you leave the comment, please send us a Slack message on the "hfla-site" channel with a link to your comment.

Dev Leads

This issue is closed automatically after creation. If a link referred you to this issue, check whether:

• A "Removed Member" is requesting reactivation to the 'website-write' team. If so, confirm that the member is/was a part of HfLA, then reactivate and inform them via a comment on the referring issue as well as via Slack.
• An "Inactive Member" believes that the bot has made a mistake. If so, determine whether the member has or has not been active based on the issue or PR number provided in the member's comment. If multiple members are being inappropriately flagged as "inactive" by the bot, then submit an ER / Issue in order to deactivate the schedule-monthly.yml workflow so that the cause of the bug can be investigated and resolved.

[roslynwythe]

@t-will-gillis We have a member @DakuwoN who had left for a bit but returned and self-assigned #6484 two weeks ago. He had posted several comments and the issue was closed 3 days ago but the next day he received an email regarding inactivity. He still has membership in website-write and his GitHub handle does not appear on this page.

[roslynwythe]

@t-will-gillis I think we want to maintain the elizabethhonest account, because it is this account that merges win data into hackforla/website.

Also I noticed the account hfla-website-checklist and I don't know if need that account, do you?

Also, vraer is Vanessa, the writer and developer working on the new wiki. Most of her work is in the website-wiki repo, but Bonnie does create issues for her in hackforla/website so she might want Vannesa to maintain rights in our repo

[t-will-gillis]

PLEASE SEE THE MESSAGE BELOW

@agutiernc
@colin-macrae
@DakuwoN
@djbradleyii
@gdkoo
@GRK1998
@nelsonuprety1

Hello all- due to a snafu, last month's notification list was initially and mistakenly duplicated on this month's list, and thus your GitHub handles were also mistakenly duplicated, i.e. and you were initially included on the list of inactive team members above.

This message is to confirm that:

• the automation DID find activity from you over the last month, and
• you are NOT on the 'notification' list for this month and your GitHub handle is no longer listed on this issue, and
• you are NOT at risk for the bot removing you from the repo next month, and
• as long as you stay active over the coming month, the bot will register your activity and your handle will not be included on next month's list.

Apologies for any confusion. Please let me know if you have any questions.
Thanks!

PS If sometime in the future your access to HfLA is removed, whether due to inactivity or due to a mistake, you can send us a message to let us know that you would like us to restore your access- we will be happy to help you out!!!

[t-will-gillis]

@t-will-gillis We have a member @DakuwoN who had left for a bit but returned and self-assigned #6484 two weeks ago. He had posted several comments and the issue was closed 3 days ago but the next day he received an email regarding inactivity. He still has membership in website-write and his GitHub handle does not appear on this page.

@roslynwythe Please see the message above. These members' GitHub handles were mistakenly copied from the previous month and were initially listed on the issue. However, the bot did record their activity in the last month and they were not and are not at risk of being removed by the bot next month. The list currently shown is the accurate report.

@t-will-gillis I think we want to maintain the elizabethhonest account, because it is this account that merges win data into hackforla/website.

Also I noticed the account hfla-website-checklist and I don't know if need that account, do you?

Also, vraer is Vanessa, the writer and developer working on the new wiki. Most of her work is in the website-wiki repo, but Bonnie does create issues for her in hackforla/website so she might want Vannesa to maintain rights in our repo

Vanessa posted a comment on #2676 which the bot will see as activity. Since there is activity this month, "Vraer" will not be on next month's list.

"elizabethhonest" and "hfla-website-checklist" keep appearing on these lists but the bot has not removed them. I will add a note to include these bot on the 'Permanent members' list so these don't appear on the list.

[colin-macrae]

The Hack for LA website bot made a mistake as I have done PRs recently!
I am responding to Issue #6554 because I have been active.
See my Issue #{list issue} or my review in PR #{list PR}

Dev Leads

This member believes that the bot has made a mistake by placing them on the "Inactive Member" list. Please see the referenced issue.

[ExperimentsInHonesty]

@t-will-gillis

Collin's links are
Issues assigned to colin-macrae
PRs reviewed by colin-macrae

[roslynwythe]

@colin-macrae Indeed the bot made a mistake. Please see #6554 (comment) and accept our apologies for the confusion. Just to clarify, your permissions are still intact.