New icons related to issues
New icon spec
(Note)
- Standard size:
16px * 16px - Border thickness:
2px - Border radius:
3px
Issue page - sidebar
| Current icon | File name | New icon |
| ---- | ----- | --------- | ----- |
| 
| arrow-double-left | 
|
| 
| todo-add | 
|
| 
| todo-done | 
|
| 
| user | 
|
| 
| milestone | 
|
| 
| timer | 
|
| 
| calendar | 
|
| 
| label | 
|
| 
| weight | 
|
| 
| users | 
|
| 
| notifications | 
|
| | notifications-off | 
|
| 
| content-copy | 
|
Issue page - comment
| Current icon | File name | New icon |
| ---- | ----- | --------- | ----- |
|
| face-slight-smile | 
|
|
| face-smile | 
|
|
| face-smiley | 
|
|
| content-edit | 
|
|
| delete | 
|
| | abouse.svg | 
|
Mockup
| Current | New |
|---|---|
 |
 |
Where to get SVGs
https://gitlab.com/gitlab-org/gitlab-design/tree/master/progress/hazel/gitlab-icons/svg
Links
Sub-issue from #32894 (closed)
Activity
mentioned in issue #32894 (closed)
I REALLY like the smiley faces. You packed so much personality into those!
I think you may have the wrong 'todo-done' for the current icon.
At first I wasn't sure about the thickness, they still feel very similar to the font-awesome icons in that regard. Then I compared these new icons with the illustrations and I can see the parity you are going for.
Since we are moving to straight svg versus icon fonts, we are not bound to just one color. Maybe there is an opportunity to add some personality through slight color variation.
@sarrahvesselov wouldn't multiple colors per icon make changing the color via CSS more difficult? It's super easy to change the fill when they're one color.
Most icons are pretty small and I'm not sure multiple colors would be worth the extra dev trouble.
@tauriedavis no, I have not found it to be more difficult at all, it just uses the fill property in the css. Classes applied to the path take care of the color, here is an example. I am talking about 4 colors maximum for the icon's static and active state. Four classes take care of it all.
Just a thought for adding more personality to our interface with little effort. Icons are small but add up across the application in terms of weight and presence.
-
Yeah, totally understand the technical part. I just meant it's more code and colors to manage. But if it's worth it, cool. I'll leave that up to you and Hazel!
Edited by Taurie Davis 
Cool stuff @hazelyang !! I love the todo icons.
I worry about the smiley's though, as the mouth is i think to small. I rather go for a bigger mouth, which is instantly recognisable without squinting, as we have some animation going. the placement of the mouth makes it very adorable though, so in that sense
In order to gauge visual weight, i think you should provide a grid view of all icons :) wdyt?
color variation sounds cool to me, although i would suggest a focus on "slight color variation", as to not confuse with emoticons
mentioned in issue #32411 (moved)
I think you may have the wrong 'todo-done' for the current icon.
@sarrahvesselov Thanks! Updated it.
@sarrahvesselov @tauriedavis @dimitrieh
About slight color variation, it also sounds good to me. I'll experiment it on other icons. Thanks!
@dimitrieh You are right. The mouth should be bigger. The original mouth is not so obvious as the icon is small.
In order to gauge visual weight, i think you should provide a grid view of all icons :) wdyt?
Good idea. Will add the grid.
-
@hazelyang i see you created notifications icons. how do you see them working on the issue list?
we don't want to show notifications-off icon by default there correct?
Edited by Dimitrie Hoekstra 
This
is a standard RSS icon that is being used everywhere including GitLab.
I want to leave this comment just as a reminder to not replace that icon on RSS links with the new one.
Edited by username-removed-86853@dimitrieh @blackst0ne Thanks for bringing up this question! I think the icon for RSS will not be changed since it's a different action from the
Subscribeaction on the issue sidebar.
Discussion: Maybe when mousing over these 3 icons, we can have them has the background color?
Edited by Hazel Yang-
@hazelyang how would you replace the subscribe buttons not in the sidebar
Maybe when mousing over these 3 icons, we can have them has the background color?
@hazelyang Slight variation on that: do that when in focus
mentioned in issue #33677 (moved)
how would you replace the subscribe buttons not in the sidebar
The one we are using for RSS. (Did I answer your question?
Slight variation on that: do that when in focus
Sure, created it (#33677 (moved)).
@hazelyang do the notifications need to be in “3D”? They have a small rounding that gives them a bit of perspective, and the other icons don't have that. Maybe you have a rationale for this
@pedroms Thanks for mentioning this. I just did that intuitively.
Edited by Hazel Yangmentioned in commit gitlab-design@6364bef0
mentioned in issue #34027 (closed)
changed milestone to %10.2
added Discussion label
added Platform label
removed Discussion label
marked this issue as related to #38499
moved to gitlab#10133
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.
mentioned in issue gitlab#10430
