Steve McIntyre <st...@einval.com> writes: > Ben Finney wrote: >> Paul Tagliamonte <paul...@debian.org> writes:
>>> So, yes, it's nonfree. Yes, it's controlled by DDs. No, I don't think >>> this should be the Vcs-Git: target. No, I don't think we should >>> endorse GitHub. Yes, we need free tools. Yes, we should contribute to >>> the F/OSS community where upstreams are. >> That last part seems to deny the D in DVCS. Why are we under such >> pressure to use one particular centralised service? > Agreed - it's really annoying to see everybody clamour for a > centralised single point of of failure for git hosting. :-( Funny, this is why I don't get why people are so upset that some use GitHub. Because of how Git works, the impact of lock-in is pretty much limited to the non-repository stuff (issues and so forth). I use GitHub for some things, largely because it makes it easy for people to contribute patches if they're used to that workflow, and it lets me take advantage of some services (like continuous integration builds) that I could but don't feel like building myself. I also push all my repositories to my own Git server with its own gitweb instance, so if GitHub disappears tomorrow, I don't lose anything of much note. Yes, it's a proprietary service and all, but not all proprietary cloud services are created equal in terms of their lock-in and other drawbacks. GitHub is pretty light-weight on that front. That said, something more akin to GitHub (including the nice integration API and fork/pull model) running on a service like Alioth would be very neat. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87iocu1fp5....@hope.eyrie.org
