Since nobody objects, I think we can make the transfer. Feel free to transfer to me Andreas.
Cheers On Sun, Oct 2, 2022 at 4:24 AM hansemrbean <hansemrb...@googlemail.com> wrote: > Thank you Sorin and Bruno! > > The documentation ( > https://docs.pytest.org/en/7.1.x/contributing.html#submitting-plugins-to-pytest-dev) > states that the repository can be transferred "if no contributor strongly > objects and two agree". We got two votes, so I will wait a bit more for > objections, and in the case none come will go ahead with the transfer. How > long shall we wait, and who shall the repo be transferred to if nobody > objects? > > Thanks, > > Andreas > > > Am 01.10.2022 um 20:15 schrieb Bruno Oliveira: > > +1 for me too btw. > > Cheers, > > On Sat, Oct 1, 2022 at 5:08 AM Sorin Sbarnea <sorin.sbar...@gmail.com> > wrote: > >> +1 from me. I think we should show that pytest-dev is an open minded >> organisation. I remeber when I lead the move of testinfra into it, where we >> faced a similar dilemma, the fact that it was a little bit more than a >> pytest plugin. Still, it did work, well I say. >> >> To be honest, I reached a point where I do my best to avoid starting to >> use any new library, if that is not hosted under a non personal account — >> just because it is not cool to depend on a single point of failure, one >> that ages too. >> >> Cheers! >> Sorin Sbarnea >> >> On Sat, 1 Oct 2022 at 08:04, hansemrbean via pytest-dev < >> pytest-dev@python.org> wrote: >> >>> This is a followup to an earlier thread ( >>> https://www.mail-archive.com/pytest-dev@python.org/msg02835.html) a >>> year and a half ago, where I asked if it would be possible to transfer >>> pyfakefs (https://github.com/jmcgeheeiv/pyfakefs) to pytest-dev. This >>> was eventually declined, mostly because pyfakefs is not a pure pytest >>> plugin, but also supports unittest and other test environments. >>> >>> The maintainer of pyfakefs, John McGehee, has contacted me, and asked me >>> to take over, as he will not be able to maintain the package anymore. While >>> discussing this, we again came to the conclusion that moving the repository >>> to pytest-dev would make much sense. I asked Bruno Oliviera (who helped >>> with with the transfer of pytest-order) in a private discussion, and he >>> encouraged me to try again, so here I am... >>> >>> I want to reiterate the reasons for the transfer I gave last time, and >>> maybe elaborate a bit more. >>> >>> - ensure continued maintenance: I will be the only maintainer now, and >>> the move to an organization would make it possible to add other owners, and >>> will probably make it more likely to find another maintainer (given the >>> visibility and size of pytest-dev). There is also the bus factor, which I >>> cannot discard given that I'm not young. >>> >>> - increase compatibility with pytest and pytest plugins, >>> >>> - improve visibility of the package, especially for pytest developers: >>> >>> pyfakefs was originally developed inside Google with the possibility to >>> mock some filesystem modules and later released on GitHub; John McGehee >>> added specific support for unittest in 2014, and another contributor added >>> pytest support in the form of the fs fixture a bit later (2015). Since then >>> the usage of pyfakefs has steadily drifted from unittest to pytest, as can >>> be seen by the usage in other repositories (I did some usage statistics for >>> dependent repos in GitHub) and by new issues, and the support for pytest >>> has been improved. I personally like pytest and see it as the superior >>> testing framework, so I'm also interested in improving the compatiblity of >>> pyfakefs with other pytest plugins - which will be easier if it is clearly >>> visible as part of the pytest environment. >>> >>> - ideally, benefit from the larger community to get more code reviews >>> and issue reports: if think this is obvious. >>> >>> Last time it had also been proposed to move to https://github.com/PyCQA >>> instead, but I really don't see a match here. >>> https://github.com/cogs-of-testing had also been mentioned, and while >>> it sounds like a good match, it has yet to be brought to life. >>> >>> Let me know if there is anything I can do to make pyfakefs better >>> compatible with pytest-dev, or if you need more information. >>> >>> Thanks in advance, >>> >>> Andreas >>> >>> >>> >>> _______________________________________________ >>> pytest-dev mailing list >>> pytest-dev@python.org >>> https://mail.python.org/mailman/listinfo/pytest-dev >>> >> -- >> -- >> Cheers, >> Sorin >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev@python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> > > [image: width=] > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <#m_-8727644505780217632_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
