All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Dan Kohn <dan@dankohn.com>,
	Ira McDonald <blueroofmusic@gmail.com>,
	printing-architecture@lists.freestandards.org
Cc: Amanda McPherson <amanda@linux-foundation.org>
Subject: Re: [Printing-architecture] LinuxPrinting.com naming
Date: Fri, 18 May 2007 16:24:56 +0100	[thread overview]
Message-ID: <464DC548.5080803@gmail.com> (raw)
In-Reply-To: <07616E99-C1A3-4F6D-AD07-E6811D16FE16@dankohn.com>

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>
> 
> 
> 


       reply	other threads:[~2007-05-18 15:24 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 ` Till Kamppeter [this message]
2007-05-18 17:03   ` [Printing-architecture] LinuxPrinting.com naming Ira McDonald
2007-05-22  0:43     ` Norm Jacobs
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=464DC548.5080803@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=amanda@linux-foundation.org \
    --cc=blueroofmusic@gmail.com \
    --cc=dan@dankohn.com \
    --cc=printing-architecture@lists.freestandards.org \
    /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.