> Am 04.03.2015 um 11:21 schrieb Daniel Stenberg <dan...@haxx.se>: > Personally, I wouldn't mind switching over to hosting the source code repo at > github (which then could provide the code over HTTPS "for free") and then on > a longer term switch to that bug tracker and allow pull requests there etc. > All in the name of going where there's already a large amount of users, it > brings features and it encourages and simplifies collaboration even further. > Do it "like the kids do". And it makes the infrastructure less dependent on > individual volunteers.
Yes, Github would be awesome. Is there an argument against moving to Github? >> If missing HTTPS support is related to cost, I can offer to pay for an SSL >> certificate. > > It is related to cost, but not strictly the price for the certificate but > even more so the effort and maintenence cost in time and energy. Hence I > would prefer to use an existing (and proven) infrastructure for it. > > My slightly longer term plan is to jump on the letsencrypt.com bandwagon once > that goes live and offer HTTPS for libssh2.org (and all other sites I host) > from then on. If you move to Github, you could host the project website on github too. We do that for http://postgresapp.com <http://postgresapp.com/> — everything is hosted on Github, for free (even binaries). Only drawback: Github pages don't support https. Thus, if you want a secure download, you have to go to the Github website and download from there.
_______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
