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

GitLab Direction

about.gitlab.com

Post reply on HN
Print view View original

21–30 of 137 posts

Re: GitLab Direction

#21

Post by sytse »

davchana wrote: post #11
sytse wrote: post #7

Earlier quoted context omitted.

Thank you very much for the encouragement, I appreciate it after significant commenting today while flying from Mexico to San Francisco. You can rest assured we'll keep working on our vision https://about.gitlab.com/direction/product-vision/ The people that ask for fixes care about GitLab and are worth listening to. There is an almost infinite demand for new features and we can't make them all (even with more then 20…

I just want to let you know that I code just for hobby, super simplistic projects like notes app, javascrtipt utilities, personal blog on Jekyll etc, gitlab @ davchana, I absolutely love Gitlab, and have been using it since almost two years. Before it I always had to find a free hosting, with lot of shaddy banner ads or unreliable systems. Gitlab.com free edition has everything I wish for, & occassionally I read & wa…

Thank you very much!

Re: GitLab Direction

#22

Post by jmiserez »

rqs wrote: post #13
sytse wrote: post #4

Earlier quoted context omitted.

What is the nr. 1 performance/ux/bugfix you would like to see? BTW This month we shipped 35 performance improvements https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=... and there were 141 bugs closed in the release of this month https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8...

I don't know about the performance and bugfix issues, but based on my experience with gitlab.com, I don't think it has a good UX design. You see, there are many many best practices in the UX world, just like those in the programming world. And seems to me, GitLab is not following many of them. For example, the width of the content area. I've once read an article that trying to dig into that topic, and one opinion tha…

There already is an option to set this, at /profile/preferences:

Layout width

> GitLab can be set up to use different widths depending on your liking. Choose between the fixed (max. 1200px) and the fluid (100%) application layout.

Re: GitLab Direction

#23

Post by jmisavage »

omeid2 wrote: post #17
AFNobody wrote: post #15

Earlier quoted context omitted.

https://gitlab.com/gitlab-org/gitlab-ce/issues/38066 When glaring security issues sit open for a year, you need to understand GitLab is a problem for anyone who has regular security audits. I am not asking for 100% redirection of resources to fix all the issues. I am suggesting they reprioritize resource allocation to lean more towards fixing issues that exist instead of new feature implementation.

You want hardened enterprise features, you pay for it; or contribute it, it is open source. I don't understand the attitude of people like you.

They have both SaaS and self-hosting options which cost considerable amount of cash ($99/mo per user for the most expensive option) for any large scale deployment. They're earning plenty and they need to fix what is valuable to their customers.

Re: GitLab Direction

#24

Post by whitepoplar »

WhyDoPeople wrote: post #16
whitepoplar wrote: post #2

GitLab is like the average kid in class that everybody makes fun of for constantly asking questions, but the joke's on them because "a little bit of slope makes up for a lot of y-intercept." While GitLab may have warts, I feel that they're very earnestly working to make the product better, bit by bit, day by day, and will one day surpass GitHub.

Just curious, what specifically you mean by "surpass Github"? I mean this with no snarky intention. I'm just wondering what tasks Gitlab doesn't perform as well as Github for you; unless you were referring to the social awareness that Github has.

I mean surpass GitHub in both usage and revenue.

Re: GitLab Direction

#25

Post by kushalpandya »

rqs wrote: post #13
sytse wrote: post #4

Earlier quoted context omitted.

What is the nr. 1 performance/ux/bugfix you would like to see? BTW This month we shipped 35 performance improvements https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=... and there were 141 bugs closed in the release of this month https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8...

I don't know about the performance and bugfix issues, but based on my experience with gitlab.com, I don't think it has a good UX design. You see, there are many many best practices in the UX world, just like those in the programming world. And seems to me, GitLab is not following many of them. For example, the width of the content area. I've once read an article that trying to dig into that topic, and one opinion tha…

Hi,

Thanks for your feedback around content width. Making GitLab accessible on all screen sizes is important to us given that there are many users out there using HD (720p) screens primarily. Our design indeed has fixed width portrait container enclosing the page body (with maximum size being 1200px) so here's how it looks on a large monitor at 100% zoom: https://i.imgur.com/lTqL6X8.png

Hence if the browser viewport width goes below 1200px, page body ends up taking full width. Although this screen resolution being still widely used, I've opened an issue to discuss this further here https://gitlab.com/gitlab-org/gitlab-ce/issues/49488

Feel free to add more details to the issue.

Re: GitLab Direction

#26

Post by Spidler »

What I'm missing is a different security model than the current `If an endpoint can push to gitlab, it is trusted and can execute code server-side`.

There is no (current) way to enforce a 2fa step in order to push to a repository, and while you can technically implement them, that doesn't mean much, due to the nature of `git push`.

What I want is a 2fa-enabled review boundary between "commit" and "execute", which currently isn't possible.

Protected branches can be unprotected without an auth step.

There's nothing on the server-side that signs `gitlab` generated merge-commits in the commit graph, so no way to distinguish them from other merges.

There's no security boundary to change the deployment details, or to modify the deployment pipeline to run from a different branch.

Basically, I'd want a way to ensure that there's an authenticated hand-off between "commit" and "deploy" steps on the chain.

Also, it'd be nifty if one could get gitlab to maintain a version number, increasing with every merge request merged, in order to get smooth tagged builds when MR's are used.

Re: GitLab Direction

#28

Post by dstick »

Thanks for sharing this! The transparancy of GitLab is amazing for people like me who have no experience nor contacts in larger companies. The handbook is a joy to read!

I discovered GitLab when researching CI/CD workflow and thanks to your tight integrations had one setup within 24 hours.

Add to that the fact that 3 fellow Dutchies are the founders which inspired me to apply our own Security startup to YC19 and all I can say is: keep it up! You’re an inspiration :-)

The only bit of constructive criticism I have is that the Epic ‘feature’ being locked behind the highest subscription is a bit weird. I’d love to be able to create an epic for our first release version but can’t. If that feature could drop a tier, that would be... epic ;-)

Re: GitLab Direction

#29

Post by omeid2 »

jmisavage wrote: post #23
omeid2 wrote: post #17

Earlier quoted context omitted.

You want hardened enterprise features, you pay for it; or contribute it, it is open source. I don't understand the attitude of people like you.

They have both SaaS and self-hosting options which cost considerable amount of cash ($99/mo per user for the most expensive option) for any large scale deployment. They're earning plenty and they need to fix what is valuable to their customers.

What makes you think they're not listening to their paid customers and fixing their needs? Paid customers get a direct contact.

Re: GitLab Direction

#30

Post by kasparsklavins »

WhyDoPeople wrote: post #16
whitepoplar wrote: post #2

GitLab is like the average kid in class that everybody makes fun of for constantly asking questions, but the joke's on them because "a little bit of slope makes up for a lot of y-intercept." While GitLab may have warts, I feel that they're very earnestly working to make the product better, bit by bit, day by day, and will one day surpass GitHub.

Just curious, what specifically you mean by "surpass Github"? I mean this with no snarky intention. I'm just wondering what tasks Gitlab doesn't perform as well as Github for you; unless you were referring to the social awareness that Github has.

Performance and stability?

Still yet to have a day where I havent had a 500 error on gitlab cloud.

Post reply on HN