Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wikimedia is moving to Gitlab

mediawiki.org

Post reply on HN
Print view View original

141–150 of 408 posts

Re: Wikimedia is moving to Gitlab

#141

Post by naavis »

SparkyMcUnicorn wrote: post #41
gravypod wrote: post #7

One thing stopping me from moving my company's code to gitlabs cloud offering is the storage sizes for repos being extremely small. I heard from a rep that this will change in November. I'm wondering if this purchase-more-storage change come relates to this?

The limit is 10GB, while GitHub's limit is "ideally less than 1 GB, and less than 5 GB is strongly recommended". I don't consider 10GB to be "extremely small", especially since that's a larger than usual limit for a hosted solution.

You can buy tons more space for Git LFS on GitHub. 10GB seems to be a hard limit on Gitlab.

Re: Wikimedia is moving to Gitlab

#142

Post by mikey_p »

Deukhoofd wrote: post #27
q3k wrote: post #17

Earlier quoted context omitted.

They are still very limited when it comes to functionality though - only the first column in https://about.gitlab.com/pricing/self-managed/feature-compar... , right?

They probably use the free Open Source option, which gives access to the top tiers for free. https://about.gitlab.com/solutions/open-source/

That means they are running non-free code, which seems to be one of their main points against Github.

Re: Wikimedia is moving to Gitlab

#143

Post by mikey_p »

Grimm1 wrote: post #21
q3k wrote: post #17

Earlier quoted context omitted.

They are still very limited when it comes to functionality though - only the first column in https://about.gitlab.com/pricing/self-managed/feature-compar... , right?

My understanding is you can self host and pay a sub and get access to all the other features. I may be wrong.

Yes, but that's only if you self-host the Enterprise Edition which contains non-free code, not the Community Edition which only contains free code.

Re: Wikimedia is moving to Gitlab

#144

Post by abbe98 »

jancsika wrote: post #53

Anyone thinking of moving to their own Gitlab instance with Gitlab CE-- either stay on Github or prepare to waste your time dealing with user spam bots that pollute your site's search results. In other words-- if you want the common use case for a FOSS project: 1. publicly viewable main repository with publicly viewable issue tracker 2. requirement to log in to view all snippets, user profiles, perhaps even other rep…

Is this mainly a concern for the Gitlab issue tracker? Wikimedia will continue to use Phabricator for issue tracking, Gitlab CE will only be used for CI and code review/hosting...

Re: Wikimedia is moving to Gitlab

#145

Post by encom »

rightbyte wrote: post #137
phikai wrote: post #117

Earlier quoted context omitted.

Hi! I'm the PM at GitLab who works on Snippets, so thanks for providing this feedback. We do have Recaptcha support which can be configured - are you seeing these kinds of issues with that enabled/configured? One item that is on the roadmap that is coming and may be of interest is `Optional Admin Approval for local user sign up` - https://gitlab.com/groups/gitlab-org/-/epics/4491 . I'm not in the group working on tha…

Relying on Google's Spying-as-a-Service tooling is not very FOSS at all. There need to be other ways to reach out to users who block Google.

I immediately back out whenever encounter Recaptcha.

The other day I was forced to endure it, because I wanted to delete my ancient Minecraft account, since Microsoft pulled a Facebook and are going to require a Microsoft account to play going forwards. Without exaggeration, it took me 15 minutes of training Google surveillance AI (had to solve it three times), for Recaptcha to let me in. I guess Google really hates me.

Re: Wikimedia is moving to Gitlab

#146

Post by e12e »

eatthoselemons wrote: post #103
dietrichepp wrote: post #9

Earlier quoted context omitted.

Probably because you got used to Critique at Google ;) I agree though. I think the most important thing in a code review system is inline comments in the diff itself, and that’s something you get from Gerrit, Phabricator (Differential), etc. It encourages people to discuss the particulars of of a diff. Merge approval can be made contingent on resolving minor issues within a diff. Diffs are also approved on a per-diff…

Do you think that gitlab will ever add inline diff comments? I don't know if it would even be feasible to add to gitlab

More online than comments on the changes in the Mr? Like: https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/2...

(there's some old discussion on there, random example)

Re: Wikimedia is moving to Gitlab

#147

Post by gramakri »

jancsika wrote: post #53

Anyone thinking of moving to their own Gitlab instance with Gitlab CE-- either stay on Github or prepare to waste your time dealing with user spam bots that pollute your site's search results. In other words-- if you want the common use case for a FOSS project: 1. publicly viewable main repository with publicly viewable issue tracker 2. requirement to log in to view all snippets, user profiles, perhaps even other rep…

The spam is infuriating (not GitLab's fault, of course). Atleast, on our instance at https://git.cloudron.io, we got massive snippet spam. After we disabled snippets, we got massive spam on the issue tracker (!). The way we "fixed" is by turning on mandatory 2FA for all users.

As a general lesson, what we learnt is these are not bots. These are real humans working in some poor country manually creating accounts (always gmail accounts) and pasting all sorts of random text. Some of these people even setup 2FA and open issues with junk text, it's amazing. Unfortunately, GitLab from what I can tell cannot make issues read-only to non project members (i.e I only want project members to open issues, others can just read and watch issues).

Currently, our forum spam (https://forum.cloudron.io) is way more than GitLab spam. On the forum, we even have Captcha enabled (something we despise) but even that doesn't help when there are real humans at work.

Re: Wikimedia is moving to Gitlab

#148

Post by barnabask »

protoduction wrote: post #133
phikai wrote: post #117

Earlier quoted context omitted.

Hi! I'm the PM at GitLab who works on Snippets, so thanks for providing this feedback. We do have Recaptcha support which can be configured - are you seeing these kinds of issues with that enabled/configured? One item that is on the roadmap that is coming and may be of interest is `Optional Admin Approval for local user sign up` - https://gitlab.com/groups/gitlab-org/-/epics/4491 . I'm not in the group working on tha…

Hi phikai, I built a privacy friendly alternative to ReCaptcha called FriendlyCaptcha [1], is there a possibility to see this integrated as a more user friendly alternative? Happy to chat (e-mail in profile) [1] https://friendlycaptcha.com/

Man this needs more attention, cool project. I see you tried to submit to HN a couple of times and didn't get traction, that's too bad. Don't give up!

Re: Wikimedia is moving to Gitlab

#149

Post by ran3824692 »

sytse wrote: post #126
ran3824692 wrote: post #109

Earlier quoted context omitted.

There's been a gitlab bug for almost 3 years to stop relying on recaptcha, https://gitlab.com/gitlab-org/gitlab-foss/-/issues/45684 Debian, KDE and Gnome have never wanted to make their users run Google's nonfree javascript blob to contribute on their gitlab instance. There's been interest, Gitlab has done very little about it. Edit: other bugs about this can be found here https://gitlab.com/gitlab-org/gitlab-foss/-/…

I think the code of this problem is that it is hard to identify if a user is a bot or a human. I've not seen any elegant free solutions to this.

That is not the core of the problem. Spammers are humans, and sometimes they will solve recaptchas in large quantities to get their spam through. Its about having a multipronged approach for administrators to stay ahead of them. For some examples of free solutions see https://www.mediawiki.org/wiki/Manual:Combating_spam. It's even possible to connect spamassassin to forms. Gitlab needs tools and automation that detects and rolls back spam, bans users, knobs to tune restrictions and rate limits based on how spammers are acting. Gitlab inc just hasn't seemed to care much to help people trying to use Gitlab and keep their software freedom.

Re: Wikimedia is moving to Gitlab

#150

Post by 20after4 »

languagehacker wrote: post #40

In the past, I've found Gerrit to be reasonably good. Phabricator, on the other hand, not so much. Having worked with MediaWiki in the past on CRs, I think this will be a good move to modernize things for them. When faced with a similar task around the same time at Wikia (now Fandom), we chose GitHub while we were moving off of SVN. I'm glad we did at the time, even without all the additional features GitHub has. I u…

What issues did you have with Phabricator? I'm maintaining phabricator for the WMF and I'm interested in anything that could improve the user experience.
Post reply on HN