News for hackers. Stuff that matters.
Re:GitLab 8.11 Released with Issue Boards and Merge Conflict... by kolanos on Monday August 22, 2016 @03:59PM (#12338979)
Congrats on the release. Haven't tested this version, but have tried recent versions and if there's one thing that I think GitHub still runs circles around GitLab it's accessibility. If you don't believe me, try firing up a screen reader and see which you find easier to navigate with your eyes closed. In some cases you'll run smack into a brick wall with GitLab. So if there's one area where massive improvement is needed (and would be appreciated) it's accessibility. Happy to help on this front, but I know for a fact there's already several open issues relating to accessibility for GitLab.
Re:GitLab 8.11 Released with Issue Boards and Merge Conflict... by sytse on Monday August 22, 2016 @04:57PM (#12339381)
Thanks. I agree will still have work to do in terms of accessibility to screen readers. Feel free to file an issue, existing issues are on https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&sta... And of course code improvements to fix things are also very welcome.
Re:GitLab 8.11 Released with Issue Boards and Merge Conflict... by fsiefken on Monday August 22, 2016 @05:07PM (#12339457)
Hi Kolanos, I count 6 GitLab command line interfaces of a different type. They might not provide all the features, but perhaps it provides a solution for visually challenged users. https://about.gitlab.com/applications/
Re:GitLab 8.11 Released with Issue Boards and Merge Conflict... by foepys on Monday August 22, 2016 @04:55PM (#12339368)
This is one of the few points I have to criticize as well. GitLab's design is a bit too chaotic for me. It's missing visual dividers in a lot of places, especially in the issue tracker. Also GitHub feels better on horizontally smaller screens.
Re:GitLab 8.11 Released with Issue Boards and Merge Conflict... by luibelgo on Monday August 22, 2016 @05:19PM (#12339531)
Also having that big header plus tabs just grabs most of the vertical space in the screen, very bad decision now that most of the screens have way more horizontal space.
Re:GitLab 8.11 Released with Issue Boards and Merge Conflict... by rmetzler on Monday August 22, 2016 @05:38PM (#12339640)
Gitlab's in-project navigation recently changed, Everyone on my team was confused.
Re:GitLab 8.11 Released with Issue Boards and Merge Conflict... by sytse on Monday August 22, 2016 @05:41PM (#12339661)
We know that navigation redesigns are confusing. But we want to keep iterating to make it better. We explained the reasoning behind the change in https://about.gitlab.com/2016/06/06/navigation-redesign/
Re:GitLab 8.11 Released with Issue Boards and Merge Conflict... by daxelrod on Monday August 22, 2016 @11:00PM (#12341073)
Almost all of the navigation redesign was excellent. The information hierarchy was made much clearer.

The only thing that confuses me and my coworkers about the new design is the decision to hide the left navigation bar behind a hamburger menu by default. It's great that we can pin it open now, but why hide all of that useful navigation behind an ambiguous, easy to miss, unlabeled icon?

Re:GitLab 8.11 Released with Issue Boards and Merge Conflict... by randx on Tuesday August 23, 2016 @04:36AM (#12342237)
> but why hide all of that useful navigation behind an ambiguous, easy to miss, unlabeled icon?

Few reasons:

1. After redesign its possible to use application without sidebar for most of day-to-day tasks. I personally use sidebar 2-3 times per day while using GitLab whole day. Keeping it hidden by default allow me to focus on context and save screen space (really valuable on small laptop)

2. Both sidebar and project navigation visible at same time confused a lot of users. For example user clicked on sidebar "Issues" while they believed it will take them to project issues page.

Re:GitLab 8.11 Released with Issue Boards and Merge Conflict... by sytse on Monday August 22, 2016 @11:21PM (#12341151)
Thanks, glad to hear the new navigation was a success. I hope that someone else can chime in on the hamburger default.