www.libssh2.org | Daily snapshots | Mailing list archive | Docs | Examples | github

Archive Index This month's Index

Subject: Re: Download libssh2 source via HTTPS?

Re: Download libssh2 source via HTTPS?

From: Alexander Lamaison <swish_at_lammy.co.uk>
Date: Wed, 11 Mar 2015 17:52:23 +0000

On 10 Mar 2015 14:49, "Tor Arntsen" <kspt.tor_at_gmail.com> wrote:
>
> 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.

Maybe that's how the curl mailing list works but it's not so good for
libssh2. Contributed patches either get an immediate response (great) or
they are forgotten. Noone (except Daniel sometimes when he must have had a
lot of coffee) takes the trouble to look back through the mailing list and
find forgotten patches. Trac is a little better because you can't 'lose'
tickets.

Github improves things a bit by separating bug reports from pull requests.
It's easy to ignore bug reports because they are problems requiring
investigation and time. But pull requests are harder to forget because they
represent a *solution* waiting for approval. Github puts these in your face
every time you visit the project page.

Nothing is a silver bullet, but anything increasing our chances of a good
thing.

Alex

_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2015-03-11

the libssh2 team