Gnome has moved to GitLab • Hacker News Board

Re: Gnome has moved to GitLab

#191

Post by diffeomorphism » Fri, Jun 01, 2018, 1:34 PM UTC

hajile wrote: 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…

> Firefox 45 (over 2 years old) and are looking to move to 52 (almost 15 months old)

That is quite misleading. They are using the extended support releases: https://www.mozilla.org/en-US/firefox/organizations/

So "almost 15 months old" should be the "most recent one up until the start of this month".

Re: Gnome has moved to GitLab

#192

Post by hajile » Fri, Jun 01, 2018, 1:37 PM UTC

Jasper_ wrote: post #143

hajile wrote: 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 Na…

Have you tried N-APIs? It definitely helps with the documentation issue? What exactly was lacking?

https://nodejs.org/api/n-api.html

Re: Gnome has moved to GitLab

#193

Post by matthberg » Fri, Jun 01, 2018, 1:47 PM UTC

anowlcalledjosh wrote: post #188

baud147258 wrote: post #177

Earlier quoted context omitted.

Link for Jwz's cadt post https://www.jwz.org/doc/cadt.html (edit: I didn't see it was already posted below)

Quick reminder: JWZ despises HN, so you'll need to copy-paste that link in order to remove the referrer header.

This could be fixed with rel="noreferrer noopener" added to the links, would that be a beneficial addition to HN?

Re: Gnome has moved to GitLab

#194

Post by fao_ » Fri, Jun 01, 2018, 1:52 PM UTC

TheRealDunkirk wrote: post #189

anowlcalledjosh wrote: post #188

Earlier quoted context omitted.

Quick reminder: JWZ despises HN, so you'll need to copy-paste that link in order to remove the referrer header.

I'm not saying the bridge has been repaired, but clicking that link doesn't seem to redirect to... THAT... image any more.

FYI - For me it auto-redirects to: https://imgur.com/32R3qLv

Re: Gnome has moved to GitLab

#195

Post by baud147258 » Fri, Jun 01, 2018, 1:57 PM UTC

TheRealDunkirk wrote: post #189

anowlcalledjosh wrote: post #188

Earlier quoted context omitted.

Quick reminder: JWZ despises HN, so you'll need to copy-paste that link in order to remove the referrer header.

I'm not saying the bridge has been repaired, but clicking that link doesn't seem to redirect to... THAT... image any more.

I tested the link, but I didn't get the redirect. I would have added the warning if it happened to me.

Re: Gnome has moved to GitLab

#196

Post by rimliu » Fri, Jun 01, 2018, 3:05 PM UTC

mic47 wrote: post #125

cellularmitosis wrote: post #103

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…

I think it's shame that lot of projects do. Why? 1.) Compared to Phabricator (which I used for almost last 4 years), github is really behind for code review (I didn't use gitlab, so can't compare). There is lot of missing features: I can't comment on selection of lines, see diff of subset of commits, do stacked pull request (one PR depends on another PR), view of open pull request is chaotic Effect is that it's way h…

Funnily, I ditched hg the moment it screwed my repo. But even then I was pretty sure git would win, and not for PR reasons.

Re: Gnome has moved to GitLab

#197

Post by brodock » Fri, Jun 01, 2018, 3:09 PM UTC

simula67 wrote: post #158

parvenu74 wrote: post #11

Was Github ruled out because it's not free enough in spirit or are the Gnome folks just wanting to run things on-prem?

You can run Github on prem using Github Enterprise [1]. However, that follows a subscription model and Github can potentially terminate it at any time. Gitlab has an open source version [2], which means that preferring Gitlab over Github prevents giving more control of the project's direction to another entity. ( Not speaking on behalf of GNOME of course, just remarking that it is a good thing that free software proj…

Also you are not allowed to use GitHub Enterprise in the "public facing internet" without "Private Mode" which means only people with an account on the system can access that.

https://enterprise.github.com/faq#faq-13

Re: Gnome has moved to GitLab

#198

Post by Karunamon » Fri, Jun 01, 2018, 3:09 PM UTC

artursapek wrote: post #60

kazz wrote: post #40

Earlier quoted context omitted.

I really wish more people would implement cookie notices like theirs. I really like the one that https://www.bosch.us/ uses too.

Are there really people who appreciate these redundant notices? Do you need a notice that a website uses TCP/IP too?

My first instinct upon seeing that intrusive popup was to invoke the element hider from uBlock and nuke it. I don't want to see that noise on this or any other website. Get out of my way and fuck off with the legalese. I'm browsing, I haven't signed any contract, get out of my face.

Re: Gnome has moved to GitLab

#199

Post by inevitable2 » Fri, Jun 01, 2018, 3:18 PM UTC

What's quite sad however, for an alternative to the big usual services and free software is to require user to sign up/register either using one of those big services with OAuth… or to feed Google's recaptcha service. One way or another, user loose. Or just stop to report issues/try to be involved in the projects.

And this apply to both gitlab.com or GNOME's instance. GitLab is supposed to be an alternative, but actually depends on those other services for users to use it (Google, GitHub and so on…)

Re: Gnome has moved to GitLab

#200

Post by boomlinde » Fri, Jun 01, 2018, 3:51 PM UTC

workinthehead wrote: post #185

matttproud wrote: post #159

Earlier quoted context omitted.

I wish it was that simple, but I never received a single notice of the migration or my need to do anything at all as a bug reporter. (Just ran a liberal grep on my inbox right now.) The only notice I received was after-the-fact. Sorry. Learning of GNOME'S cavalier attitude toward user reports and eventual product direction was exactly why I moved off the platform in the intervening years. I had high hopes when I was…

Bug reporters who can't even be arsed to follow up or check in on their reports aren't worth nearly as much as you seem to think they are.

The reports may still be relevant. If the problem is easily reproducible or even just well described, a bug report should be useful independent of the activity or further engagement of the reporter.