Decision: limiting-factor access to devops resources

Governance and decisions
1

I would like to have the access required to perform devops tasks for forgefriends.

  1. If you agree, please simply add :heart: to this issue.
  2. If you disagree or have reservations, please write them in a comment below and I will do my best to address them.

This application follows the forgefriends decision making process.

Pledge

I pledge to act in accordance with the code of conduct, and manifesto.

If there is an agreement for me to have access to this resource, I understand it will automatically be revokd if I do not contribute in a concrete way during more than one month.

Background

See my public activity.

1 Like
2

This is heavily inspired from #160 - [AGREEMENT] patdyn Application to Contributors Team - forgejo/governance - Codeberg.org

3

Thanks for this application. It is not really necessary given that forgefriends is essentially in reboot mode after sleeping during a few years, but it sets a useful example going forward.

You have been granted access to the LXC containers that run the forgefriends & f3 resources. There are backups and no users at the moment: it really is a no risk situation. The benefit of the early days of booting a community (or rebooting in this case).

1 Like