Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #101245

Re: GitHub's “pull request” is proprietary lock-in

Show key headers only | View raw

On 01/04/2016 03:21 AM, m wrote:
> W dniu 03.01.2016 o 05:43, Ben Finney pisze:
>> That and other vendor-locked workflow aspects of GitHub makes it a poor
>> choice for communities that want to retain the option of control over
>> their processes and data.
> 
> I'm also afraid that Github will make to git the same thing as Google
> did to Jabber/XMPP.
> 
> Decade ago, I had plenty of friends on my jabber contacts list. Next,
> Google made it's talk compatible with jabber, then my friends slowly
> migrated to gtalk, because if they used gmail anyway, then why not use
> it also for jabber?
> 
> And then Google turned off XMPP support and suddenly I lost ability to
> contact with 80% of my friends without having stupid hangouts running,
> or without falling back to email (which is not so bad BTW).

I use gtalk with Pidgin every day using XMPP.  So Google still supports
XMPP.  However what they stopped doing was allowing federated XMPP,
which pretty much breaks XMPP, at least the spirit of it.  So the only
way to chat with gtalk users is to use your gtalk account.  But you
certainly don't need hangouts.  XMPP works fine between your client and
the Google server.

I agree that Google really pulled a bad one with gtalk though.  Dropping
federated XMPP support was definitely not in keeping with their original
"do no evil" mantra.

> The same can be with Github and git. PPL will forget how to use git
> without github. When Github will make git-incompatible changes, vast
> majority will need/want to follow the changes and eg. will use Gitlabs
> propertiary binary.

Yup you are correct.  However for the foreseeable future, you can still
do a git clone from github, and you can still use your local repository
normally.  In fact I think this is really part of the github workflow.
But who knows what the future will bring.  I can sure see the wisdom of
the GPLv3 as we move into a world of software as a service, where even
Microsoft uses Linux, and charges us for it.

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: We will be moving to GitHub Zachary Ware <zachary.ware+pylist@gmail.com> - 2016-01-01 13:58 -0600
  Re: We will be moving to GitHub Paul Rubin <no.email@nospam.invalid> - 2016-01-01 12:33 -0800
    Re: We will be moving to GitHub Zachary Ware <zachary.ware+pylist@gmail.com> - 2016-01-01 14:46 -0600
      Re: We will be moving to GitHub Paul Rubin <no.email@nospam.invalid> - 2016-01-01 13:19 -0800
    Re: We will be moving to GitHub Ben Finney <ben+python@benfinney.id.au> - 2016-01-02 18:02 +1100
    Re: We will be moving to GitHub Michael Torrie <torriem@gmail.com> - 2016-01-02 20:31 -0700
    GitHub's “pull request” is proprietary lock-in (was: We will be moving to GitHub) Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 15:43 +1100
      Re: GitHub's ³pull request² is proprietary lock-in (was: We will be moving to GitHub) Michael Vilain <vilain@NOspamcop.net> - 2016-01-02 20:56 -0800
        Re: GitHub's ³pull request² is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 02:04 -0500
          Re: GitHub's ³pull request² is proprietary lock-in Christian Gollwitzer <auriocus@gmx.de> - 2016-01-03 08:44 +0100
            Re: GitHub's ³pull request² is proprietary lock-in Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 19:03 +1100
              Re: GitHub's ³pull request² is proprietary lock-in Christian Gollwitzer <auriocus@gmx.de> - 2016-01-03 09:33 +0100
                Re: GitHub's ³pull request² is proprietary lock-in Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 19:45 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 20:18 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 04:31 -0500
                Re: GitHub's ³pull request² is proprietary lock-in Paul Rubin <no.email@nospam.invalid> - 2016-01-03 01:50 -0800
                Re: [python] Re: GitHub's ³pull request² is proprietary lock-in "W. Trevor King" <wking@tremily.us> - 2016-01-03 01:42 -0800
                Re: GitHub's ³pull request² is proprietary lock-in Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 20:46 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 21:17 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 21:24 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Paul Rubin <no.email@nospam.invalid> - 2016-01-03 02:42 -0800
                Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 23:33 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Paul Rubin <no.email@nospam.invalid> - 2016-01-03 21:29 -0800
                Re: GitHub's ³pull request² is proprietary lock-in Christian Gollwitzer <auriocus@gmx.de> - 2016-01-04 08:02 +0100
          Re: GitHub's ©¯pull request©— is proprietary lock-in Michael Vilain <vilain@NOspamcop.net> - 2016-01-03 12:51 -0800
        Re: GitHub's �pull request� is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-03 08:05 -0700
        Re: GitHub's �pull request� is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-03 08:14 -0700
      Re: GitHub's “pull request” is proprietary lock-in Kevin Walzer <kw@codebykevin.com> - 2016-01-03 16:58 -0500
      Re: GitHub's “pull request” is proprietary lock-in m <mvoicem@gmail.com> - 2016-01-04 11:21 +0100
        Re: GitHub's “pull request” is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-04 10:41 -0700
          Re: GitHub's "pull request" is proprietary lock-in Josef Pktd <josef.pktd@gmail.com> - 2016-01-04 13:29 -0800
          Re: GitHub's “pull request” is proprietary lock-in m <mvoicem@gmail.com> - 2016-01-05 01:24 +0100
    Re: GitHub's “pull request” is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 19:51 -0500
    Re: GitHub's “pull request” is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-03 21:16 -0700
    Re: GitHub's “pull request” is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 23:58 -0500

csiph-web