PostmarketOS is moving to Gitlab
postmarketos.org
postmarketos.org
I, too, would write off anything created/owned/loosely related to Microsoft as being trash/corporate bullshit/inferior to literally anything else. When they released VSCode, I chuckled because why would anyone want to use a stripped down visual studio running in electron, don't they know it's going suck? However, after some time I would constantly be seeing praise from people about how good VSCode is (lol I can't believe M$oft is paying people to say good things about their editor online, right?!). Then, for whatever reason, one day I decide to download it, just to prove that I'm right and it's just yet another sub par Microsoft product being praised by fanboys.
And wouldn't you know it, I was completely wrong. VSCode is actually really, really good. If you would told me a year or so ago that'd I'd be using a Microsoft product daily (by choice), actually preferring it over other options, AND is open source. I'd have probably laughed at you because I'd never touch any of their bloated corporate spyware.
They're definitely far from perfect, I still won't touch Windows unless I absolutely have to, Skype for Business sucks (Mac), and from what I've gathered Microsoft Teams is a shitshow. But they're absolutely moving in the right direction (in some areas at least), and I'm not going to jump on every microsoft product now, but I won't immediately write them off either. Hell, I'm even interested in checking out .net core at some point.
The increased efforts/contributions towards open source should alone tell you that this isn't the same Microsoft. Which is why the GitHub acquisition didn't even phase me, nor am I deleting all my repositories, moving to GitLab, and then writing a blog post about how big bad microsoft is going to literally ruin open source.
Now... if this was still 80s Gates or Balmer's microsoft, I probably would be worried about GitHub's future. But, from everything I've read, Nadella seems likes he's a really cool dude.
So you know, there's that.
It's not as if all the children could be temporarily given to host families and kept safe----they're not actually part of the foster system, or intending full time stay in the US.
Github rate limit: "5000 requests per hour"
{
"resources": {
"core": {
"limit": 60,
"remaining": 58,
"reset": 1530102452
},
"search": {
"limit": 10,
"remaining": 10,
"reset": 1530099950
},
"graphql": {
"limit": 0,
"remaining": 0,
"reset": 1530103490
}
},
"rate": {
"limit": 60,
"remaining": 58,
"reset": 1530102452
}
}> For API requests using Basic Authentication or OAuth, you can make up to 5000 requests per hour.
> For unauthenticated requests, the rate limit allows for up to 60 requests per hour.
5000 requests per hour, so they could have all their issues imported in less than an hour.
Why call this anything but just straight up FUD related to MS hate? I've been amused by the negative reaction to the acquisition, as if GitHub was somehow a charity before MS bought them, and overnight became the reincarnated as Darth Vader.
Let's take a look at what's missing:
> But independent of that, GitHub has always had a vendor lock-in with the user's issues and pull requests hidden behind a rate limited API instead of a proper export feature. And even if you managed to export it through that API, you can not host your own GitHub instance and modify it as you like because there is not even a partially open source version of it.
With gitlab, we have one API call to request the entire export, and another one to download it. Whereas with GitHub we need a script that queries the API for all kinds of information we would like to extract. Whenever GitHub changes their API, it needs to be adjusted. And there aren't many projects out there that do this. Besides running a full gitlab instance, the best way seems to be the "github-backup" project [1], and it can not keep up with GitHub's changes:
> Notes added to commits and lines of code don't get backed up yet. There is only recently API support for this.
But the part that really matters is that you can not run your own GitHub instance after you exported all the data with the API and your preferred script.
With the tools available today, the next best thing for us to switching from GitHub to gitlab and using gitlab's export functionality would be running a local gitlab instance that does the GitHub import once a week, and using that as fallback. But if you are willing to do that, then you might as well switch to gitlab completely, just like we did it.
It's not that I think Microsoft will do a bad job (and the issue isn't about Microsoft specifically) it just made me realize something that I logically knew but never thought about: Github can be bought, and it's a near-monopoly.
We take advantage of a seemingly altruistic service like Github, but I now process that they're a for-profit corporation, and there is no reason they couldn't exploit that fact. While I don't think they would do this, Microsoft could easily deprioritize projects that compete with their products, or surround popular releases with adware (like Sourceforge did a few years ago).
Gitlab is a for-profit corporation as well, so they're not immune to this, but the difference is that I can easily run my own Gitlab server if I really wanted to, or fork the project and make "Tombert's Cool Gitlab Competitor" whenever I need to. Inherently, Gitlab has created its own competition, which I think can shield a bit from my concerns.
Also, I've grown to really like the Gitlab interface; maybe that's a good enough reason to switch.
I need a break from work and research, so I'm planning on finally trying out drebrez's LVM branch on my old Nexus 7 this weekend. I might also look into what it would take to get a HTC One (m7) booting.
If you think that GitLab (the company) is any better for your data than GitHub (Microsoft) you are incapable of understanding economy and capitalism.
LOL that's quite the generalization. How about the argument that with GitLab you don't have vendor lock in since you can export and run your own instance at any moment? Seems like a compelling reason for GitLab to be a better place for your data.
Wouldn't every single user have to create a new account in the Gitlab instance running on the new server?
Granted, Github has Enterprise, but that's proprietary, and I like that there's no need to worry about license fees and whatnot with Gitlab.
I'm not expecting GitHub to change much, if at all, but part of an open internet is people and companies being able to choose how they want to do things.
"[..] But independent of that, GitHub has always had a vendor lock-in with the user's issues and pull requests hidden behind a rate limited API instead of a proper export feature. And even if you managed to export it through that API, you can not host your own GitHub instance and modify it as you like because there is not even a partially open source version of it."
With the above context, I'd say M$ may be different now compared to before but it's changing only because it has to and only because they reap what they sow. Previous seeds grew.
Speaking about V$Code, there was so much hatred in GitHub when peeps asked maintainers to allow users to customise the blue status bar that I think I saw true "spirit" of that company. See for yourselves: https://github.com/Microsoft/vscode/issues/1884 - some juicy posts have been deleted/edited since though
PS. I moved all my 80 Open Source libraries to BitBucket and haven't looked back since. I applaud all others that migrate out of GitHub.
obviously can't tell about the edited ones, but there's not a single "juicy" comment by someone from Microsoft there IMHO? I mostly see external commenters misbehaving.