-
Notifications
You must be signed in to change notification settings - Fork 28
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
Maintaining pytest-cookies 🍪 #41
Comments
Hi @hackebrot yes I have used Cookiecutter and pytest |
Hi @hackebrot hope you are well. |
@hackebrot I am interested in helping to maintain |
@hackebrot would you consider submitting https://docs.pytest.org/en/6.2.x/contributing.html#submitting-plugins-to-pytest-dev |
I will happily help with migration work and future maintenance/modernization. Let me know where I can help |
@JonZeolla I think any migration to pytest-dev would have to come from @hackebrot as the project owner if he wanted to pursue that option. The migration doc does mention a changelog requirement so I'm wondering if the "github releases" changelog would be sufficient? |
Hi folks! 👋🏻 Thank you for offering to help with maintenance for this plugin. I do wonder whether it makes more sense for this plugin to be migrated to the Cookiecutter org. What do you think? |
That sounds reasonable to me |
@hackebrot any update on that migration? I have some modernization work that I would like to get into this project. Let me know if I can help with anything - I am trying to avoid creating a fork if possible. |
I'm keen for this modernisation too, and can help if required. The baseline should be Python 3.7, pytest 4 and cookiecutter 2 now (at least). update: See #63 |
Agree with this; PR noted above fixes some issues we were seeing |
@hackebrot I'm still happy to take over this project if you are willing to transfer it to me (or into an org). I would be looking to merge my modernization PR #55 and pick up other modernization efforts like #63, etc. |
Hey @hackebrot , just following up on above; this is a super useful project and would hate to see it become unmaintained. |
What is the current status? Did someone need to do a fork to get it working again on GHA windows? |
If you need something that works, then you can install the fixed branch of my fork, as below. But it really needs merging here.
|
@JonZeolla, do you think it's time to kick-off a PEP 541 request to transfer the project? Last release was nearly 2 years ago and it's been broken since May 2022. |
Hi @jamesmyatt! 👋🏻 As you can tell, I don't actively work on this project any longer. I should have bandwidth to publish a new release this week, if you can help me figure out what's most pressing. I reckon it's #63? |
Hi @hackebrot . Thanks for all of your work on this project. If you have the time, then I think that #63 should be sufficient to support cookiecutter 2.1.0 onwards. Thanks. However, if you do have the time, then it might be more efficient to just work on adding maintainers, like @phillipahereza (#40), @AGMETEOR (#39) and @JonZeolla, and/or transferring it to the cookiecutter or pytest-dev organisations. Then they can work on getting a new release out. |
I, too, would like to add my gratitude to @hackebrot for creating this important tool and, second, express an interest in seeing it transferred to a group of people who can continue to move it forward. I bet everyone here knows the experience of letting a project fall out of service. This project has legs :). Can you get it freed up to move again @hackebrot ? If you're interested in working on it in the future, maybe the best option is to add collaborators on this repository. You can add some of the people mentioned above. Please feel free to add me as a maintainer if you like. |
Hi @phillipahereza & @AGMETEOR! 👋
Thanks so much for your interest in helping out with maintaining pytest-cookies. Have you folks used pytest and cookiecutter before?
The text was updated successfully, but these errors were encountered: