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

Announcing new tools, forums, and features

github.com

Post reply on HN
Print view View original

231–240 of 282 posts

Re: Announcing new tools, forums, and features

#231

Post by brazzledazzle »

elliotec wrote: post #82
markdog12 wrote: post #61

Earlier quoted context omitted.

> I don't really quite understand all the love of GitLab - Open Source - Free private repos - Free self-host (edit to add "Free") - Everything in one spot (repos, ci, review, coding environment, etc...)

It's only kind of open source, and only partly. They call it open core, so saying open source outright is a bit misleading. The review feature is very new in GL, and that plus all of the things you are mentioning within "everything in one spot" is available in this update (except maybe the coding env, not sure what that means anyway), if you've read the announcement. Github also has self hosting.

Github Enterprise (their self hosted version) is quite expensive.

Re: Announcing new tools, forums, and features

#232

Post by hitekker »

sytse wrote: post #206
tyre wrote: post #201

Earlier quoted context omitted.

Meta-comment: As a founder and engineer, I used to give a lot of shit to Social Media as a growth channel. GitLab staff are "on point" by commenting on anything relevant to their industry (code creation/management) where their target customers are (HN). To other founders, this is what good marketing looks like.

Thanks Chris. It is a tricky balance not being too noisy (I understand the sentiment of https://news.ycombinator.com/item?id=12502468 ) but I tried to add to the conversation by by sharing our thoughts about the project repo dilemma.

A willingness to engage with the community as often and as effectively as you guys have is surely not commonplace.

Hope you can keep it up! :)

Re: Announcing new tools, forums, and features

#233

Post by rwbcxrz »

tootie wrote: post #225
captn3m0 wrote: post #17

This is a rough summary of what all I read in the blog post: 1. projects. replaces trello, waffle.io, zenhub and many other similar services. 2. code reviews allow approval/request changes as sunny's screenshot shows 3. reviews can be made mandatory. 4. github platform integrations is getting a roadmap 5. a graphql api to query their database 6. enforce 2fa in organizations (much love for this one) 7. summarized time…

This all seems like baby stuff compared to Atlassian though. JIRA, Confluence, Bitbucket, HipChat. That's hard to beat.

> baby stuff

JIRA doesn't support markdown. That seems like baby stuff to me.

Re: Announcing new tools, forums, and features

#234

Post by kareemm »

luikore wrote: post #229
old-gregg wrote: post #183

This is the example of how hard it can be for companies, especially successful companies, to alter their course even slightly. Github success was about making code repositories pretty and social. But this is no longer enough to keep evolving as a company of their size. Yet the internal product DNA still revolves around repos, so as a result, issues, wikis and now Projects (!) live under a single repository. This is b…

One project with multiple repos just adds unnecessary work of integration and management. Or, your definition of project is something big, vague and blurry. Some people are eager to divide their project into multiple repos in spite of git being a distributed version control system. Having many teams doesn't mean you should have many repos. Why not just let your team work on one small directory inside the repo?

> One project with multiple repos just adds unnecessary work of integration and management. Or, your definition of project is something big, vague and blurry.

I think this depends on your job function. At Codetree we have a bunch of customers who need to see a project that spans multiple GitHub repos. The person who needs this view is the person responsible for delivery - usually a project manager, a product manager, or a dev manager.

A common example is a project that spans an API repo, a front end repo, and a mobile repo. If you're responsible for delivery, you want to be able to answer questions like "How much work is left to deliver the FooBar feature", or "Show me all the tickets assigned to Joe". To answer these, you must see issues from multiple repos rolled up into a single view.

Re: Announcing new tools, forums, and features

#235

Post by Manishearth »

garethadams wrote: post #164
sytse wrote: post #155

Earlier quoted context omitted.

To make sure there is no confusion we now refer to ourselves as open core https://about.gitlab.com/about/#stewardship I want to echo here what I said in https://news.ycombinator.com/item?id=12501271 "If there are features that people think that should belong in the open source edition we're all ears. We've done so before https://news.ycombinator.com/item?id=10931347 A feature comparison between CE and EE can be found…

> 1. Can you rebase in the GitHub interface? > 2. Does GitHub have an option to fast forward merges? So is Gitlab's aim to just play catchup to Github?

GitLab has had a larger feature set than GitHub for a long time now.

Github compromises by having a nice ecosystem of tools which you can plug in, but having it built in is always nice since the integration is tighter.

Re: Announcing new tools, forums, and features

#236

Post by eropple »

tyre wrote: post #201
sytse wrote: post #190

Earlier quoted context omitted.

I agree that putting projects under repositories looks counterintuitive. In BitBucket you have multiple repositories under one project https://confluence.atlassian.com/bitbucket/projects-79249795... We at GitLab are trying to keep it simple by having only one repository, one wiki, one issue tracker, one CD pipeline, and one set of milestones per project. Projects always below to a group. We aggregate on the group lev…

Meta-comment: As a founder and engineer, I used to give a lot of shit to Social Media as a growth channel. GitLab staff are "on point" by commenting on anything relevant to their industry (code creation/management) where their target customers are (HN). To other founders, this is what good marketing looks like.

YMMV, but I find sytse so hugely overbearing that I actively don't want to use GitLab because I don't want to encourage what I see as tacky, bad behavior. He and other GitLab staff can do as they like, but I'm not rewarding it.

Re: Announcing new tools, forums, and features

#237

Post by reitanqild »

oldmanjay wrote: post #215
st3v3r wrote: post #203

Earlier quoted context omitted.

I've only seen that among members of the alt-right.

The alt-right is apparently everyone's favorite new boogeyman for use in thought-free dismissal It's always disappointing to see a self-described intellectual community give over so heavily to such an obviously broken thought process, but humans being the emotionally manipulable creatures they are, it makes sense.

IMO:

A lot of people seems to think they are smart because they belong to a powerful or politically correct group.

Also a lot of people seems to think they are smart because they are rooting for the underdog or just plain contrarian. ; )

Re: Announcing new tools, forums, and features

#238

Post by vernon99 »

yosyp wrote: post #175
dr_win wrote: post #148

Earlier quoted context omitted.

I would put all projects under one repo as orphan branches. With some branch-naming conventions you can easily separate those.

Imagine you just hired a new web developer, and added him to this repo. His first local repo clone will include 3 entire projects for iOS, Android, and backend server, that he has no use for, or should even have permissions to access in the first place. This sounds like a security nightmare, that also significantly impacts local update times and makes for a huge repo.

So companies like Fb (with their gazillions of files) can afford a single repo and you hiring a new developer cannot?

Re: Announcing new tools, forums, and features

#239

Post by Animats »

I just hope Github doesn't pivot in a direction that makes them no longer a safe place to archive open source code. We've had two failures already - Google Code (shut down) and Sourceforge (started putting adware on the executables of others.)

Github, please don't blow it.

Post reply on HN