https://developers.slashdot.org/story/18/06/04/1314247/microsoft-acquires-github-for-75b !!!
Hi Visvanath,
it's actually an agreement: the acquisition will happen at the end of this year.
More details in https://blogs.microsoft.com/blog/2018/06/04/microsoft-github-empowering-developers/ and https://blog.github.com/2018-06-04-github-microsoft/ .
HTH,
Matteo
That said you can see why M$ have done this, for people not happy having their code on an M$ owned service, they have just created a huge amount of disruption while those people migrate, causing project delays and other difficulties. For people who swallow the change, M$ get to control how you work, quite what that means in the long term remains to be seen. Either way M$ win. Also, for those working on projects that choose not to migrate, or if you want to fork a project that hasn't moved, you are still stuck with GitHub, so even if I move my own projects (likely), I can't delete my account entirely. Which really bugs me.
https://developers.slashdot.org/story/18/06/04/0935200/microsofts-interest-in-buying-github-draws-backlash-from-developers
How do the owners of Moodle feel about Microsoft taking care of their code?
They don't.
Moodle has always maintained and hosted their own source code repo (first cvs now git.moodle.org)
Github does provide a "mirror" of git.moodle.org to make it easy for organisations that use github (and to helpfully offload some internet traffic from Moodle's core git server.)
Although - there are a few plugins that MoodleHQ host on github:
https://github.com/moodlehq
I guess we'll just have to wait and see how many organisations decide to move away from github and onto other systems - I can't imagine Microsoft will make the same mistakes that sourceforge did though.
I second/support/endorse Dan's post .
Today people is moving away from GitHub, migrating to GitLab: unless you're going for your own with something like gogs/gitea - simplifying, to have both web access to git and team work organization, kind-of Trac - we're creating pressure on the GitLab infrastructure - several overload issues in these days since early Monday - but still trusting a "central hub" which differs from GitHub, at the moment, only by offering the same product as OSS but their servers are paid w/ money not w/ volunteering - not to mention that GH is selling its own software to the Companies.
IMHO the point today is: can you tolerate kind-of AI spidering all the repos, both public AND private?
M$ is used to sign NDAs so you could stay safe about the privacy but, in case it will happen, it will give M$ the opportunity to better shape the needs in the development area for different languages even lurking at your hosted closed-sources.
I'm used to work with M$ products since ages in my professional life and I know most of the issues that VSTS has still today - while since '94 I'm playing with Linux for my "personal life" - : at the moment, for my spare time SW hobbies, which are all public - i.e. they could be "stolen" either way, even in other Git Hosted Services - , I'm fine with GH being bought by M$, waiting to see its actual strategies w/o speculating too much.
HTH,
Matteo
Thanks, that is a relief. The point is, Moodle core on Github is not the original, it is just a backup. Being GPL there is no problem people copying code (in fact it is encouraged).
May be I am still allergic (or have developed a PTSD) from the days that the soft spoken CEO of Microsoft went ranting "Linux is cancer!" (meaning the GPL). I don't understand why they now spread the same cancer. What happened to their own Open Source Hub https://opensourcehub.microsoft.com/ ? On the surface it looks like they are embracing FOSS, for example https://open.microsoft.com/. But the oldies haven't forgotten their EEE warfare https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish.
Hi Visvanath,
indeed it's a mirror - which, in the inner nature of git, means a full backup - : all the issues are stored in the Tracker regardless the "hub" where the git repo is mirrored (better than hosted).
EEE IMHO no more works for them as in the no more recent past: it looks like Cloud and Serverless are the new key points, with "more than a bit" of AI, not really clear to me exactly where it will appear and be applied.
HTH,
Matteo
Moodle has always maintained and hosted their own source code repo
It's not actually Git repositories that makes GitHub valuable (Git is a distributed system). I think it's more about all the attached services and interactions such as review comments, issue tracking, pull requests etc happening there. So I would add that even more importantly, Moodle HQ also runs all other essential systems - the bugs tracker, documentation wiki or the translations portal - in house too.
Does this mean that Moodle core will now ship with ClippyJS (www.smore.com/clippy-js) ? And the tracker will have its assistance too:
It is indeed wise from Moodle HQ to run their own infrastructure. But it is a bigger operation that the most of OS projects on Github and can have that luxury. Running own Git server is not a big deal, but as you noted the attached services and interactions are the key. Github is the Facebook of Open Source developers! And ironically, the github.com source itself is not Open Source!
@Gareth
Are you still running away from that (proverbial) Clippy? After leaving Microsoft two decades ago, I had to leave Skype then LinkedIn and now Github. Thank God, Internet is vast, there are plenty of possibilities. And it helps to come to a bigger revelation, after giving up these things, one doesn't miss them really.
https://linux.slashdot.org/story/18/06/09/052249/linux-foundation-celebrates-microsofts-github-acquisition
Hi Visvanath,
the AMA post should give us a picture of M$'s GH in the next years: if they'll not keep those promises trusted by any of us, IF they'll keep the current set of API features, there will be always the chance to migrate elsewhere - I mostly mean issues (PRs included) and wikis.
Shortly, Ill keep an eye on their APIs.
HTH,
Matteo
Just for the record: from https://moodle.org/mod/forum/discuss.php?d=375017 bounced then to https://blog.moodle.net/2018/keeping-track-of-moodlenet/, I've read that contributing code to MoodleNet is done via GitLab.
HTH,
Matteo