frakti permissions cleanup about frakti HOT 13 CLOSED

Thanks! @feiskyer I believe @bergwolf 's contribution would be strong reference as new frakti maintainer.

I believe @Crazykev @heartlock will still be able to assign issues, I would like to mentor them go through membership ladder (and @bergwolf as well).

@cblecker Please kindly give me some time to fix the legacy issues here. Any deadline from your side?

from frakti.

@gnawux @bergwolf I'm not active for the project recently and I'd like to remove myself from the maintainers' list. Would some of you replace me in the kubernetes/frakti-maintainers and kubernetes/frakti-admins team?

from frakti.

No specific deadline, no. As long as it’s in progress, I’m happy.

If there is anything I can do to help, please let me know.

from frakti.

Thanks @feiskyer.

Agree with @resouer, I think @bergwolf, who is in Berlin this week and not online at this time, will continue this work.

from frakti.

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from frakti.

/remove-lifecycle stale

@resouer @bergwolf Any update on this?

from frakti.

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from frakti.

/remove-lifecycle stale

@resouer @bergwolf Any update on this?

from frakti.

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

from frakti.

/remove-lifecycle stale

from frakti.

@resouer @feiskyer
Checking back in regarding outside collaborators. At this point it's been over a year since the original issue was created 😬 We're now actively planning to clean up outside collaborators org wide on December 1st.

@ZeroMagic has been active ideally should apply for membership (along with being added to frakti-maintainers).

@Crazykev, @heartlock, @bergwolf - have not been active in the past year (<5 Devstats recorded contributions in the last year) and I would suggest removal over applying for org membership. -- As a note, even if removed, it does not stop people from contributing. It just means they'd have less permissions (would need /ok-to-test on PRs etc).

How would you like to proceed?

from frakti.

Permissions have been cleaned up. @Crazykev, @heartlock, @bergwolf if you need permissions to continue to work on fraki, Please go ahead and file for org membership and we can pursue adding you the appropriate groups for repo permissions 👍

If you have any questions, please don't hesitate to reopen or ping me on slack.

Thanks!
/close

from frakti.

@mrbobbytables: Closing this issue.

from frakti.