Closed mazzystr closed 2 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
/close
@kubevirt-bot: Closing this issue.
/reopen
@tylerauerbeck: You can't reopen an issue/PR unless you authored it or you are a collaborator.
@mazzystr Didn't think I would have the power to reopen, but gave it a shot anyway. This probably needs reopened as there is still some work to do here.
/remove-lifecycle rotten
/reopen
@cwilkers: Reopened this issue.
Searching the actual repo content finds many instances of the potentially offensive language, but mostly in dated blog posts. Rather than try to rewrite so many older posts, we may choose to leave older posts alone, and adopt a new CI check to warn if new content contains words deemed potentially offensive.
Now working from a new search:
git grep -I -E 'master|slave|whitelist|blacklist' -- \
':!vendor' ':!cluster-up' ':!cluster-sync' ':!*generated*' ':!*_posts*'
Review repo for offensive langauge