--===============8302197403034692680== Content-Type: multipart/signed; boundary="nextPart14982247.aKFYDgW0P1"; micalg="pgp-sha1"; protocol="application/pgp-signature" --nextPart14982247.aKFYDgW0P1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" On Tuesday, February 18, 2014 14:54:04 you wrote: > On Tuesday 18 February 2014 14:30:13 Aaron J. Seigo wrote: > I'm about half-way there with you. I agree with the principle, but as= with > artwork (where developers still have plenty of say) I think this shou= ld be > in both hands at once. I agree. With artwork, it is usually a consultation type relationship. = The=20 artist works with the developers, but retains direction and decision ma= king.=20 > Which puts (as you rightly do) the blame as much on us as anyone - we= should > step up more, as marketing/promo people, when it comes to branding. More than just =E2=80=9Cstepping up=E2=80=9D, a mandate from the develo= pment community to=20 manage these things is needed, and a group needs to take on that commit= ment=20 and execute over the long term. =E2=80=9CStepping up=E2=80=9D is not go= ing to produce=20 consistent results, as seen in this case. > So yes, perhaps we should have said to Vishesh that Baloo is not a pe= rfect > name. I did, and explained why, on a public mailing list. That was ignored. P= erhaps=20 I=E2=80=99m not part of the =E2=80=9Cwe=E2=80=9D around these parts any= more, but it was pointed out. Developer have the understanding that branding is ultimately a decisio= n made=20 at their sole discretion, even when it impacts others. > Meanwhile, I didn't think of anything horrible and still don't feel i= t is > that bad *and* it seems nobody has hammered on this point yet - I sug= gest we > stick with it. The name itself is not objectively bad, and that has never been the iss= ue. The=20 issue is *changing* a name that already exists and for which quite a bi= t of=20 effort has been put into. It exists on wikis such as Userbase and Techb= ase, in=20 configuration UI (though that has been pushed back to a minimum, more o= r less),=20 etc. The lack of continuity not only throws confusion into the air, it = removes=20 what is probably the most obvious and easiest public communications pat= h:=20 =E2=80=9Cversion 2 addresses the prior version=E2=80=99s challenges whi= le retaining its=20 benefits=E2=80=9D. Now there is the more complex task of explaining wha= t Baloo does,=20 what it does differently from Nepomuk, why this necessitated such a big= change=20 ... iow we=E2=80=99re going to be faced with discussion revolving aroun= d=20 implementation details rather than being able to focus purely of user b= enefit=20 stories. > Besides, in our communication we should indeed call it > 'search' or 'semantic search' and nothing else anyway. Agreed ... which is also why introducing a new name publicly is not a g= reat=20 idea: it makes accomplishing this more difficult. --=20 Aaron J. Seigo --nextPart14982247.aKFYDgW0P1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEABECAAYFAlMDawAACgkQ1rcusafx20OikQCggwxKNoK591CT2bIO4q97O6By 3X0An25wH6j4jkKOlAcrJE9URZE2aE+U =wH2r -----END PGP SIGNATURE----- --nextPart14982247.aKFYDgW0P1-- --===============8302197403034692680== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ This message is from the kde-promo mailing list. Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription. --===============8302197403034692680==--