#10 Wow, the impact of the majority of the world not having GDPR means that only the EU could potentially be protected from such abuses (by requiring that data be deleted). This is a most unfortunate situation for anyone paying to keep secrets in a private repository...
Either way, Gitlab mitigation is easy
Yeah, I can't imagine GitHub making much money from subscriptions after this acquisition.
@Toadofsky
Do you know what happened to Skype after Microsoft purchased it?
It slowly become more and more buggy until these days it's almost unusable. Apparently Skype was strong competition to Microsoft's services, and they thought "We'll just buy it and destroy it." And so they did.
My guess is they want to do the same to Github, and if it's true then a lot of programmers will have to start using something else quite soon...
Do you know what happened to Skype after Microsoft purchased it?
It slowly become more and more buggy until these days it's almost unusable. Apparently Skype was strong competition to Microsoft's services, and they thought "We'll just buy it and destroy it." And so they did.
My guess is they want to do the same to Github, and if it's true then a lot of programmers will have to start using something else quite soon...
#14 I haven't said anything positive about this acquisition and personally I'm quite disappointed about it.
At the same time I don't think MSFT intends to ruin things, it just happens... for example, it's been 10 years:
www.polygon.com/2015/1/12/7532341/microsoft-says-there-are-plans-for-rare-classics-like-banjo-kazooie
At the same time I don't think MSFT intends to ruin things, it just happens... for example, it's been 10 years:
www.polygon.com/2015/1/12/7532341/microsoft-says-there-are-plans-for-rare-classics-like-banjo-kazooie
Perhaps they want strategic control with quality developer tools, rebrand the stuff and bring it closer to the MS cloud and away from the competition. Perhaps they'll teach an AI to write code based on the repos, but don't think they will destroy the service.
#11 -- What does GDPR have to do with Microsoft's acquisition of GitHub?
#14: Skype was already "buggy" (a lot of very bad bugs) even before Microsoft acquired it. It's only gotten worse. And, the "enterprise" integration aspects, such as Linc or Lync or whatever the hell it is have admins so scared of implementing it ... that "enterprise" product is dead.
But, true, if GitHub follows the "mediocre" Microsoft path of butchering acquisitions -- you're right -- it could become another Skype. (And, don't put it past them. Nice to say one thing; but then always do another; and then make excuses, etc.)
#14: Skype was already "buggy" (a lot of very bad bugs) even before Microsoft acquired it. It's only gotten worse. And, the "enterprise" integration aspects, such as Linc or Lync or whatever the hell it is have admins so scared of implementing it ... that "enterprise" product is dead.
But, true, if GitHub follows the "mediocre" Microsoft path of butchering acquisitions -- you're right -- it could become another Skype. (And, don't put it past them. Nice to say one thing; but then always do another; and then make excuses, etc.)
GDPR requires that personal information be deleted upon request. I don't know to what extent source code is considered personal or whether it contains personal information.
@Toadofsky
Your #11 post, citing #10 (which was one of my posts), mentions GDPR. I'm still not sure how that relates to Microsoft's acquisition of GitHub.
Buzzwords and acronyms are nice [to throw around], especially when they're new. Doesn't mean they're being used or applied properly.
When I mentioned "regulation," I was alluding to entities such as the FCC and FTC (market space aware watchdog organizations) -- not things like GDPR. Data protection (GDPR) is quite a bit different than mergers and acquisitions that have significant market impact (i.e. seeking or needing approval due to concerns over monopolies, etc.)
GDPR comes into play in a number of places in the M&A, but, as far as software source code repositories, and "deletion upon request" and GDPR in that vein -- it doesn't necessarily apply.
You should probably read-up on what GDPR entails, and then consider reading-up on the acronym "SCM" (source control management). -- And then please back-read the history here.
Your #11 post, citing #10 (which was one of my posts), mentions GDPR. I'm still not sure how that relates to Microsoft's acquisition of GitHub.
Buzzwords and acronyms are nice [to throw around], especially when they're new. Doesn't mean they're being used or applied properly.
When I mentioned "regulation," I was alluding to entities such as the FCC and FTC (market space aware watchdog organizations) -- not things like GDPR. Data protection (GDPR) is quite a bit different than mergers and acquisitions that have significant market impact (i.e. seeking or needing approval due to concerns over monopolies, etc.)
GDPR comes into play in a number of places in the M&A, but, as far as software source code repositories, and "deletion upon request" and GDPR in that vein -- it doesn't necessarily apply.
You should probably read-up on what GDPR entails, and then consider reading-up on the acronym "SCM" (source control management). -- And then please back-read the history here.
Just in case, I opened an account on GitLab. From now on I will create a duplicate of my projects on GitLab. If anything goes wrong with GitHub, then there will be an exact replica ready on GitLab.
The technique is really not diffictult. To your "config" file in the ".git" folder you have to add a new remote "gitlab" and a new "credential" for the GitLab repo's url in the "user" section ( so that you don't have to type in your GitLab user name when asked for authentication ). Then you have to push to the "gitlab" remote as well as the usual "origin". ( The API is exactly the same, and you can use your usual Git CLI. )
This is the first project I have duplicated on GitLab:
gitlab.com/pythonflaskserverapps/helloworld
Now the storm can come, I'm secure.
ps. You can have a private repo for free on GitLab.
The technique is really not diffictult. To your "config" file in the ".git" folder you have to add a new remote "gitlab" and a new "credential" for the GitLab repo's url in the "user" section ( so that you don't have to type in your GitLab user name when asked for authentication ). Then you have to push to the "gitlab" remote as well as the usual "origin". ( The API is exactly the same, and you can use your usual Git CLI. )
This is the first project I have duplicated on GitLab:
gitlab.com/pythonflaskserverapps/helloworld
Now the storm can come, I'm secure.
ps. You can have a private repo for free on GitLab.
This topic has been archived and can no longer be replied to.