<p dir="ltr">Here is the 'flavor' info I mentioned in today's meeting. I don't see any follow ups offhand.</p>
<p dir="ltr">--Pete</p>
<div class="gmail_quote">---------- Forwarded message ----------<br>From: "Matthew Miller" <<a href="mailto:mattdm@fedoraproject.org">mattdm@fedoraproject.org</a>><br>Date: Nov 18, 2014 12:41 PM<br>Subject: fedora cloud/server/workstation terminology request<br>To: <<a href="mailto:marketing@lists.fedoraproject.org">marketing@lists.fedoraproject.org</a>><br>Cc: <br><br type="attribution">Hi everyone. I have a terminology request.<br>
<br>
Red Hat often has to field questions from customers, partners,<br>
analysts, and the public at large about whether Red Hat offers support<br>
for community projects they underwrite, such as Fedora. We in Fedora do<br>
our best to make our community supported model clear to all. [1]<br>
<br>
An important part of Red Hat's way of explaining this is to make a<br>
distinction between "products" — sold and supported — and upstream<br>
*projects*. When we in Fedora talk about "products" for the new,<br>
separate Cloud, Server, and Workstation builds, we're not referring to<br>
something sold and supported. Instead, we mean something focused and<br>
more intentionally planned and targeted than before. We obviously have<br>
no designs on the commercial marketplace. But while *we* know that, Red<br>
Hat's product management (see, there's that word) folks are telling me<br>
that casual use of the word "product" by the Fedora team is really<br>
making their job harder and, more importantly, is confusing the<br>
marketplace. We recognize that a great deal of energy over many years<br>
has gone into distinguishing RH's products from community (including<br>
Fedora) projects. It's not our intention, of course, to undermine that<br>
distinction. As a result, I'd like to ask us all to avoid using the<br>
word "product" in Fedora marketing and communications, such as in the<br>
upcoming F21 GA announcement.<br>
<br>
We're not, by the way, being asked to expunge the word "product" from<br>
our vocabulary in an Orwellian kind of way — it's okay if it comes up<br>
naturally in internal discussion. But it would be helpful if we stay<br>
mindful of the possible confusion such a word creates in communications<br>
outside the project.<br>
<br>
So what should we use instead? I suggest we use the word "flavor" for<br>
our separate builds. This fits nicely in Fedora's (English)<br>
alliterative lexicon. We might also use "variant" or "target" or<br>
"development platform" or whatever where appropriate.<br>
<br>
Translators might (rightly) ask how "flavor" would be translated. The<br>
"flavor" idiom may not make sense in every language in the sense of<br>
food. I suggest in case of difficulties, this be translated in the same<br>
way as the term "flavor" is translated when used in particle physics to<br>
describe categories of the subatomic particles called quarks. This is<br>
the same sense we're using, and these categories also have nothing to<br>
do with flavor as it describes food, so the translation should work<br>
fine.<br>
<br>
<br>
[1] <a href="https://fedoraproject.org/wiki/Communicating_and_getting_help" target="_blank">https://fedoraproject.org/wiki/Communicating_and_getting_help</a><br>
<br>
--<br>
Matthew Miller<br>
<<a href="mailto:mattdm@fedoraproject.org">mattdm@fedoraproject.org</a>><br>
Fedora Project Leader<br>
--<br>
marketing mailing list<br>
<a href="mailto:marketing@lists.fedoraproject.org">marketing@lists.fedoraproject.org</a><br>
List info or to change your subscription:<br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/marketing" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/marketing</a></div>