- Issue created by @c-logemann
- 🇩🇪Germany c-logemann Frankfurt/M, Germany
Already contacted two of the current maintainers. But the one I reached at slack cannot add additional maintainers. Will now contact rest of them.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
These offers need to about a single request. Since it has been created as offered to be co-maintainer, it cannot be changed to be an offer to be the new project owner.
- 🇩🇪Germany c-logemann Frankfurt/M, Germany
@avpaderno I didn't know that yet. But it makes sense if this issue should be part of the official process. I will add a second issue and connect them.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
@c-logemann You need to open a single issue, but that issue needs to be for the higher role you want to get. That cannot be changed five months after the issue was created, though.
- 🇩🇪Germany c-logemann Frankfurt/M, Germany
@avpaderno OK you wrote "single request" but I think it's not so obvious on this doc page → . Now I will follow the process but I think it's a little bit unflexible in cases like this. First I came along and just wanted to offer my help. Yesterday I chatted with a maintainer and he gave me the idea for taking over ownership.
Changes without discussion with existing maintainers is currently even too easy in my opinion. In the past I had a situation where I was only a Co-Maintainer and was suddenly removed by a new owner who dropped any support for the old code. On another project I had a discussion with an owner (without any co-maintainers) and he just decided to give me ownership. What if the current maintainers of this project also want to do this in this case?
- 🇮🇹Italy apaderno Brescia, 🇮🇹
Generally, there should be some communication. I can imagine somebody being removed as co-maintainer/maintainer because not being active in that role, though.
As for being appointed as project owner instead of maintainer, that should not happen so frequently, as it requires at least the role of site moderator, to be able to change a node owner. If that happens, and it is not the desired result, I suggest creating an issue in the site moderators queue.