HNHacker News
TopNewBestAskShowJobs

sytse

12,257 karma · joined December 15, 2009

I'm a co-founder and executive chair of GitLab https://about.gitlab.com/ and co-founder of Kilo Code. More information about me is on http://sytse.com/ I'm also a general partner at Open Core Ventures https://opencoreventures.com/ (portfolio companies are listed on the website)
submissionscomments
sytse··on Starship – SN8 – High-Altitude Flight Test
And they had enough confidence that it might work that they attempted to land the first attempt on solid ground instead of in the water.
sytse··on Death of an open-source business model
In the future contributors might insist on a DCO instead of an CLA so that it is impossible for the project to change from open source to a closed license. Debian insisted on that when switching to GitLab https://about.gitlab.com/blog/2017/11/01/gitlab-switches-to-...
sytse··on Why I Love Tailwind
In https://news.ycombinator.com/item?id=25305467 there was talk about the PETAL stack of which Tailwind is a part. It consists of Phoenix, Elixir, Tailwind, Alpine.js, and LiveView.
sytse··on Sourcehut's Second Year in Alpha
That sounds interesting and useful. Thanks for the explanation.
sytse··on Sourcehut's Second Year in Alpha
Local CI is very important to quickly solve failed runs.

The problem is that we need a ton of logic in the coordinator. For example on how to do matrix builds. For local builds to be perfectly similar we would have to recreate that logic inside the runner. This is hard, not in the least because it are different programming languages.

sytse··on Sourcehut's Second Year in Alpha
The parent asked which features of sourcehut are not in GitLab. I think manual triggers are in GitLab https://forum.gitlab.com/t/gitlab-ci-run-pipeline-manually/1... and I assume post build triggers are.

Logging in via SSH seems useful although that would mean keeping the machine running after a failed build.

sytse··on Investing in Isovalent
What do people think about this way to explain eBPF:

Microkernels were presented as the future in which fewer things would run in the kernel. Instead we've gone in the other direction in which more is running inside the kernel.

Monolithic kernel: the Network Device runs inside the kernel and the Packet Filter outside.

Microkernel: both the Network Device and Packet Filter run outside the kernel.

eBPF: both the Network Device and the Packet Filter run inside the kernel.

sytse··on A 20kg hybrid drone that can fly at 50kmh for 4 hours
For reference, the Stihl chainsaw I just purchased had a 50:1 gasoline to oil mix. That is 2%, of course there are probably 25:1 or 20:1 engines out there as well.
sytse··on The new pricing model for Travis CI
Deeplink to the GitHub Actions vs. GitLab CI part of the decision kit https://about.gitlab.com/devops-tools/github-vs-gitlab/ci-mi...
sytse··on Dan Kohn has died
So sad that Dan is no longer with us, he is gone much too soon. My sincere condolences. Dan was an extra ordinary human. He was patient, friendly, warm, smart, and moved an entire community forward, sometimes almost by himself.
sytse··on Wikimedia is moving to Gitlab
Thanks for creating this! I think adding support for this in GitLab is a no-brainer. After that we can consider enabling it for GitLab.com
sytse··on Wikimedia is moving to Gitlab
I think the focus of our Trust and Safety team has been on GitLab.com and not on all GitLab instances. We'll discuss changing this.
sytse··on Wikimedia is moving to Gitlab
That looks cool! Can someone create an issue to add support for this to GitLab? And maybe we can consider switching GitLab.com to this as well.
sytse··on Wikimedia is moving to Gitlab
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.
sytse··on Wikimedia is moving to Gitlab
At GitLab Inc. we have a Trust and Safety team https://about.gitlab.com/handbook/engineering/security/opera... that prevents spam.

So far that functionality has lived in separate repositories from the core codebase since few people needed it, the cycle time was quicker, and it is an advantage to not have the spammers see the code.

If there is strong interest in collaborating on this I'm sure they will be happy to engage. I'll ask them how best to structure this.

sytse··on Business Operations – Tech Stack
We use Okta (which is in the list) for AD purposes and JAMF (which I'll ask to add to the list but is on https://about.gitlab.com/handbook/business-ops/team-member-e... ) for Mobile Device Management (MDM).
sytse··on Business Operations – Tech Stack
Thank you!
sytse··on Business Operations – Tech Stack
Thanks! I think that this is possible because of the transparent culture we created. Other CEOs have the same level of knowledge. There is just no appetite in the company to risk saying things in public.

Yesterday someone showed us the new tech stack page in a meeting. We're all proud because it replaces a bunch of spreadsheets where each department (finance, security, people) tried to maintain the same list of apps with a single yml file. I ask if anyone has a concern if I tweet it, everyone is OK with it since it is already public anyway.

That takes a value of transparency https://about.gitlab.com/handbook/values/#transparency which has us be public by default https://about.gitlab.com/handbook/values/#public-by-default even when it is hard https://about.gitlab.com/handbook/values/#transparency-is-on...

And it takes us reinforcing these values now in 17 different ways https://about.gitlab.com/handbook/values/#how-do-we-reinforc...

sytse··on Business Operations – Tech Stack
For eSignature I speculated on Twitter https://twitter.com/sytses/status/1319360157113970688?s=21

For CDNs we switched from Fastly to Cloudflare because we needed support for SSH (port 22)

And for email sending I think you want multiple providers so you have a hot one (already know on the internet to send a large volume of mail in your name) in cause a provider has problems with delivery.

sytse··on Business Operations – Tech Stack
Our spend with vendors isn’t public because that vendors don’t want discounts published.
sytse··on Business Operations – Tech Stack
Yep, maybe the mods can change the title to reflect that this is the software GitLab the company uses.

This was probably submitted to Hacker News after someone saw my tweet https://mobile.twitter.com/sytses/status/1319325053217992704 which has some questions and answers in the replies.

John already linked to the architecture of GitLab the application in https://news.ycombinator.com/item?id=24869339 in case you are interested in that.

Happy to answer any questions about either.

sytse··on Business Operations – Tech Stack
Correct, GitLab running on GCP file servers for git repositories and GCP object store for most of the rest (container registry, artifacts, etc.)
sytse··on Atlassian moving to cloud-only, will stop selling server licenses
We (GitLab) have strong planning features but are missing workflow enforcement. GitLab also has a wiki but it is less user friendly than Confluence.
sytse··on Atlassian moving to cloud-only, will stop selling server licenses
What agile stuff are you missing from the paid versions of GitLab? We have epics, roadmaps, milestones, and iterations. The only thing that is missing I can think of is workflow enforcement, but that doesn’t strike me as Agile.
sytse··on HashiCorp Boundary
This is awesome, thanks for making this. Boundary seems like the missing open source building block to achieve Zero Trust.

Zero Trust means authenticating per application instead of per network. For more context see https://about.gitlab.com/blog/2019/04/01/evolution-of-zero-t...

Proxying connections as Boundary does seems like the most elegant solution to achieve this in a way that doesn't require modifying the application.

sytse··on How to Build a Great Series A Pitch and Deck
This is awesome! Great addition to the space. Another one I think is great is Sequoia their deck template https://www.slideshare.net/PitchDeckCoach/sequoia-capital-pi...
sytse··on You weren't meant to have a boss (2008)
And you are accountable to your employees. Take the board I have for example. It is a relief to know that if I’m not longer the right person they will replace me. If you are bootstrapped with 1000+ employees a board might be something you want even if you don’t need to do it from an ownership perspective.
sytse··on Gitter is joining Matrix
That sounds like a great use case and we would welcome Matrix support in GitLab. Adding this isn't on our company roadmap so it would have to be a contribution. See https://gitlab.com/gitlab-org/gitlab/-/issues/22996 for a related but not quite the same suggestion.
sytse··on Gitter is joining Matrix
1. ChatOps is still a feature of GitLab https://docs.gitlab.com/ee/ci/chatops/ and supports multiple chat platforms. GitLab doesn't need to own the chat to make chatops work.

2. GitLab contacted Matrix.

I think 3. and 4. have answers in https://matrix.org/blog/2020/09/30/welcoming-gitter-to-matri...

sytse··on Gitter is joining Matrix
From the GitLab side we're very happy with the new home for Gitter. Chat is very useful but using multiple incompatible technologies has lead to fragmentation and silos. For example external developers being on Gitter when the organization behind the project is on Slack. Matrix is a great way to solve that and we hope Gitter will contribute to the success of it.
← PreviousPage 7 of 34Next →