Introduce the shibui gitmoji (beautiful and simple)

[EmGarr]

Hello @carloscuesta :sunglasses:!

• Emoji: :o:
• Code: :o:
• Description: Shibui (渋い) (adjective), shibumi (渋み) (noun), or shibusa (渋さ) (noun) are Japanese words that refer to a particular aesthetic of simple, subtle, and unobtrusive beauty. source I know it is not fairly common in programming. However, in my company when we do something simple and beautiful we put a shibui tag in the commit. I'd love to see the concept appear in gitmoji :)

[vhoyer]

Firstly, I loved the idea as an idea, because I'm obsessed with Japanese culture (in fact, I was listening to my Spotify Wrapped while writing this comment, and most of the songs are in japanese), but because I liked it so much, I feel the need to be specially impartial; I've always adopted the position of trying my best not to add more emojis to the "spec" to prevent useless complexity for newcomers to gitmoji (since I've encountered resistance amongst my peers about the adoption of gitmoji due to "there being too many emojis, I always feel confused about which one to use"). Stick with me in this haha:

So here are my concerns/inquires:

• can't this be covered with :art: or :recycle:?
• that suggested description is far too large to our standards, all of our descriptions have been short concise and to the point in the past, can you suggest another description more in the style of gitmoji? Bear in mind, this description we ask in the issue template should be the description you see in the emoji card bellow the name of it on the site, you know? Eye balling, I think the largest description we have is for :passport_control: ("Work on code related to authorization, roles and permissions.")
• I'm worried that, with the emojis, we are trying to always describe/categorize the "what" has been done in one particular commit (:white_check_mark: , :lock: , :zap: ...), not the "how" that "what" was done (the exceptions being :hankey:, :beers:), and I feel that this emoji, :o:, better fall in the category of "how", which in the recent past has been a deal breaker on accepting new emojis, so what I'm trying to say is: do you have examples of when one would use this emoji?
• Referencing a Japanese concept may be harmful to the international aspect of this project as it was pointed out on #922, besides, the :o: emoji should represent "affirmation"/"correctness"/"agreement" according to the Japanese interpretation on the subject as far as I know, which don't really represent 渋み very well in my opinion, maybe :diamond_shape_with_a_dot_inside: could represent better this concept, but really, I only know what I read from the Wikipedia introduction so pardon me if I'm wrong in this, what do you think? do you agree with my point that :o: is not really a great fit?

[EmGarr]

Thanks for the answers :heart: .

I clearly here your concerns and shibui is clearly a "how" and not a "what". I mostly used it when I find a solution to a complex problem with a really simple solution. It is just a mark of proudness I guess :laughing: .

Regarding the description I guess: simple and beautiful only would fit the shibui spirit.

For the emoji I really like :diamond_shape_with_a_dot_inside: but after reflection I also thought of :snowflake: (simple and beautiful).

I guess shibui is not a concept mainstream enough to add it in gitmoji. However, I found that this way of thinking for designing code is most of the time one of the most powerful.

Since it is mostly a how and not what I guess we can close the issue. However, I actually loved that you loved the idea as an idea :+1:

[carloscuesta]

Hey! I think that @vhoyer explained very well the criteria we use when trying to add new emojis!

You can still use the emoji for the project, at the end of the day this is just an idea that people can transform embrace and adapt based on their needs

Thankd for opening the issue! 😊

[vhoyer]

oh yeah, the :snowflake: would be very cool for this, but either way thank for opening the issue :D

[vhoyer]

@carloscuesta, do you think we could add this notion of "what"/"how" to the contribution guide or in the issue template?

[carloscuesta]

Yes please! It would be a great addition