Move to pytest-dev organization

[nicoddemus]

Please consider transferring this plugin to the pytest-dev organization.

[ftobia]

That's a good idea. Would I retain commit access to the repo (but not the broader org)?

[nicoddemus]

Oh certainly! The idea is to prevent "plugin abandon", which doesn't seem to be the case here of course. You will have full admin rights to the repo.

[ftobia]

This is still a good idea. There's a bit of work that needs to be done to execute on this issue: https://github.com/pytest-dev/pytest/blob/master/CONTRIBUTING.rst#submitting-plugins-to-pytest-dev

Notably make sure these are done:

• PyPI presence with a setup.py that contains a license, pytest- prefixed name, version number, authors, short and long description.
• a tox.ini for running tests using tox.
• a README.txt describing how to use the plugin and on which platforms it runs.
• a LICENSE.txt file or equivalent containing the licensing information, with matching info in setup.py.
• an issue tracker for bug reports and enhancement requests.
• a changelog

[nicoddemus]

@ftobia thanks for getting back to this.

I think the only thing missing is a CHANGELOG of sorts, if I'm not mistaken.

[MRigal]

@nicoddemus and @ftobia the CHANGELOG is now also included :-)

[utapyngo]

And now the project seems abandoned, though it works for me.

[nicoddemus]

Is there still interest in this from the maintainers?

[ssbarnea]

I was about to raise a duplicate ticket with the same question. I really need an test ordering solution but I am inclined not to trust a plugin under a personal organization (mainly due to maintenance risks).

If nothing happened in almost 4 years, I really doubt to see it materializing, even if the effective repository transfer takes minutes (updating info can be done later, especially as github does very good redirects).

@ftobia what do you think?

[ftobia]

I'd still like to see the project moved, and we are blocking on active maintainers. @ssbarnea are you interested?

[ssbarnea]

I can help with maintenance. Lets start by moving the project under pytest-dev and assuring that involved parties have enough permissions to reconfigure it. The move needs to be done by a pytest-dev org admin (requires right to create repo). If i am correct first give Bruno ownership here, so he can initiative transfer.

Do not forget to add me after, so I can take care of CI/CD part.

[nicoddemus]

Sure, fine by me! Who should I add as admin of the project after the move?

It would also be important to add the some people as maintainers in PyPI, or at least setup automatic releases based on pushing something to the repo (often tags).

[ssbarnea]

For pypi, two humans as owners as a safety net but publishing should be done via a bot account, same for the entire pytest-dev org.

[ssbarnea]

@ftobia Can we resume this move? Based on my experience, you just need to send an email similar to https://mail.python.org/pipermail/pytest-dev/2020-August/005000.html -- that is how I did it.

I guess that is needed to assure transparency and to give opportunity to others to look at the project.

[mrbean-bremen]

FWIW, I forked this repo and created pytest-order, which takes the current development version with some merged PRs and fixed CI builds. I also made a PyPi package.
I still hope that the original project will be revived. For the time being I will maintain that fork, but I will happily abandon it if this one is revived.
UPDATE: Renamed repository from pytest-ordering2 to pytest-order.

[nicoddemus]

@mrbean-bremen we can have a grace period to see if @ftobia has something to say, and if not, we can move your fork to pytest-dev if you would like.

[mrbean-bremen]

I've made a separate issue in my fork to handle this.

[mrbean-bremen]

@ftobia - can you please give some feedback on how you would prefer to advance this?

As I wrote above, I have meanwhile made my own fork, where most of the open issues have been resolved. I'm thinking about moving that to pytest-dev, but I would still prefer to have the changes incorporated in this repo and moved that to pytest-dev instead. Most of the changes could easily be transferred, except maybe for the marker name, which I changed to order (as has been proposed in #38, which would not be upwards-compatible).

So I see the following possibilities in order of preference:

• You move this repo to pytest-dev and add some contributors (there have been several people contributing, so I don't think that would be a big issue), to be able to move this along, and give some guidance how you want to progress (especially with the order name). In this case I would try to move over the changes, where it makes sense, and archive the fork.
• You add a note that this repo is no further developed, and point to the fork. In this case I would go and try to move the fork to pytest. Still would want to have you as an additional owner (there maybe several in an organization).
• You do nothing. In this case I will wait a couple of months, and try to move the repo if nothing changes.

Thanks for your work and happy New Year!

You can also PM me as hansemrbean at googlemail.com.

[ssbarnea]

I am happy to see progress on this, especially as I started to avoid plugins not under pytest-dev due to long term maintenance risks. That one is a very useful tool in the shed.

[mrbean-bremen]

@ssbarnea - I decided to wait for a response until begin of March, otherwise I'll try to move my own fork over to pytest-dev.

[nicoddemus]

As commented in pytest-dev/meta#7 (comment), let's move this ahead. 👍