[code-quality] Moving pylint/astroid to GitHub

Ian Cordasco graffatcolmingov at gmail.com
Fri Oct 16 19:41:59 CEST 2015

On Oct 16, 2015 10:56 AM, "Florian Bruhin" <me at 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).
> [1] https://travis-ci.org/
> 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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/code-quality/attachments/20151016/9de822f2/attachment.html>

More information about the code-quality mailing list