-
-
Notifications
You must be signed in to change notification settings - Fork 766
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
Review Inactive Team Members #6554
Comments
@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 |
@t-will-gillis I think we want to maintain the Also I noticed the account 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 |
PLEASE SEE THE MESSAGE BELOW @agutiernc 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:
Apologies for any confusion. Please let me know if you have any questions. 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!!! |
@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.
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. |
The Hack for LA website bot made a mistake as I have done PRs recently! Dev LeadsThis member believes that the bot has made a mistake by placing them on the "Inactive Member" list. Please see the referenced issue. |
Collin's links are |
@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. |
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:
Draft
in the "New Issue Approval" column, that you have added to it within the last 30 days.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
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:
ready for dev lead
label and a note letting us know when you will be back.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
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:
schedule-monthly.yml
workflow so that the cause of the bug can be investigated and resolved.The text was updated successfully, but these errors were encountered: