All of lore.kernel.org
 help / color / mirror / Atom feed
From: till.kamppeter@gmail.com (Till Kamppeter)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [Printing-architecture] Google Summer of Code 2014 - IPP-over-USB printer support - Joint project idea for OpenPrinting and the kernel
Date: Wed, 26 Feb 2014 18:37:43 +0100	[thread overview]
Message-ID: <530E2667.1080708@gmail.com> (raw)
In-Reply-To: <8E2929D6-4A60-4D27-9012-5250503D9B51@apple.com>

I have posted this project on our project ideas list now:

https://www.linuxfoundation.org/collaborate/workgroups/gsoc/google-summer-code-2014

Feel free to do corrections on the posting.

I have also announced our participation in the GSoC on our front page:

https://www.linuxfoundation.org/collaborate/workgroups/openprinting

   Till

On 02/26/2014 02:56 AM, Michael Sweet wrote:
> Greg,
> 
> On Feb 25, 2014, at 8:47 PM, Greg KH <greg@kroah.com> wrote:
>> ...
>> So you want to do this as a userspace library talking directly to the
>> USB device through usbfs/libusb?  Or should the kernel provide a basic
>> "pipe-like" functionality to the hardware to make it easier for things
>> to be queued up to the device?
> 
> libusb is enough.
> 
>> Is there a pointer to the spec somewhere so that I can see what is
>> needed here?
> 
> http://www.usb.org/developers/devclass_docs
> 
>>>> Second,
>>>> I want to suggest this as a Google Summer of Code project, asking for
>>>> mentors on the kernel side. Mentoring Organization will be the Linux
>>>> Foundation, hosting projects for both OpenPrinting and the kernel.
>>>
>>> This will make an excellent SoC project, but you'll need someone
>>> familiar with Avahi, libusb, HTTP, systemd, and general networking for
>>> this.  This isn't a kernel project.
>>
>> That's a non-trivial set of experience to try to find, good luck :)
> 
> Agreed.
> 
>> And why systemd?  What is needed from it for this?
> 
> Just for the launch-on-demand functionality.  Not absolutely required, but it helps to minimize the overall "weight" of the OS when you aren't printing constantly...
> 
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
> 

WARNING: multiple messages have this Message-ID (diff)
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>, Greg KH <greg@kroah.com>
Cc: "printing-architecture@lists.linux-foundation.org"
	<printing-architecture@lists.linux-foundation.org>,
	Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	kernelnewbies@kernelnewbies.org
Subject: Re: [Printing-architecture] Google Summer of Code 2014 - IPP-over-USB printer support - Joint project idea for OpenPrinting and the kernel
Date: Wed, 26 Feb 2014 18:37:43 +0100	[thread overview]
Message-ID: <530E2667.1080708@gmail.com> (raw)
In-Reply-To: <8E2929D6-4A60-4D27-9012-5250503D9B51@apple.com>

I have posted this project on our project ideas list now:

https://www.linuxfoundation.org/collaborate/workgroups/gsoc/google-summer-code-2014

Feel free to do corrections on the posting.

I have also announced our participation in the GSoC on our front page:

https://www.linuxfoundation.org/collaborate/workgroups/openprinting

   Till

On 02/26/2014 02:56 AM, Michael Sweet wrote:
> Greg,
> 
> On Feb 25, 2014, at 8:47 PM, Greg KH <greg@kroah.com> wrote:
>> ...
>> So you want to do this as a userspace library talking directly to the
>> USB device through usbfs/libusb?  Or should the kernel provide a basic
>> "pipe-like" functionality to the hardware to make it easier for things
>> to be queued up to the device?
> 
> libusb is enough.
> 
>> Is there a pointer to the spec somewhere so that I can see what is
>> needed here?
> 
> http://www.usb.org/developers/devclass_docs
> 
>>>> Second,
>>>> I want to suggest this as a Google Summer of Code project, asking for
>>>> mentors on the kernel side. Mentoring Organization will be the Linux
>>>> Foundation, hosting projects for both OpenPrinting and the kernel.
>>>
>>> This will make an excellent SoC project, but you'll need someone
>>> familiar with Avahi, libusb, HTTP, systemd, and general networking for
>>> this.  This isn't a kernel project.
>>
>> That's a non-trivial set of experience to try to find, good luck :)
> 
> Agreed.
> 
>> And why systemd?  What is needed from it for this?
> 
> Just for the launch-on-demand functionality.  Not absolutely required, but it helps to minimize the overall "weight" of the OS when you aren't printing constantly...
> 
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
> 


  reply	other threads:[~2014-02-26 17:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 17:01 Google Summer of Code 2014 - IPP-over-USB printer support - Joint project idea for OpenPrinting and the kernel Till Kamppeter
2014-02-25 17:01 ` [Printing-architecture] " Till Kamppeter
     [not found] ` <CA+55aFx=5ubeSTcWVcM1bxnjG72fV0vwzTktuqccy1h4-aMScg@mail.gmail.com>
2014-02-25 17:26   ` Till Kamppeter
2014-02-25 17:26     ` [Printing-architecture] " Till Kamppeter
2014-02-25 18:42 ` Michael Sweet
2014-02-25 18:42   ` Michael Sweet
2014-02-26  1:47   ` Greg KH
2014-02-26  1:56     ` Michael Sweet
2014-02-26  1:56       ` Michael Sweet
2014-02-26 17:37       ` Till Kamppeter [this message]
2014-02-26 17:37         ` Till Kamppeter
2014-02-26 23:02       ` Greg KH
2014-02-27  0:05         ` Michael Sweet
2014-02-27  0:05           ` Michael Sweet
2014-02-27  1:35           ` Greg KH
2014-02-27  2:33           ` Carlos Rimola
2014-02-27  2:33             ` Carlos Rimola
2014-02-27 15:37             ` Michael Sweet
2014-02-27 15:37               ` Michael Sweet
2014-02-27 19:23               ` Carlos Rimola
2014-02-27 19:23                 ` Carlos Rimola
2014-02-27 19:29                 ` Michael Sweet
2014-02-27 19:29                   ` Michael Sweet
2014-03-04 22:28                   ` Carlos Rimola
2014-03-04 22:28                     ` Carlos Rimola
2014-03-05  1:00                     ` Michael Sweet
2014-03-05  1:00                       ` Michael Sweet
2014-02-26 22:31 ` Valdis.Kletnieks at vt.edu

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=530E2667.1080708@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.