Add more space on Network page
Since I didn't find any related issues in the Masterplan for GitLab UI, I'd like to propose to add some space at the bottom of the Network page. Or just redesign it at all. =)
For example, the search input field is a bit tight, the background color of the left vertical bar is too dark, etc.
/cc @dzaporozhets
Activity
Milestone changed to %8.11
@blackst0ne thanks. I will see what we can do
For some excellent improvements on this we can take a look at:
the timeline scrolling of: http://www.oneviewcalendar.com/
This has some excellent improvements on readability of where we are in time.
and the network/timeline view / search functionality of: https://www.gitkraken.com
This has some excellent search functionality, colors and consistent use and spacing of curved lines.
Although github has a horizontal view, which has a focus on contributor instead of commit, I like the vertical scrolling which feels more native. We could however introduce a switch between the two:
- vertical scroll: focus commit message
- horizontal scroll: focus contributors vs master branch
other small github thingy, is the mention to keyboard shortcuts:
I think they do a wonderful job here
As for the space the graph takes up: there is no reason for this to be blocked by the css fixed width 1280px rule. It's one of those situations referred to in: https://gitlab.com/gitlab-org/gitlab-ce/issues/13680
obvious other changes, would be:
- the change from square to circular avatars
will come back to this!
Edited by Dimitrie Hoekstra
@dimitrieh are you working on this?
Milestone changed to %8.12
Reassigned to @dimitrieh
-
@dimitrieh feel free to unassign.
-
@jschatz1 thanks :) will got down on this real soon!
Milestone changed to %Backlog
-
@awhildy Wondering if we could do an in between update on this, which only involves css change.. Just making it wider for bigger screens would already be an incremental upgrade to this and would partly solve this issue, like in this mockup from my previous comment: https://gitlab.com/gitlab-org/gitlab-ce/issues/18640#note_14079517
@dimitrieh I love finding the low-hanging fruit. However, honestly, I'm not sure that those tweaks really add enough value or solve enough of the problem. I'm also very hesitant to change the max width of the page, as that feels pretty consistently set across all the other tabs in this experience, and other general pages of GitLab.
For this issue, I'd rather take a little more time to consider a larger overhaul of the page. Make sure it's great at solving the issues it is trying to solve, and overall clean up the design. Have the experience make better use of the space it has. I don't know enough about the history of how it came to be the way it came, but it does obviously look quite a bit out of place, and I do find it hard to parse. I like the examples you found in https://gitlab.com/gitlab-org/gitlab-ce/issues/18640#note_14078967. If we have a better idea of where we'd eventually want to go with the design, it could then be much easier to break that apart into chunks of work we could actually schedule.
mentioned in issue #29990 (moved)
moved to gitlab#5142
Hey!
GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current
gitlab-cerepository will become a read-only mirror, without any proprietary code. All development is moved to the currentgitlab-eerepository, which we will rename to justgitlabin the coming weeks. As part of this migration, issues will be moved to the currentgitlab-eeproject.If you have any questions about all of this, please ask them in our dedicated FAQ issue.
https://gitlab.com/gitlab-org/gitlab-ee/issues/13855You can also find more information here:
https://gitlab.com/gitlab-org/gitlab-ee/issues/13304- https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/
Frequently Asked Questions
For an up to date list of questions and answers, please take a look at
https://gitlab.com/gitlab-org/gitlab-ee/issues/13855What will we do with the repository names?
https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.
Why rename gitlab-ce to gitlab-foss?
Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear
I created a merge requests for CE, and this got closed. What do I need to do?
You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.
How does the licensing work in this new setup?
Everything in the
ee/directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in theee/directory, the process of contributing changes is the same as when using the gitlab-ce repository.Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?
No. Merge requests submitted to this project will be closed automatically.
Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?
Yes.
How will this affect users of GitLab CE using Omnibus?
No changes will be necessary, as the packages built remain the same.
How will this affect users of GitLab CE that build from source?
Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.
Where can I see a timeline of the remaining steps?
https://gitlab.com/gitlab-org/gitlab-ee/issues/13304Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?
Yes, these changes will be synced to gitlab-foss automatically, several times per day.
