podman-compose
podman-compose copied to clipboard
containers
Looking for new maintainers of podman-compose.
We have not heard from @muayyad-alsadi for many months, and wish him well. But if he no longer has the time or ability to maintainer this repository, I think it is time to open it up to others.
If you are interested in helping maintain this project then please comment on this issue.
If @muayyad-alsadi wants to continue working on this Repo or to choose some people to help maintainer it please respond within the next 30 days, otherwise I will add a couple of new maintainers.
For the record I've been contacting different people regarding helping to maintain podman-compose during last month, which is probably what triggered this discussion on Github.
I'm pointing this out as a way to say that there's at least one person who thinks he's strongly committed to move this project forward.
~Hey, I would be interested to help~ - finished my first contribution (https://github.com/containers/podman-compose/pull/830) which needs some tests added :)
Currently using the latest master as the last release misses some features I depend on ✌🏻
@SebTM I got maintainer permission around a week ago, so the repository is unblocked for contributions now.
I still waited some time in case Muayyad would resume active maintenance as there was one merged PR on 25 February. There's no activity again and no responses to previous emails, so I'm assuming maintainership now.
@p12tic wanted to ask if there are any plans to make a new release as quite a few useful features have been merged since the last one, such as profiles. Also good luck, hope you will have a good maintainership!
@filipdutescu The release has been done. I don't have access to pypi, so the release will not be transferred there.
If you are interested in helping maintain this project then please comment on this issue.
I'm willing to help with this project sometimes too, but can't make any huge time commitments currently.
For pypi, the people running it are very helpful usually. It would be worth a try if an established member of this project sends them a mail to explain the situation.
I have access to PyPI but @p12tic removed my write access to this repo! we need a co-maintained not another xz-backdoor.
@rhatdan please add more maintainers, but please don't remove my access.
I have access to PyPI but @p12tic removed my write access to this repo! we need a co-maintained not another xz-backdoor.
This was last ditch effort to preserve code quality on the repo because you were merging PRs with broken tests and unaddressed review comments. Additionally, I've tried to contact you multiple times since January and none of my 8 emails have been answered so far.
We would have addressed this topic after a private discussion via email, but I didn't get a reply...
@rhatdan
Could you confirm that @p12tic the new maintainer of the project? I'm asking because you are:
- A member of Containers organisation.
- The creator of this GitHub Issue.
The reason for my inquiry is:
- I have been a contributor to this repository even before it was transferred to Containers.
- I was the original author of the
podman-composepackaging PR and am currently one of the two PyPI maintainers of this package, along with @muayyad-alsadi. - @p12tic has requested that I grant him rights on PyPI.
Additionally, it would be beneficial if the Containers organisation could reach an agreement with @muayyad-alsadi, the original author of this package.
hello, @p12tic reached me and restored my write access and we sorted out the misunderstanding.