On 10 March 2015 at 13:10, Bill Segall <bill_at_segall.net> wrote:
> After the send-email some fraction of the developers engaged enough to be on
> a mailing list might be motivated enough to download and have a look at a
> patch but we've already presented a barrier to entry, cos it's not just
> click to look.
Actually, no. That's not what happens or how it works. Patches to the
mailing list will a) hit the major group of developers, and b) be
immediately visible and easily discussable. It is *more* accessible
than a pull request from github. I can state this with confidence
because that's what we have on the libcurl mailing list - repo on
github, and we have both pull requests (which I see because my github
account is connected to the repo), and normal patches posted to the
mailing list. The latter is by far the most convenient.
It's already been decided to move the libssh2 repo to github, and I'm
not opposed to that at all. But to me the pull request feature (or
just about all the rest of its features) is not what's good with
github - what's good is simply that it's a reliable, fast, git remote
repo. And that's really all. The rest I don't see much need for.
Received on 2015-03-10