It isn't so much about the customer but about the product. Our ambition went from being a source code tool to a complete DevOps platform delivered as a single application.
I think a lot of the changes you see can be explained from that.
12,257 karma · joined December 15, 2009
It isn't so much about the customer but about the product. Our ambition went from being a source code tool to a complete DevOps platform delivered as a single application.
I think a lot of the changes you see can be explained from that.
Maybe you're working on a self-managed version that still needs to be updated?
Regarding user interface modularity you can already turn on and off many parts in the front end https://imgur.com/a/aIRkDmt
Please note that about.gitlab.com contains all our static content, including our 10,000 page handbook. This typo isn’t on our main about page but deep in the marketing handbook.
If there is a right of first refusal many investors will decline to engage in future rounds since if they end up negotiating a good deal it might fall apart at the last moment.
It is a funny contrast that GitHub is closed source and hosts most of the open source code in the world. And GitLab is open core and hosts mostly closed source (and maybe the most closed source).
In some way an alternative for using Kubernetes and managed services of cloud providers.
I think there is a need for something that is easier to use than Kubernetes. I’ve started the 5 minute production app for this. The idea is to use managed services and Terraform to make stateful services easy. This way you’re not locked in but have flexibility going forward.
Because of the expected volume we had a different process for responding on social yesterday and I wasn't part of that group.
I think the blog post with me as the author https://about.gitlab.com/blog/2021/01/26/new-gitlab-product-... and the FAQ https://about.gitlab.com/pricing/faq-new-product-subscriptio... answer most questions. But happy to answer any other questions.
So apart from adding the cloud non-compete clause (don't offer Elastic as a Service) there are many more restrictions added compared to Apache 2. For example I think linking can only happen with GPL3 code and it is copylefted instead of permissive https://en.wikipedia.org/wiki/Comparison_of_free_and_open-so...
PS: I agree this post should be about GitHub and what they achieved for the thriving community of developers in Iran who are making things work despite their circumstances.
This includes many proprietary ones, we generally choose the product that will work best for us, considering the benefits of open source, but not excluding proprietary software.
Mattermost is not part of the single application that GitLab is. There is a good integration between with GitLab and our Omnibus installer allows you to easily install it. But it is a separate application from a separate company.
I'm posting this because I found a lot of people don't know that Zoom includes a complete chat client that includes channels.
And #HugOps to the engineers at Slack working on this. I appreciate that they posted a periodic update even when there was no news to report: "There are no changes to report as of yet. We're still all hands on deck and continuing to dig in on our side. We'll continue to share updates every 30 minutes until the incident has been downgraded."
Maybe a few things are happening:
1. Some large technical improvements can be shipped in multiple changes that add value.
2. Most companies do more large technical changes than is optimal.
3. Engineers are motivated to make the large technical changes since they are interesting and make their future work easier so they will prioritize them despite the measure.
4. GitLab is having fewer larger technical improvements than optimal.
5. Our dual career structure ensures that there are engineers who can do these larger technical improvements without being below average themselves because they are more productive than others.
6. We are not pushing very hard on this metric since we do it in a group setting instead of per individual.
I think that complexity is hard to measure and therefore easy to game.
At GitLab we only measure tasks completed, the number of changes that shipped to production, with the requirement that every change has to add value. This measure has been used throughout R&D https://about.gitlab.com/handbook/engineering/performance-in... to assess productivity for multiple years now with good success https://about.gitlab.com/blog/2020/08/27/measuring-engineeri...
When you tell new engineers about this target they see a great opportunity to game it, just ship smaller changes. It turns out that smaller changes are quicker to ship. Lead to better code and tests. Have lower risk of cancellation and problems in production. And lead to earlier and better feedback.
Inspired by Goodhart’s Law I'll propose the following: A measure that when it becomes a target improves productivity. ~Sijbrandij's Law