## Problem Who doesn't want to use `:tanuki:` within GitLab!? Edit from 2023: :tanuki: :newtanuki: ## Proposal ### Designs Full design in https://gitlab.com/gitlab-org/gitlab/issues/23137 ### Roadmap 1. [ ] Complete [Award emoji cleanup](https://gitlab.com/groups/gitlab-org/-/epics/278) epic 1. [x] Create ~backend and ~GraphQL and REST API endpoints to add and remove custom emojis at the group level. 1. [ ] ~frontend changes so that you can select a custom emoji if at least one exists in the database. If no custom emojis exist, display a message under the `Custom` tab - `You have not created any custom emojis. Add one now (links to page to add/remove)`. We'll like need to inject the custom emojis from the DB into the `emojiCategoryMap`. We should pay close attention that we are making this performant via caching and/or other methods so we aren't making unnecessary DB calls at every render of the emoji picker. * [x] Once we have this, we will upload `:tanuki:` and other custom emoji to GitLab.com so we can try it out. 1. [ ] Implement the ~frontend [interface](https://gitlab.com/gitlab-org/gitlab/issues/23137) via Vue/Apollo to add and remove custom emojis from within a group. All groups and sub-groups share the same common set of custom emojis. A minimum of `Reporter` permissions is required to add or remove emojis. 1. [ ] Blog post to raise awareness and celebrate ### Meeting agenda https://docs.google.com/document/d/1l8e7KDf77-2WWSgjwok17nw_MiPRSqrmyXNkHb5NPjQ/edit (internal only)