From: Norm Jacobs <Norm.Jacobs@Sun.COM>
To: Ira McDonald <blueroofmusic@gmail.com>
Cc: printing-architecture@lists.freestandards.org,
Amanda McPherson <amanda@linux-foundation.org>,
Till Kamppeter <till.kamppeter@gmail.com>
Subject: Re: [Printing-architecture] LinuxPrinting.com naming
Date: Mon, 21 May 2007 19:43:26 -0500 [thread overview]
Message-ID: <46523CAE.5000706@Sun.COM> (raw)
In-Reply-To: <e395be80705181003k37564376k2c81119e85e4e293@mail.gmail.com>
Apparently, I missed the context of Dan Kohn's message. What *exacly*
is being proposed here?
-Norm
Ira McDonald wrote:
> Hi,
>
> <OP Chair hat on> There is a very strong negative feeling among many
> of the OP WG chairs whose companies do NOT ship Linux that we should
> keep the name "Open Printing" (which we've always had from the outset
> six years ago), to indicate that the scope is POSIX (not just Linux) for
> our APIs and components.
>
> We can change the name, but it's likely to lose us several working
> group chairs and my immediate predecessor as OP Steering
> Committee chair, Norm Jacobs (Sun Solaris).
>
> Cheers,
> - Ira
>
> On 5/18/07, Till Kamppeter <till.kamppeter@gmail.com> wrote:
>
>> Yes, it has the advantages you mentioned, and the part of the project
>> most known to users had the name linuxprinting.org.
>>
>> Disadvantages are that we are renaming a project again after short time
>> and this means changing back all texts on the site, distros have to
>> rename the packages again, confusing the users, changing names in
>> OpenPrinting APIs (or leaving traces of all project names in the APIs
>> with the time) ...
>>
>> So I want to ask the OpenPrinting workgroup members about whether we
>> should rename or not. Or whether we should agree on the name on the next
>> OpenPrinting Steering Committee meeting. So anyone of the OP folks, WDYT?
>>
>> Till
>>
>>
>> Dan Kohn wrote:
>>
>>> Till, I apologize in advance if you see this request as a reversal.
>>>
>>> Anyway, Amanda and I both think that the LinuxPrinting name is much
>>> stronger and more compelling than OpenPrinting. The term "open" has
>>> been overused so much that it is almost meaningless at this point. I
>>> appreciate that LinuxPrinting provides drivers for BSD, Solaris, OS X,
>>> etc. (and we want it to continue to do so), but just as the Linux
>>> Foundation and Linux Standard Base work on an array of issues but have a
>>> Linux focus at their core, so does LinuxPrinting. Would you be willing
>>> to change the branding of your website and working group?
>>>
>>> - dan
>>> --Dan Kohn <mailto:dan@dankohn.com>
>>> COO, The Linux Foundation <http://www.linux-foundation.org>
>>> <http://www.dankohn.com/> <tel:+1-415-233-1000>
>>>
>>>
>>>
>>>
>>
>
>
>
next prev parent reply other threads:[~2007-05-22 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <07616E99-C1A3-4F6D-AD07-E6811D16FE16@dankohn.com>
2007-05-18 15:24 ` [Printing-architecture] LinuxPrinting.com naming Till Kamppeter
2007-05-18 17:03 ` Ira McDonald
2007-05-22 0:43 ` Norm Jacobs [this message]
2007-05-21 22:14 ` Till Kamppeter
2007-05-22 5:29 ` Jim Zemlin
2007-05-22 15:36 ` Ira McDonald
2007-05-22 2:24 ` Jim Zemlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46523CAE.5000706@Sun.COM \
--to=norm.jacobs@sun.com \
--cc=amanda@linux-foundation.org \
--cc=blueroofmusic@gmail.com \
--cc=printing-architecture@lists.freestandards.org \
--cc=till.kamppeter@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.