All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Daniel Dressler <danieru.dressler@gmail.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] An overview of libjtapi status + "Is anyone interested in an intern?"
Date: Thu, 06 Sep 2012 20:12:20 +0200	[thread overview]
Message-ID: <5048E784.9070300@gmail.com> (raw)
In-Reply-To: <CAGC3nLABhNf0hrZKk_Hs6qZmGQe7t=dE1uH-A-1t0KVB4YtsoQ@mail.gmail.com>

On 09/05/2012 11:13 PM, Daniel Dressler wrote:
> I'm entering my third year of university so next summer will be my
> last. I would like to continue libjtapi, it took 7 years for jtapi to
> get implemented and I fear IPP Everywhere is moving to fast for
> another 7 year wait. By 2019 I expect most people who need jtpai will
> have reinvented the wheel. I also want to have the experience of
> working in an office environment. Thus sometime within a few month
> I'll go through the list of companies contributing to pwg and see if
> any would be interested in having an intern work for them on a pwg job
> ticket backend next summer. I applied for a fall internship with
> Google and got an interview but I'd prefer to be working on libjtapi
> next summer. California sounds nice but I think the world needs
> libjtapi.

I wish you all the best to get an internship where you can continue 
libjtapi, case you will not get one I have already one GSoC student slot 
reserved for you.

    Till



      reply	other threads:[~2012-09-06 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 21:13 [Printing-architecture] An overview of libjtapi status + "Is anyone interested in an intern?" Daniel Dressler
2012-09-06 18:12 ` Till Kamppeter [this message]

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=5048E784.9070300@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=danieru.dressler@gmail.com \
    --cc=printing-architecture@lists.linux-foundation.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.