Hey,
what do you think about moving pylint and astroid from Bitbucket/hg to GitHub/git? I've briefly talked with Claudiu about this, and he seems open to the idea and suggested I write this mail :)
If people agree, I'll be able to move issues (including the correct issue numbers) and the repository (including tags/branches). I recently helped doing the same for pytest:
https://bitbucket.org/pytest-dev/pytest/issues/699/
Unfortunately, I didn't find a good way to migrate pull requests, so those would've been to be recreated by their authors.
Some rationales, from my point of view:
- GitHub has the bigger exposure, and more people are familiar with it than with Bitbucket - this potentially means more contributors.
- Contributing is IMHO cumbersome with Bitbucket. Apparently, one's supposed to use bookmarks instead of branches (because branches can't be deleted, IIRC), but Bitbucket doesn't support doing pull requests with them - the "solution" Bitbucket uses when editing things with the online editor is to create a new fork for every change, by the way...
I also tried to find documentation for basic stuff like "how do I contribute to a project with branches and PRs", and found it very difficult. Sure, I'm used to git, but getting started with git was a lot easier than with hg/bitbucket.
- Travis CI[1] is a lot better than drone.io, the current CI system in use. For example, one is able to test PRs, which is something essential in a CI IMHO (and also makes contributing easier).
I don't think I need to elaborate on that :)
- There's also a lot of other potentially useful tooling which is available for GitHub, but not BitBucket - see point 1 (bigger exposure).
My plan would be to create a pylint organization on GitHub and move the repos and issues there.
Opinions?
Florian
On Oct 16, 2015 10:56 AM, "Florian Bruhin" me@the-compiler.org wrote:
Hey,
what do you think about moving pylint and astroid from Bitbucket/hg to GitHub/git? I've briefly talked with Claudiu about this, and he seems open to the idea and suggested I write this mail :)
If people agree, I'll be able to move issues (including the correct issue numbers) and the repository (including tags/branches). I recently helped doing the same for pytest:
https://bitbucket.org/pytest-dev/pytest/issues/699/
Unfortunately, I didn't find a good way to migrate pull requests, so those would've been to be recreated by their authors.
Some rationales, from my point of view:
GitHub has the bigger exposure, and more people are familiar with it than with Bitbucket - this potentially means more contributors.
Contributing is IMHO cumbersome with Bitbucket. Apparently, one's supposed to use bookmarks instead of branches (because branches can't be deleted, IIRC), but Bitbucket doesn't support doing pull requests with them - the "solution" Bitbucket uses when editing things with the online editor is to create a new fork for every change, by the way...
I also tried to find documentation for basic stuff like "how do I contribute to a project with branches and PRs", and found it very difficult. Sure, I'm used to git, but getting started with git was a lot easier than with hg/bitbucket.
Travis CI[1] is a lot better than drone.io, the current CI system in use. For example, one is able to test PRs, which is something essential in a CI IMHO (and also makes contributing easier).
I don't think I need to elaborate on that :)
There's also a lot of other potentially useful tooling which is available for GitHub, but not BitBucket - see point 1 (bigger exposure).
My plan would be to create a pylint organization on GitHub and move the repos and issues there.
Opinions?
Florian
I'm replying from my phone so forgive me for being brief.
A month or longer ago there was discussion by Claudiu about moving pulling to the PyCQA (Python Code Quality Authority). I'm still willing to make you both administrators if you're interested in still doing this.
Regarding the move to GitHub I have no strong opinions. Flake8 moved to GitLab and mirror on GitHub and accept PRs there. Personally I have grown to prefer GitLab but that's me. We've definitely benefited from the move to git but I don't think we would have increased participation any more than we have by moving all parts of the project to GitHub.
Cheers, Ian
Seems reasonable to me as well for the reasons outlined. I think rather than a new organization in GitHub I would pick the PyCQA org that already exists (and did for pep8's recent move). But just my two cents.
~ Ian Lee On Oct 16, 2015 10:42 AM, "Ian Cordasco" graffatcolmingov@gmail.com wrote:
On Oct 16, 2015 10:56 AM, "Florian Bruhin" me@the-compiler.org wrote:
Hey,
what do you think about moving pylint and astroid from Bitbucket/hg to GitHub/git? I've briefly talked with Claudiu about this, and he seems open to the idea and suggested I write this mail :)
If people agree, I'll be able to move issues (including the correct issue numbers) and the repository (including tags/branches). I recently helped doing the same for pytest:
https://bitbucket.org/pytest-dev/pytest/issues/699/
Unfortunately, I didn't find a good way to migrate pull requests, so those would've been to be recreated by their authors.
Some rationales, from my point of view:
GitHub has the bigger exposure, and more people are familiar with it than with Bitbucket - this potentially means more contributors.
Contributing is IMHO cumbersome with Bitbucket. Apparently, one's supposed to use bookmarks instead of branches (because branches can't be deleted, IIRC), but Bitbucket doesn't support doing pull requests with them - the "solution" Bitbucket uses when editing things with the online editor is to create a new fork for every change, by the way...
I also tried to find documentation for basic stuff like "how do I contribute to a project with branches and PRs", and found it very difficult. Sure, I'm used to git, but getting started with git was a lot easier than with hg/bitbucket.
Travis CI[1] is a lot better than drone.io, the current CI system in use. For example, one is able to test PRs, which is something essential in a CI IMHO (and also makes contributing easier).
I don't think I need to elaborate on that :)
There's also a lot of other potentially useful tooling which is available for GitHub, but not BitBucket - see point 1 (bigger exposure).
My plan would be to create a pylint organization on GitHub and move the repos and issues there.
Opinions?
Florian
I'm replying from my phone so forgive me for being brief.
A month or longer ago there was discussion by Claudiu about moving pulling to the PyCQA (Python Code Quality Authority). I'm still willing to make you both administrators if you're interested in still doing this.
Regarding the move to GitHub I have no strong opinions. Flake8 moved to GitLab and mirror on GitHub and accept PRs there. Personally I have grown to prefer GitLab but that's me. We've definitely benefited from the move to git but I don't think we would have increased participation any more than we have by moving all parts of the project to GitHub.
Cheers, Ian
code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
Hey,
Claudiu and I plan to look at the migration of pylint/astroid to GitHub tomorrow evening (GMT+2, i.e. in something like 24h).
A month or longer ago there was discussion by Claudiu about moving pulling to the PyCQA (Python Code Quality Authority). I'm still willing to make you both administrators if you're interested in still doing this.
I'd be glad if you could do that - I'll probably play with a move to a repo under my user first to see if everything goes well, but if it does, it'd be nice to complete the real move too.
I'm @The-Compiler on GitHub, Claudiu is @PCManticore.
Florian
On Mon, Dec 7, 2015 at 11:06 AM, Florian Bruhin me@the-compiler.org wrote:
Hey,
Claudiu and I plan to look at the migration of pylint/astroid to GitHub tomorrow evening (GMT+2, i.e. in something like 24h).
A month or longer ago there was discussion by Claudiu about moving
pulling
to the PyCQA (Python Code Quality Authority). I'm still willing to make
you
both administrators if you're interested in still doing this.
I'd be glad if you could do that - I'll probably play with a move to a repo under my user first to see if everything goes well, but if it does, it'd be nice to complete the real move too.
I'm @The-Compiler on GitHub, Claudiu is @PCManticore.
Florian
That's awesome!
I've added you as an Owner temporarily so you can transfer the repository easily. I've also invited Claudiu. We can work out permanent (co-)ownership of the Org too if you'd like to.
I've also created two teams, so you can expand the dev team of PyLint without giving those developers administrator access over the repository.
Let me know if you need any other help. If the transition happens roughly 24 hours from now, that's midday for me and I'll be around on the list and on IRC in ##python-code-quality on Freenode too.
Cheers, Ian
Hi,
at Logilab, we've been involved for years with mercurial development and we fight daily against the centralized model offered by github, among others. The latter explains why we've self-hosted pylint for such a long time even if the UI didn't reach the level of other well-known platforms. Unfortunaly, I still fail to see a lot of counter arguments against the rationales exposed by Florian and we already have to admit that the switch to bitbucket has been a success, as it has allowed a new generation of developpers to take over pylint's development and making it even more successful. So if you, people who make the project alive today, feel like it has to be done, go with it. Even if it makes me, and maybe a few others, sad.
Still, if there is some options to use e.g. gitlab with a mirroring to github or alike which keeps the expected benefit but without the centralized model, I would like to have them considered. This maybe of interest for others PyCQA projects.
Anyway, whatever the move, if we go out of bitbucket I would rather benefit from the opportuntiy to put pylint under the PyCQA umbrella as proposed by Ian.
Cheers,
On Wed, Oct 21, 2015 at 6:52 AM, Sylvain Thénault sylvain.thenault@logilab.fr wrote:
Hi,
at Logilab, we've been involved for years with mercurial development and we fight daily against the centralized model offered by github, among others. The latter explains why we've self-hosted pylint for such a long time even if the UI didn't reach the level of other well-known platforms. Unfortunaly, I still fail to see a lot of counter arguments against the rationales exposed by Florian and we already have to admit that the switch to bitbucket has been a success, as it has allowed a new generation of developpers to take over pylint's development and making it even more successful. So if you, people who make the project alive today, feel like it has to be done, go with it. Even if it makes me, and maybe a few others, sad.
Still, if there is some options to use e.g. gitlab with a mirroring to github or alike which keeps the expected benefit but without the centralized model, I would like to have them considered. This maybe of interest for others PyCQA projects.
Using GitLab and mirroring to GitHub is a definite option. PyCQA already has an organization there and mirrors a few repos to GitHub. That said, I maintain a Jenkins infrastructure for those projects so I can run CI on the merge requests received through GitLab. GitLab only recently launched their own CI service and I haven't had time to investigate it at all.
Travis CI is most certainly a lot less to manage if they move to GitHub. (Note that Flake8 has Travis enabled in the event someone sends a PR through GitHub.)
Like I said, I won't try to sway either way, but I would vastly prefer if Travis supported GitLab as well, but they don't and probably never will.
Cheers, Ian
* Florian Bruhin me@the-compiler.org [2015-10-16 17:51:34 +0200]:
what do you think about moving pylint and astroid from Bitbucket/hg to GitHub/git? I've briefly talked with Claudiu about this, and he seems open to the idea and suggested I write this mail :)
Thanks for all your answers!
Claudiu and I agree it'll be a good idea to move it to the PyCQA organization on on GitHub.
I'll wait until after the next pylint/astroid release as hopefully the PRs will have cooled down a bit until then. :)
Florian
On Fri, Oct 23, 2015 at 6:10 AM, Florian Bruhin me@the-compiler.org wrote:
- Florian Bruhin me@the-compiler.org [2015-10-16 17:51:34 +0200]:
what do you think about moving pylint and astroid from Bitbucket/hg to GitHub/git? I've briefly talked with Claudiu about this, and he seems open to the idea and suggested I write this mail :)
Thanks for all your answers!
Claudiu and I agree it'll be a good idea to move it to the PyCQA organization on on GitHub.
I'll wait until after the next pylint/astroid release as hopefully the PRs will have cooled down a bit until then. :)
Florian
That's awesome to hear! Feel free to email me off list to coordinate making you both admins and getting the project set up.
Cheers, Ian
participants (4)
-
Florian Bruhin -
Ian Cordasco -
Ian Lee -
Sylvain Thénault