We will be moving to GitHub

[Bernardo Sulzbach]

On Sat, Jan 2, 2016 at 5:12 AM, Chris Angelico <rosuav at gmail.com> wrote:
> On Sat, Jan 2, 2016 at 5:43 PM, Steven D'Aprano <steve at pearwood.info> wrote:
>> There are times where everybody should do the same thing -- choosing whether
>> to drive on the left or the right side of the road, for example. And there
>> are times where following the crowd like lemmings is actively harmful, no
>> matter how convenient it seems in the short-run.
>
> The popularity of technology IS an argument in its favour, though. How
> many people here use Gopher instead of HTTP? Would it be better to
> serve Python content on the obscure protocol rather than the popular
> one? When 99% of people know how to use one technology and 1% know how
> to use a different one, it's advantageous to go where the people are.
> (Of course, there are other considerations, too - PHP is popular, but
> that alone isn't a reason to use it. The context here is of
> technologies so similar in functionality that we really CAN make a
> decision on these kinds of bases.)
>
> The Python project *needs* new contributors. This is not in question.
> You can't expect to keep the project going solely on the basis of the
> people currently writing and applying patches. So there are two
> options:
>

I must agree with Chris, visibility in OSS is key of it. If you write
a library and license it under BSD 3-Clause but keep it in your local
network forever it is not as open as if you would throw it in GitHub.
There are many people there, and there are many people willing to at
least review the code of interesting projects.