[AGREEMENT] @wetneb applying to the mergers team #54

wetneb commented 2024年01月03日 09:46:50 +01:00

Application

I propose to become part of the the mergers team, and to participate in reviewing and merging pull requests in accordance with the pull requests agreement.

1. If you agree, please simply add a 👍 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 Forgejo decision making process.

Pledge

I pledge to act in accordance with the code of conduct, and all other rules and processes agreed via the Forgejo decision making process.

Given my limited knowledge of Go and of Forgejo's code base, I pledge to err on the side of caution and defer to other contributors for code reviews, initially contributing reviews more from a user's standpoint.

If there is an agreement for me to be a member of the team, I will consider applying again a year later.

Background

My interest in Forgejo comes from:

• the need for a self-hosted forge at Kanthaus, which I maintain at git.kanthaus.online
• the broader interest in migrating FOSS projects I am involved in out of GitHub, to an open source platform
• enthusiasm for Forgejo's federation plans
• interest in experiencing participation to a FOSS project with a thought-through governance model

So far I have contributed some pull requests focused around pain points encountered during my own use of the platform.

My primary open source project is OpenRefine, a data cleaning tool.

### Application I propose to become part of the [the mergers team](https://codeberg.org/forgejo-contrib/governance/src/branch/main/TEAMS.md#mergers), and to participate in reviewing and merging pull requests in accordance with the [pull requests agreement](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). 1. If you agree, please simply add a 👍 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 Forgejo [decision making process](https://codeberg.org/forgejo-contrib/governance/src/branch/main/DECISION-MAKING.md). ### Pledge I pledge to act in accordance with the [code of conduct](https://codeberg.org/forgejo/code-of-conduct/), and all other rules and processes agreed via the Forgejo [decision making process](https://codeberg.org/forgejo-contrib/governance/src/branch/main/DECISION-MAKING.md). Given my limited knowledge of Go and of Forgejo's code base, I pledge to err on the side of caution and defer to other contributors for code reviews, initially contributing reviews more from a user's standpoint. If there is an agreement for me to be a member of the team, I will consider applying again a year later. ### Background My interest in Forgejo comes from: * the need for a self-hosted forge at [Kanthaus](https://kanthaus.online), which I maintain at [git.kanthaus.online](https://git.kanthaus.online/) * the broader interest in migrating FOSS projects I am involved in out of GitHub, to an open source platform * enthusiasm for Forgejo's federation plans * interest in experiencing participation to a FOSS project with a thought-through governance model So far I have contributed [some pull requests](https://codeberg.org/forgejo/forgejo/pulls?q=&type=all&sort=&labels=&milestone=0&project=0&assignee=0&poster=94198) focused around pain points encountered during my own use of the platform. My primary open source project is [OpenRefine](https://openrefine.org), a data cleaning tool.

earl-warren commented 2024年01月18日 18:04:28 +01:00

The delay has passed and since there has been no concern and only approvals, you are now part of the mergers team. The only thing left to do is for you to send a PR to add yourself to the team. 🎉

The delay has passed and since there has been no concern and only approvals, you are now part of the mergers team. The only thing left to do is for you to send a PR to add yourself to the team. 🎉

earl-warren commented 2024年06月29日 11:05:32 +02:00

@wetneb you applied before the hard fork, back when it had a different impact to be in the mergers team. There were multiple branches, each commit was scrutinized on a weekly basis and could hardly be compromised by accident or malice, there was no automated release process in place and a change landing in a branch could not end up on on someone else machine 24h later.

Since then having merge rights has a different meaning and the consequences of misusing them are more impactful.

Given that you've not been active in Forgejo lately, I mean to ask if you are ok with this.

@wetneb you applied before the hard fork, back when it had a different impact to be in the mergers team. There were multiple branches, each commit was scrutinized on a weekly basis and could hardly be compromised by accident or malice, there was no automated release process in place and a change landing in a branch could not end up on on someone else machine 24h later. Since then having merge rights has a different meaning and the consequences of misusing them are more impactful. Given that you've not been active in Forgejo lately, I mean to ask if you are ok with this.

wetneb commented 2024年06月29日 23:59:51 +02:00

If you would like me to remove myself from the mergers team, I am happy to do so. For the record I never expressed the need to be part of this team, it was your suggestion that I apply.

Perhaps it could be worth introducing an inactivity threshold to systematize this (to avoid having to ask yourself for people to voluntary remove themselves, which is always a bit difficult to do I would say)

If you would like me to remove myself from the mergers team, I am happy to do so. For the record I never expressed the need to be part of this team, it was your suggestion that I apply. Perhaps it could be worth introducing an inactivity threshold to systematize this (to avoid having to ask yourself for people to voluntary remove themselves, which is always a bit difficult to do I would say)

earl-warren commented 2024年06月30日 09:01:12 +02:00

I never expressed the need to be part of this team, it was your suggestion that I apply.

And that was helpful.

If you would like me to remove myself from the mergers team, I am happy to do so.

Noone expressed any concerns regarding your presence and I do not feel that the rights you have are in any danger of being misused. I realized this week, looking at the team that the burden of responsibility evolved much more than could have ever been anticipated. Since you've not been active lately and that you applied on my suggestion, to help bootstrap this team, I thought I'd notify you of this change.

If I was in your position I'd prefer to leave the team because I'm a little stressed when my accounts have elevated permissions in a project I'm not actively involved in. But this is your decision to make.

The inactivity expiration already exists since a position in a team is only valid for one year and needs to be renewed. If they do not, they will eventually be removed. What was not anticipated is that the profile of a team would change so rapidly.

> I never expressed the need to be part of this team, it was your suggestion that I apply. And that was helpful. > If you would like me to remove myself from the mergers team, I am happy to do so. Noone expressed any concerns regarding your presence and I do not feel that the rights you have are in any danger of being misused. I realized this week, looking at the team that the burden of responsibility evolved much more than could have ever been anticipated. Since you've not been active lately and that you applied on my suggestion, to help bootstrap this team, I thought I'd notify you of this change. If I was in your position I'd prefer to leave the team because I'm a little stressed when my accounts have elevated permissions in a project I'm not actively involved in. But this is your decision to make. The inactivity expiration already exists since a position in a team is only valid for one year and needs to be renewed. If they do not, they will eventually be removed. What was not anticipated is that the profile of a team would change so rapidly.

wetneb commented 2024年06月30日 09:49:15 +02:00

Ok, then I can reassure you about my stress level: I'm doing well. I would let the expiration period play its role.

Ok, then I can reassure you about my stress level: I'm doing well. I would let the expiration period play its role.

earl-warren commented 2024年06月30日 10:34:35 +02:00

I'm happy for you 😄

I'm happy for you 😄

earl-warren commented 2025年03月25日 02:01:12 +01:00

@wetneb it has been more than a year, would you like to apply?

@wetneb it has been more than a year, would you like to apply?

wetneb commented 2025年03月25日 08:09:43 +01:00

Although I hope to get active again this summer, I think it's worth leaving the Mergers team. Should I open a new issue for that?

Although I hope to get active again this summer, I think it's worth leaving the Mergers team. Should I open a new issue for that?

earl-warren commented 2025年03月25日 09:05:47 +01:00

You can just open a pull request removing your name from the TEAMS file. And I'll support your application this summer.

You can just open a pull request removing your name from the TEAMS file. And I'll support your application this summer.