Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Looking for additional maintainer(s)! #381

Open
xomiamoore opened this issue Jan 22, 2024 · 14 comments
Open

Looking for additional maintainer(s)! #381

xomiamoore opened this issue Jan 22, 2024 · 14 comments

Comments

@xomiamoore
Copy link
Contributor

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 :)

@yuval9313
Copy link
Contributor

yuval9313 commented May 11, 2024

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?

@xomiamoore
Copy link
Contributor Author

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?

@dimastbk
Copy link
Collaborator

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.

@xomiamoore
Copy link
Contributor Author

@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! :)

@dimastbk
Copy link
Collaborator

@xomiamoore thanks!

@dimastbk
Copy link
Collaborator

@xomiamoore could you remove these actions from the branch ruleset?

  • unit-test (3.6)
  • unit-test (3.7)

Now supported python 3.8+

@yuval9313
Copy link
Contributor

Hey @xomiamoore I could certainly try

@dimastbk
Copy link
Collaborator

dimastbk commented May 13, 2024

@xomiamoore and could you see PR rules? Now review from @JonatanMartens is required (see #397).

@xomiamoore
Copy link
Contributor Author

@dimastbk Added you as an exception to the branch protections, you should be able to merge now!

@dimastbk
Copy link
Collaborator

@xomiamoore no, I can't merge #398

image

@dimastbk
Copy link
Collaborator

@xomiamoore Hi! Could you see #398 (comment) ?

@xomiamoore
Copy link
Contributor Author

@dimastbk I saw you were able to merge it, did closing and reopening give you the right permissions?

@dimastbk
Copy link
Collaborator

dimastbk commented Jun 4, 2024

@xomiamoore No, I made a hack: I added empty jobs for python3.6 and python3.7 to workflow, see e9bf785. But we should remove these jobs from branch ruleset, because of EOL of these python versions were in 2021 and 2023.

@ArtemIlinArammeem
Copy link

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants