@sean-k1 are you happy with that?

@julien-duponchelle sure!

Invitation sent

@julien-duponchelle
Sorry Julien, but I have an error in pypi version 0.45.0, 1.0.0 ,1.0.1 and I don't have authorization to delete it, could you please delete it?

Should be good now

@dongwook-chan are you happy with that?

Yes!

Invitation sent!

@julien-duponchelle
Thank you for granting me collaborator rights on the python-mysql-replication project. 😁 I truly appreciate the trust and opportunity you've extended. However, I noticed that I was given "collaborator" status rather than the "maintainer" role as previously discussed. I wanted to check if this was intentional or an oversight. Having maintainer rights would assist in streamlining some of the tasks I anticipate, especially with the upcoming Hacktoberfest preparations.

I'm happy with that but I don't know how to do it. I see only the option to add collaborator but I don't see a way to increase the permission. I wonder If I need to move the project to an org for that.

That's a good idea. Maybe a code of conduct could help. Do you have an example ? I think I could draft something and share it the community.

I think your suggestion is really a good one, but I'd like to propose this before we go into details:

If you want to solve problems like async ones as you said, then you can refer to examples about management other open source project maintainers did. Their trial and error would be helpful.

However, if you want to expand the project and have it become a part of an industry or other, you can refer to documents related to community organization. Approaches such as community organization would be more beneficial in this case than relying on the personal experiences of other project maintainers.

You can decide on the direction you want to take on your own, or with the new additional maintainers @dongwook-chan @sean-k1. I can find and share some example or document, if needed, after the decision on the direction has been made.