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

Every software system used at Gitlab

about.gitlab.com

Post reply on HN
Print view View original

21–30 of 123 posts

Re: Every software system used at Gitlab

#21

Post by api »

threeseed wrote: post #17
mr-karan wrote: post #13

For a company that makes and promotes FOSS, their tech stack sure is dominated by proprietary SASS vendor lock in solutions.

As someone who has a B2B startup there is almost nothing in the open source space for Marketing/Sales Ops. And anything that does exist is really low quality. And it's because (a) most developers aren't exposed to non-Engineering parts of the company so they have no understanding of what problem to solve and (b) it is incredibly lucrative to build a proprietary SaaS solution.

That kind of software is not fun or sexy, so people have to be paid to write it. Same goes for accounting where there are few open source solutions. Boring as hell, and profitable.

Re: Every software system used at Gitlab

#23

Post by echelon »

durpkingOP wrote: post #2

Why is salesforce the center of attention?

How much money do you wager that Salesforce license costs?

I know there's the whole build-vs-buy debate, but with the cost of Salesforce, might it not be better to just stick everything in a database and throw a MySQL WYSIWYG tool like phpmyadmin in front in order to let non-engineers see the schema and build forms?

I suppose if you're earning money hand over fist (or keep getting VC funds) then the cost of your Salesforce license doesn't matter. But I bet that hurts. And unlike a lot of the other software in use, Salesforce comes with steep lock-in.

Re: Every software system used at Gitlab

#24

Post by bdcravens »

mr-karan wrote: post #19
threeseed wrote: post #17

Earlier quoted context omitted.

As someone who has a B2B startup there is almost nothing in the open source space for Marketing/Sales Ops. And anything that does exist is really low quality. And it's because (a) most developers aren't exposed to non-Engineering parts of the company so they have no understanding of what problem to solve and (b) it is incredibly lucrative to build a proprietary SaaS solution.

> there is almost nothing in the open source space for Marketing/Sales Ops There is https://erpnext.com/ which is completely FOSS built on Frappe framework. If anything, it is rather higher quality than most SASS solutions out there.

It's not entirely clear on their website, but I assume the full software is at https://github.com/frappe/erpnext, and they have a model similar to Sentry?

Re: Every software system used at Gitlab

#27

Post by troquerre »

threeseed wrote: post #11
troquerre wrote: post #10

How did GitLab track and create this diagram? Is there a service that does it automatically?

It looks very much like OmniGraffle. And adding a new system is a pretty big deal at a large company so keeping it up to date isn't that difficult.

I meant how do they track the data? If they're just doing it manually that makes sense though it seems inefficient...

Re: Every software system used at Gitlab

#29

Post by spondyl »

inopinatus wrote: post #22

I’m wondering where the GL is, for when we outgrow Xero (which was about six months ago).

This isn't a recommendation or advice but if you're after a ledger that's larger than what Xero can offer to a big org, Netsuite seems to be what Gitlab uses and is ironically enough also what Xero uses. Unfortunately (and somewhat ironically?) we're too big to actually have Xero run on Xero

Re: Every software system used at Gitlab

#30

Post by spondyl »

I don't know if any Gitlabbers are in the comments but I'd be interested to know: Is this basically your internal asset register open sourced?

I suppose they're not particularly top secret but there could be a version that has some more sensitive data and this is a safe derivative for example. Similarly, such an asset register would likely have non-technical assets as well while this just seems to be tangible, technical things?

I figure any large company with a risk management function will already have/need such a spreadsheet (or document), complete with some sort of data classifications to exist for auditing reasons so the interesting step is maintaining it out in the public.

Kudos to Gitlab for having the culture to allow this sort of stuff :)

Post reply on HN