Live data from Hacker News

Gnome has moved to GitLab

about.gitlab.com

141–150 of 212 posts

Re: Gnome has moved to GitLab

#141
post #98

Earlier quoted context omitted.

To be clear, despite this announcement being posted to gitlab.com (i.e. the "hosted GitLab", which can and will remove you/your/repo any group at any time), the GNOME project is self-hosting their own gitlab instance. So they are indeed insulated from such hypothetical damage.

And will? Are there examples where Gitlab removed users / projects for controversial reasons?

Hate to bring up gamergate, but a project related to the movement was completely taken offline by a rogue github employee.

There are a number of sources, all of them biased, so I'd prefer not to link any.

Re: Gnome has moved to GitLab

#142
post #62
post #37

Earlier quoted context omitted.

> "You don't use github just for git." Well, some people do. I don't, apparently you don't, probably most people don't. But you could and some people do. I've seen a few projects on github with notes to the effect of "don't bother submitting issues/PRs here, do it through our [mailing list/etc]"

The Linux kernel for example.

The kernel is just mirrored on GH, which is why they want PRs and bug reports sent to their mailing list.

Re: Gnome has moved to GitLab

#143
post #64

Now it's time for them to move to Node. They currently use the JS engine from Firefox 45 (over 2 years old) and are looking to move to 52 (almost 15 months old). Let's not forget that the update before that was from FF25 which was from 2013. It's past time to port your stuff to N-API and actually allow devs to have access to standard dev tools using standard dev practices. It would be a great change for Gnome devs to…

I've tried. Multiple times:

https://github.com/gnome/gnode https://github.com/WebReflection/node-gtk https://github.com/endlessm/eos-knowledge-content-node https://github.com/Place1/node-gir

The C++ V8 / Node API is actually more unstable than the equivalent SpiderMonkey one (there is supposed to be NaN, Node's wrapper abstraction library, but complex language bindings like I did requires a lot more than what's in NaN), and overall I encountered a lot of bugs in the ecosystem. Making libuv work with an external message loop like glib requires some complex plumbing. The thread story is a lot worse: glib wants to call your callback function from another thread, and V8 will crash if you try to do that.

There's a lot of edge cases when you're implementing language bindings, and I kept hitting into non-rounded-off edges, bad documentation, and impassable walls.

Re: Gnome has moved to GitLab

#144
post #130

Earlier quoted context omitted.

I feel like this is unfortunate. Github has a giant user-based, and using github would be a great way to reduce the friction of having first-time contributors submit a pull-request. In my case, if KiCAD were hosted on github, I would have already contributed by now. I think its a shame that more of these projects don't adopt a strategy of "let's try github, and if they screw us over, then we'll migrate to a platform…

Github has dabbled a bit too much in politics in recent years TBH. It doesn't surprise me that projects like GNOME would take pause at that, among the other reasons people are listing.

I can’t agree enough.

Re: Gnome has moved to GitLab

#145

Too bad GitHub was out of the question just because it's not open source. I don't think there is a single platform out there that has done more for the open source community than GitHub. Most of the great OSS projects are on it and it helped democratize open source participation by providing a very nice UI and a set of robust tools that simply didn't exist before.

On the other hand Github could also become the next sourceforge.

Sourceforge went the way it did not only because it was always a hornet's nest of ads and viruses, but they allowed bloatware and viruses to be bundled with project downloads. I don't see GitHub ever behaving in that way, though if they did there'd be a mass exodus for sure.

Re: Gnome has moved to GitLab

#146

Too bad GitHub was out of the question just because it's not open source. I don't think there is a single platform out there that has done more for the open source community than GitHub. Most of the great OSS projects are on it and it helped democratize open source participation by providing a very nice UI and a set of robust tools that simply didn't exist before.

Why should github be the first choice and subject to exhaustion? Are there not compelling reasons to got with gitlab?

Re: Gnome has moved to GitLab

#147

Unrelated, but GitLab has a pretty slick cookie notice. Tells you exactly what they're doing and lets you opt out of non-essentials.

I’d like it more if it were half the height. And that’s not hard to achieve, by removing the width capping, putting the heading and paragraph inline, removing the logo image and reducing unnecessarily large margins; I got it from what I think was 193px to what I think was 86px, yielding a result that I found much more pleasant.

Re: Gnome has moved to GitLab

#148
post #139
post #123

Earlier quoted context omitted.

Only "many"? o_O ;-)

In the dark prehistory of the Linux desktop, Qt/KDE was GPL so Gtk/GNOME went with the "more free" LGPL to support proprietary apps. I guess that strain of pragmatism hasn't gone away.

It's the other way around -- Qt wasn't GPL until 2005, GNOME started in 1997 in response to the non-free license.

https://en.wikipedia.org/wiki/GNOME#History

Re: Gnome has moved to GitLab

#149
post #148
post #139

Earlier quoted context omitted.

In the dark prehistory of the Linux desktop, Qt/KDE was GPL so Gtk/GNOME went with the "more free" LGPL to support proprietary apps. I guess that strain of pragmatism hasn't gone away.

It's the other way around -- Qt wasn't GPL until 2005, GNOME started in 1997 in response to the non-free license. https://en.wikipedia.org/wiki/GNOME#History

Ah, right, Qt wasn't GPL but it still "infected" apps with a copyleft-like provision.

Re: Gnome has moved to GitLab

#150

Earlier quoted context omitted.

Is it really that hard to write a little script to copy the issues over? Github has an exceptional API.

As others have pointed out, this is Gitlab. When it comes to github, they previously helped me transitioning a bugzilla into github issues, but it doesn't look like they do this anymore. Back then, I managed to get approval from all our contributors/issue authors so that their individual bugs and comments would show up as their individual bugs and comments, as well as retaining issue numbers. This is the code for it,…

Likewise mine for Cyrus:

https://github.com/cyrusimap/BugzillaImport

Post reply on HN