On Wed, 2015-07-08 at 15:59 -0300, Till Kamppeter wrote:
> 2. Create an organization named OpenPrinting on GitHub and move
> ippusbxd to there. Move also the other projects to there converting
> them to GIT.
One very big advantage of using GitHub is that you get to use tools
like Travis CI/Jenkin
Yes, I will maintain ippusbxd as a separate upstream package, and I will
maintain it in a GIT repository. The only question is how to do it.
There are two possibilities:
1. Create the GIT repo on the OpenPrinting web server, probably the
Linux Foundation has already other problems under GIT. A
On Wed, 2015-07-08 at 08:40 -0400, Ira McDonald wrote:
> Till said that he would move the code to a Git
> repository (I hope this pleases you Tim) and link it off the Open
> Printing website.
That's great news, yes. :-)
Tim.
*/
signature.asc
Description: This is a digitally signed message part
Hi,
When Till and I talked about this on yesterday's OP monthly call,
we concluded that keeping ippusbxd in a separate package was
the best choice. Till said that he would move the code to a Git
repository (I hope this pleases you Tim) and link it off the Open
Printing website.
If anyone objects
Hello,
On Jul 7 12:02 James Cloos wrote (excerpt):
"TK" == Till Kamppeter writes:
TK> I am thinking about joining [ippusbxd] into the cups-filters
TK> upstream package to not have too many tiny packages
...
JC>> licenses are incompatible. (GPL2 vs Apache2).
...
If, after some time, anyon
Le mardi, 7 juillet 2015, 16.33:44 Tim Waugh a écrit :
> On Mon, 2015-07-06 at 22:15 -0300, Till Kamppeter wrote:
> > I am thinking about joining it into the cups-filters upstream
> > package to not have too many tiny packages to make up the complete
> > printing stack and cups-filters contains all
On Mon, 2015-07-06 at 22:15 -0300, Till Kamppeter wrote:
> I am thinking about joining it into the cups-filters upstream package
> to not have too many tiny packages to make up the complete printing
> stack and cups-filters contains all manufacturer-independent software
> for communication with pr
> "JM" == Johannes Meixner writes:
>>> "TK" == Till Kamppeter 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-indepe
Hello,
On Jul 7 08:10 James Cloos wrote (excerpt):
"TK" == Till Kamppeter 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
> "TK" == Till Kamppeter 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 prin
Hello,
On Jul 6 22:15 Till Kamppeter wrote (excerpt):
ippusbxd is a daemon to support IPP-over-USB printing
...
I am thinking about joining it into the cups-filters
upstream package to not have too many tiny packages
to make up the complete printing stack
What would be a real drawback of "m
Hi,
ippusbxd is a daemon to support IPP-over-USB printing, a standard for a
packet-based USB protocol for printers, which especially adds full IPP
and HTTP functionality to a USB-connected, non-networked printer: Web
interface of the printer for configuration (especially also the
printer's Wi
12 matches
Mail list logo
