[HN Gopher] Gitlab 13.1
___________________________________________________________________
Gitlab 13.1
Author : bjoko
Score : 120 points
Date : 2020-06-22 18:30 UTC (4 hours ago)
(HTM) web link (about.gitlab.com)
(TXT) w3m dump (about.gitlab.com)
| dindresto wrote:
| With every release I wonder why our team is even paying for
| Gitlab Bronze. It seems to offer no value at all, might as well
| go for the free tier and save a thousand dollars a year.
| bryanlarsen wrote:
| Merge Request Reviews was moved to core as part of this
| release.
| dindresto wrote:
| Yes, this update basically reduced the value of Bronze
| significantly as there were no relevant new features coming
| to Bronze and those that we were paying for are now in the
| free tier.
| dindresto wrote:
| I'm not saying they should remove any free features, but now
| and then it'd be nice seeing a Silver feature come to Bronze.
| rakoo wrote:
| Maybe the value is in ensuring the Gitlab team can continue
| working on the product, because they are paid to do so ?
| matthewcford wrote:
| Same boat, although with GitHub pricing changes it's more
| advantageous to switch. The fact that the security and
| dependency management is locked at gold when they are free on
| Github is annoying.
| matthewcford wrote:
| Moving breakman into core is nice but not enough
| threeseed wrote:
| It's great and impressive how quick Gitlab moves in adding new
| features.
|
| But if I have a Graphic Design repo it emphasises Kubernetes,
| Packages and Security features that have zero relevance. And
| there is no way to disable them.
|
| And that on every single repo it places these Add
| License/Contributors etc buttons front and centre even though for
| 99% of internal projects they serve no purpose.
|
| Every release Gitlab seriously needs to step back and think about
| how to simplify the interface. Because it's starting to get a bit
| ridiculous.
| sytse wrote:
| This comment makes a lot of good points.
|
| I think we can stop recommending License and Contributors since
| GitLab is mostly used for closed source software. The templates
| will still be there but just not suggested until you started to
| create a new file.
|
| And you should be able to disable everything but the repo if
| you want to. And of course you can disable the repo as well if
| you just want the planning features for example.
| threeseed wrote:
| Also please put in place this simple UI rule: "If it doesn't
| need attention don't make it coloured or bold"
|
| e.g. thumbs up/down, report abuse etc.
| jayd16 wrote:
| >Graphic Design repo it emphasises Kubernetes, Packages and
| Security features that have zero relevance. And there is no way
| to disable them.
|
| You can do it in Settings > General > "Visibility, project
| features, permissions"
| lttlrck wrote:
| Yes agree completely. I'd love to whittle down the noise.
| rossmohax wrote:
| > It's great and impressive how quick Gitlab moves in adding
| new features.
|
| Don't trust their feature list, they often "forget" to use it
| themselves. Many of those features are there to tick the box
| and daze executives, but are barely usable in practice.
|
| It took them a year to start supporting Kubernetes clusters
| with RBAC, they didn't use autodevops for their own releases,
| even for simple components, nor any kubernetes integration,
| monitoring, feature flags, Geo, backup procedure. Who in the
| right mind is going to enable Web Application Firewall feature,
| when rules exceptions cannot be configured?
|
| Somewhere in comments here will be reply from Gitlab employee,
| saying that dogfooding is something they are constantly working
| on, it doesn't matter. What they should be doing is to update
| documentation pages with feature maturity level and have a
| block of links to most popular bugs related to the feature, so
| that poor devops engineers don't have to rediscover all the
| pain and come prepared.
|
| Just to be clear, Gitlab is an awesome tool, it is just not as
| awesome as their marketing wants us to believe.
| sytse wrote:
| _" Somewhere in comments here will be reply from Gitlab
| employee, saying that dogfooding is something they are
| constantly working on"_
|
| To ensure we meet your expectations I want to state that
| we're continuously working on dogfooding, you can track our
| progress in https://gitlab.com/gitlab-
| org/gitlab/-/issues?label_name=Dog...
|
| _" What they should be doing is to update documentation
| pages with feature maturity level and have a block of links
| to most popular bugs related to the feature"_
|
| That is a great idea and I wonder if
| https://about.gitlab.com/direction/maturity/ meets your
| expectations. We recently update the criteria for viable and
| complete to incorporate dogfooding:
|
| - Viable: Significant use at GitLab the company.
|
| - Complete: GitLab the company dogfoods it exclusively.
|
| And thanks for calling us an awesome tool. Hope you don't
| mind the tongue-in-cheek response at the top of my comment :)
| dan1234 wrote:
| Looks like WebAuthn is still missing, even though there seem to
| have been merge requests featuring it forever!
|
| Anyone know which milestone it'll be merged into?
| candiddevmike wrote:
| The alert integration looks interesting, but the screenshots for
| code intelligence look awful. Who decided to use a super light
| shade of gray on a white background?
| threeseed wrote:
| Their UI has a lot of these annoying issues and they never
| seemed to get around to fixing them.
|
| My other favourites:
|
| 1) UI is all muted and grey which is great because it allows
| you to focus on your code, issues etc. Well except for the
| Thumbs Up/Down buttons which are a bright yellow and the only
| thing to stand out. And it's a feature that serves no purpose
| in most cases.
|
| 2) Report Abuse button is next to the New Issue button. But
| it's given the same size and prominence. Is abuse really as
| common as creating new issues ?
|
| 3) Backgrounds. Some are light grey. Some are dark grey. Some
| buttons background is filled, others solid.
| jeldergl wrote:
| Thanks for adding your thoughts, hopefully I can shed some
| light in a few places.
|
| 1) I'm assuming you're referring to the emoji buttons. They
| are useful to determine upvotes and downvotes on issues and
| merge requests. These counts can be used when sorting for
| popularity. We leverage system emoji here and in most cases
| they are a bright yellow (https://emojipedia.org/thumbs-up/).
| It'd be possible to use our custom icon library
| (http://gitlab-org.gitlab.io/gitlab-svgs/?q=thumb-) for these
| buttons, but then they wouldn't visually align with other
| award emoji that can be added inline. Here's more info
| https://docs.gitlab.com/ee/user/award_emojis.html.
|
| 2) If you don't have permission to close the issue (or merge
| request), you will only see the 'Report abuse' button (I'm
| guessing this is what you're seeing), otherwise there would
| be a split button with 'Close issue' as the default option,
| and 'Report abuse' as the second. I agree that this needs
| some further consideration, so I opened an issue to start a
| discussion https://gitlab.com/gitlab-
| org/gitlab/-/issues/223775. Feel free to contribute and add
| your thoughts there too.
|
| 3) A few things are at work here. We recently updated our
| neutral palette to normalize it with the rest of the color
| palette, and address some accessibility items. We're working
| on updating the neutral variables and remap them throughout
| the product, see https://gitlab.com/gitlab-org/gitlab-
| ui/-/issues/627 and https://gitlab.com/groups/gitlab-
| org/-/epics/2964. If there's anything you don't think would
| be addressed by those changes, it'd be great if you could
| open a new issue (https://gitlab.com/gitlab-
| org/gitlab/-/issues/new) and cc the UX designers (@gitlab-
| com/gitlab-ux/designers). Regarding buttons, we are in the
| process of replacing deprecated buttons in the product with
| new ones from GitLab UI https://gitlab-org.gitlab.io/gitlab-
| ui/?path=/story/base-but.... Here are a few issues covering
| that effort https://gitlab.com/gitlab-
| org/gitlab/-/issues?scope=all&utf8.... Many other issues will
| be created to do the same in other parts of the product.
|
| I hope this helps, thanks again for your comments!
| jtwaleson wrote:
| I somehow had a feeling Gitlab would be bought this year, but the
| list dramatically falls apart upon closer inspection:
|
| - Google: will never work, completely different mindset and
| engineering culture. Gitlab feels way too unrefined (in a good
| sense).
|
| - AWS: Gitlab is already too different from their tech, and will
| never be that tightly coupled with the rest of AWS.
|
| - IBM: :') they wish
|
| - MS: already has GitHub
|
| Any others?
|
| I think any giant company would have a hard time integrating all-
| remote Gitlab.
| travbrack wrote:
| I think you're underestimating the power of a boatload of cash.
| All of the companies you listed could afford to buy gitlab.
| jtwaleson wrote:
| Sure they could, but it still needs to make sense from either
| a growth or a defense play. I don't see that for any of these
| companies.
| stock_toaster wrote:
| > I think any giant company would have a hard time integrating
| all-remote Gitlab.
|
| Atlassian maybe? ( _shudder_ )
| thereyougo wrote:
| "This month's Most Valuable Person (MVP) is Jacopo Beschi "
|
| What a cool company culture. telling people they are doing good
| in person is nice, telling it to them and also sharing it with
| the world is great
| leipert wrote:
| GitLab employee here:
|
| The MVPs are not employees, but community contributors as
| outlined here: https://about.gitlab.com/community/mvp/
|
| But yes, I agree: it is very nice to share the achievements of
| our OSS contributors with the world :)
| AaronFriel wrote:
| If anyone from GitLab is reading this, these pages are locked in
| a refresh loop. I can't read the content because it is
| scrolling/moving slightly with every refresh which is happening
| constantly.
|
| Latest version of Chrome stable, uBlock Origin in default config,
| HTTPS Everywhere, React/Redux devtools are the extensions I have
| installed.
|
| I let the page run for 30 seconds and:
|
| * CPU usage on two cores was at 100%
|
| * 2,943 requests were made for 319 MB of resources over 30.06
| seconds
|
| A staggering rate of 100 requests per second that persists
| indefinitely - I have no reason to believe the refresh loop is
| broken at any point.
| Fogest wrote:
| Same problem as you on Chrome. I thought it was just me. I see
| requests happening to many different sites.
| boleary-gl wrote:
| GitLab technical evangelist here.
|
| I can't seem to reproduce this - maybe it's uBlock Origin? Are
| you sure it's the default configuration? What were the requests
| to - just to the main HTML page?
| Earwig wrote:
| Same issue here as the original post and similar extensions.
| I followed the suggestion of clearing cookies for
| about.gitlab.com and it doesn't help.
| AaronFriel wrote:
| Yes, the page infinitely navigates back to itself resulting
| in a whole page refresh.
| [deleted]
| john_cogs wrote:
| Thanks for reporting this. I created an issue to report this to
| the Gitlab website team. You can follow along and anything I
| might have missed here: https://gitlab.com/gitlab-com/www-
| gitlab-com/-/issues/8052
| jeandp wrote:
| @AaronFriel try deleting your cookies for the website and see
| if that resolves it. I recall someone at GitLab having that
| problem the other day and think I recall that clearing their
| cookies fixed the issue for them. Either way I'll notify our
| marketing website team to have a look at this.
| AaronFriel wrote:
| One thing to look at is that the page does at least one whole
| page refresh by default, even an incognito window.
|
| If I open up the page in incognito, I see _two_ requests in
| the network tab for https://about.gitlab.com/releases/2020/06
| /22/gitlab-13-1-rel...
| rpadovani wrote:
| It is not in the blog post probably because it is still in Alpha,
| but Gitlab now has a Dark Theme <3
|
| Settings -> Preferences: there is a new theme called "Dark Mode
| (Alpha). Indeed still in Alpha, but I love they are working on
| this!
| robotmay wrote:
| Welp, this is confirmation that I haven't been keeping up on
| everything going on; when I learn about my most desired feature
| on my company's software from a Hacker News post :S
| leipert wrote:
| Before you file an issue, double check if an issue for the
| problems you experience with the Dark Mode already exists in
| this epic: https://gitlab.com/groups/gitlab-org/-/epics/2902
|
| And of course: have fun on the dark side (as they are the ones
| with the cookies)
| [deleted]
| citrus1330 wrote:
| I love GitLab
|
| Better UI than GitHub and was first to provide free private repos
| kingbirdy wrote:
| Bitbucket provided free private repos before Gitlab existed
| kroltan wrote:
| Severely limited* free private repos
___________________________________________________________________
(page generated 2020-06-22 23:01 UTC)