[Community] Re: "Op1st" as formal short-hand for "the Operate First project"

+1 on Lars' argument and thinking. I second keep calling it "Operate First" and add qualifiers as need, like "Operate First Community Cloud" On Fri, May 13, 2022 at 7:47 PM Lars Kellogg-Stedman <lars(a)redhat.com&gt; wrote: > On Wed, May 11, 2022 at 06:47:37PM -0700, Karsten Wade wrote: > > Of all the options I've seen — OF, OPF, O1, Op1st — it is "Op1st" that > is > > most distinct and actually reflective of the brand as existing > shorthands > > for "operation/operate" and "first". > > I've always felt that "Op1st" is clunky. The correct pronunciation > doesn't really follow from the spelling if you're not already familiar > with Operate First. It looks like a clever numeric contraction -- like > "i18n" or "l10n", but it isn't. > > If I wanted a shorthand for referring to Operate First, I would go > with either "opf" (because that's already in wide use through our own > configuration and documentation), or possibly "O1" as a distant > second. > > If I were looking to differentiate "operate first", the concept, vs > "operate first", a particular implementation of that concept: I guess > I would follow the example that's already been given for Fedora, and > just keep calling things "operate first", adding qualifiers as > necessary ("operate first cluster", etc). Spelling it "Op1st" and > still pronouncing it "operate first" doesn't seem to do anything but > sew confusion and practically we end up in the same place. > > -- > Lars Kellogg-Stedman <lars(a)redhat.com&gt; | larsks @ {irc,twitter,github} > http://blog.oddbit.com/ | N1LKS > _______________________________________________ > Community mailing list -- community(a)lists.operate-first.cloud > To unsubscribe send an email to community-leave(a)lists.operate-first.cloud > _______________________________________________ Community mailing list -- community(a)lists.operate-first.cloud To unsubscribe send an email to community-leave(a)lists.operate-first.cloud