From: James Cloos <cloos@jhcloos.com>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>,
Debian-printing@lists.debian.org
Subject: Re: [Printing-architecture] Upstream future of ippusbxd
Date: Tue, 07 Jul 2015 08:10:30 -0400 [thread overview]
Message-ID: <m3egkk5ft5.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <559B2849.7060907@gmail.com> (Till Kamppeter's message of "Mon, 06 Jul 2015 22:15:53 -0300")
>>>>> "TK" == Till Kamppeter <till.kamppeter@gmail.com> writes:
TK> I am thinking about joining [ippusbxd] into the cups-filters
TK> upstream package to not have too many tiny packages to make up the
TK> complete printing stack and cups-filters contains all
TK> manufacturer-independent software for communication with printers
TK> which is not part of CUPS itself.
Be sure, if you do, to note the licensing issues for all of those who
packages cups-filters for distributions.
And also make sure that nothing which derrives from Mike's code ever
inter-links with anythig which derrives from Daniel's, since the
licenses are incompatible. (GPL2 vs Apache2).
(As mentor, I advised Daniel that the licence should be compatible with
cups. He refused.)
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next prev parent reply other threads:[~2015-07-07 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 1:15 [Printing-architecture] Upstream future of ippusbxd Till Kamppeter
2015-07-07 8:47 ` Johannes Meixner
2015-07-07 12:10 ` James Cloos [this message]
2015-07-07 14:16 ` Johannes Meixner
2015-07-07 16:02 ` James Cloos
2015-07-08 9:12 ` Johannes Meixner
2015-07-08 12:40 ` Ira McDonald
2015-07-08 14:10 ` Tim Waugh
2015-07-08 18:59 ` Till Kamppeter
2015-07-13 10:05 ` Tim Waugh
2015-07-07 15:33 ` Tim Waugh
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=m3egkk5ft5.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=Debian-printing@lists.debian.org \
--cc=printing-architecture@lists.linux-foundation.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.