pyzeebe
pyzeebe copied to clipboard
camunda-community-hub
Looking for additional maintainer(s)!
Hello all, we are searching for another maintainer or two for Pyzeebe! Please note our maintainer and reviewer expectations.
Please reply if you are interested :)
I've attempted to solve some issues but it seems no active maintainers are available and the original @JonatanMartens is revoked. Could you suggest a solution other than creating another pyzeebe?
Hi @yuval9313. The only maintainer is @JonatanMartens (who still has Maintainer access, where are you seeing that it is revoked?)
I agree that I'd rather not fork pyzeebe, which is why we're looking for another Maintainer. Is that something you'd be able to take on?
Hi! I would like to be maintainer of pyzeebe. Problem is that my English is not very good, so I have some problems writing docs.
@dimastbk Hi Dmitriy! Glad to hear it, I'll give you Maintainer permissions now! 🚀
No worries about your English, we are a global community so we have many contributors where English isn't their first language. If you ever want a proofreader, feel free to tag me and I am happy to review! :)
@xomiamoore could you remove these actions from the branch ruleset?
- unit-test (3.6)
- unit-test (3.7)
Now supported python 3.8+
@xomiamoore and could you see PR rules? Now review from @JonatanMartens is required (see #397).
@dimastbk Added you as an exception to the branch protections, you should be able to merge now!
@xomiamoore Hi! Could you see https://github.com/camunda-community-hub/pyzeebe/pull/398#issuecomment-2113964308 ?
@dimastbk I saw you were able to merge it, did closing and reopening give you the right permissions?
@xomiamoore No, I made a hack: I added empty jobs for python3.6 and python3.7 to workflow, see https://github.com/camunda-community-hub/pyzeebe/pull/398/commits/e9bf785eeace61712b172ab78517bedcdad74a73. But we should remove these jobs from branch ruleset, because of EOL of these python versions were in 2021 and 2023.
@dimastbk Hi! I see you've done a lot of work on this repo lately, thank you for that. Do you plan to make a new release soon?
@xomiamoore @JonatanMartens Hi! Can you add PYPI_TOKEN (https://github.com/camunda-community-hub/pyzeebe/blob/master/.github/workflows/publish.yml#L26) to environment variables? As I see on pypi, @JonatanMartens is owner of https://pypi.org/project/pyzeebe/. I would like to create new prerelease https://github.com/camunda-community-hub/pyzeebe/releases
Hey @dimastbk @xomiamoore, I think Camunda should create a pypi organization. Let me know when it is set up and I will transfer pyzeebe to the organization.
The PYPI_TOKEN environment variable is a github secret, which I don't have access to change currently.
I would also like to add some maintainers to the read-the-docs. @xomiamoore let me know who I can add.
@JonatanMartens, I got this notice when I tried to sign up for a pipy org, so not sure how long it will take to get a Camunda organization. Until then, I can add you as an admin to the repo to add the token as a secret?
@dimastbk would you be interested in being added to the read-the-docs as a maintainer as well?
@xomiamoore feel free to add me as an admin, will add the token asap
@JonatanMartens hi. Can you send invite again? I missed the link and it has expired.
Hello, I am interessed, @xomiamoore could you link maintainer and reviewer expectations again the link is broken.
Hey @felicijus -- thanks for the heads up, it's here now: Maintainer and reviewer expectations
@dimastbk, @JonatanMartens, do you need another maintainer?
@JonatanMartens Hi. Can you send invite to RTD again? I missed the link and it has expired.