On Tue., Jun. 22, 2021, 14:50 Glenn Linderman, <v+pyt...@g.nevcal.com> wrote:
> On 6/22/2021 12:52 PM, Brett Cannon wrote: > > > > On Mon, Jun 21, 2021 at 4:09 PM Glenn Linderman <v+pyt...@g.nevcal.com> > wrote: > >> On 6/21/2021 2:31 PM, Christopher Barker wrote: >> >> >> By contrast, requiring a github account for reporting bugs also makes >>> python an unwelcoming place for non-developers in general. Github is a >>> developers' social network, "mere" users are much less likely to want to >>> be part of it. Many will just silently abandon their bug report. >> >> >> But you don’t need to be “part of it” in any meaningful way. One only >> needs to create an account, which could be quite anonymous, and even >> temporary. >> >> And is no harder, and probably easier, than creating an account on a >> Python-specific site. >> >> Also: cPython is a large, complex, and mature project. I don't think many >> non-developers can even identify a true bug, much less write a helpful big >> report. There are many other ways to be involved in and contribute to the >> Python community that don't require a gitHub (or any) account. >> >> I understand the issue here — I feel that way about businesses that use >> Facebook for their website. But in that case, I can’t even read it without >> a Facebook account. I don’t mind needing an account to contribute to a >> conversation. >> >> And while GitHub has become the dominant player in Open Source >> development— it has not (yet?) reached out to control much else. >> >> -CHB >> >> >> With all due respect to Microsoft, who has contributed significantly to >> Python development, and continues to do, some people don't care for some of >> Microsoft's policy and actions, and Microsoft owns GitHub, so your last >> paragraph is somewhat naive, at best. >> >> So what is the difference between a GitHub account, and Microsoft account? >> > > They are entirely different and separate; there's no relation there at all. > > > Good, but given the Skype experience, it is questionable how long they > will stay that way. > You can choose to view that as a one-off or indicative of a pattern. I'm choosing the former (you can use the LinkedIn acquisition as support for my view). > One thing I will remind people is I personally have led the work to move > this project from: > > 1. SourceForge to our own infrastructure > 2. Mercurial to git > 3. Our own infrastructure to GitHub for code management > > So if GitHub were to do something we don't like we can always move > platforms again. > > > Indeed, but platform churn slows contributions, too. > Sure, but I don't think anyone is about to argue we should have stayed on SF. Nor are there plans to switch off of GitHub. Regardless, there are no plans to halt what was decided when we accepted PEP 581. Most of the concerns which have been brought up in this thread were already expressed back then (the account merge one I didn't remember, hence why I replied). >
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/IL6TJJXAIZODIQ5CNSIVV2LN4R43ZJKP/ Code of Conduct: http://python.org/psf/codeofconduct/
