<table><tr><td style="">ngraham added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D25278">View Revision</a></tr></table><br /><div><div><p>This isn't random; Baloo is a brand name with a logo in progress (<a href="https://phabricator.kde.org/D24957" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D24957</a>). We have a HIG page about this: <a href="https://hig.kde.org/style/writing/brandnames.html" class="remarkup-link" target="_blank" rel="noreferrer">https://hig.kde.org/style/writing/brandnames.html</a>. Baloo is even mentioned there as an example of a brand name. :)</p>
<p>the TL;DR version is that if we give something a catchy codename that we use to refer to it--especially in communication with users in the form of bug reports, release announcements, and social media comments and postings--we need to accept that it's a brand name and then surface it in the UI so that users can learn it. We already did this for KRunner in Plasma 5.17 (previous it was referred to with the nondescript and non-promo-friendly term "Plasma Search") and nobody complained to my knowledge.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R119 Plasma Desktop</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D25278">https://phabricator.kde.org/D25278</a></div></div><br /><div><strong>To: </strong>ngraham, VDG<br /><strong>Cc: </strong>davidedmundson, plasma-devel, LeGast00n, The-Feren-OS-Dev, jraleigh, fbampaloukas, GB_2, ragreen, ZrenBot, ngraham, alexeymin, himcesjf, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart<br /></div>