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

Review Inactive Team Members #363

Closed
t-will-gillis opened this issue Nov 22, 2023 · 3 comments
Closed

Review Inactive Team Members #363

t-will-gillis opened this issue Nov 22, 2023 · 3 comments

Comments

@t-will-gillis
Copy link
Owner

t-will-gillis commented Nov 22, 2023

DRAFT

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 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.

@ cnk
@ arfgit
@ Abrosss
@ 93Belen
@ bootcamp-brian

Did we make a mistake?

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 done some kind of activity in the past 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 were active during the last 30 days (using the above measurements) and the bot made a mistake, let us know by responding in a comment below with the following message, then selecting "Reopen with comment":

I am responding to Issue #363.
The Hack for LA website bot made a mistake, I have been active!
See my Issue # or my review in PR #  

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 try to encourage you to unassign yourself from the issue and allow us to return it to the prioritized backlog. However, exceptions are sometimes made.

Removed Members

Our team bot has determined that the following member(s) have not been active with the Website team for over 60 days, and therefore the member(s) have been removed from the 'website-write' team.

@ cnk
@ averdin2
@ abuna1985
@ ArchilChovatiya
@ arpitapandya
@ elvisEspinozaN
@ aidenshaw07
@ plang-psm
@ bootcamp-brian

If this is a mistake or if you would like to return to the Hack for LA Website team, let us know by responding in a comment below with the following message, then selecting "Reopen with comment":

I am responding to Issue #363.
I want to come back to the team!
Please add me back to the 'website-write' team, I am ready to work on an issue now.

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 the issue is open, check whether:

  • A "Removed Member" is requesting reactivation to the 'website-write' team. If so, reactivate the member and inform them via a comment on this issue as well as via Slack. After informing the member, close this issue.
  • 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.
@t-will-gillis-dummy
Copy link
Collaborator

bot made a mistake

@t-will-gillis-dummy
Copy link
Collaborator

seriously, bot made a mistake

@t-will-gillis
Copy link
Owner Author

The Hack for LA website bot made a mistake!
I have been active! See my Issue # or my review in PR #
I am responding to Issue #363.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Status: QA
Development

No branches or pull requests

2 participants