All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: htl10@users.sourceforge.net,
	"printing-architecture@lists.linux-foundation.org"
	<printing-architecture@lists.linux-foundation.org>,
	Printing-japan <printing-japan@lists.linux-foundation.org>,
	"printing-summit@lists.linux-foundation.org"
	<printing-summit@lists.linux-foundation.org>,
	Ira McDonald <blueroofmusic@gmail.com>
Subject: Re: [Printing-architecture] GSoC, & printing & not-so-printing projects.
Date: Thu, 06 Feb 2014 17:10:45 +0100	[thread overview]
Message-ID: <52F3B405.4040203@gmail.com> (raw)
In-Reply-To: <1391601767.6086.YahooMailBasic@web172303.mail.ir2.yahoo.com>

Hin-Tak, I have put up the ideas list for OpenPrinting now. please 
update the ddiwrapper project appropriately.

    Till

On 05.02.2014 13:02, Hin-Tak Leung wrote:
> Hi Till,
>
> GSoC application for organizations has just started. I assume you'll put in an application
> again as per usual?
>
> I have mentioned once or twice before that ddiwrapper (using wine + extra bits to run
> windows printer drivers) is due for an update from recent DIB developments; also there
> are newer windows (8!) as well as 64-bit windows become common
> since what was 32-bit XP/2000 era technology. One other interesting recent
> development is http://www.darlinghq.org/ - which probaby means using Mac OS X printer
> drivers might be a possibility - so I think you could update the project descriptions, etc a bit.
>
> Also, one very important thing - I don't read e-mails to my gmail account often
> (mostly for automating patch submissions, etc!), and contact should always be
> the sourceforge address, and *most important*, all GSoC or not-GSoC-related queries
> *must* CC one of the mailing lists. I cannot emphasize this often enough.
>
> Just co-incidentally, these last few weeks saw an alternative HFS+ (i.e. Mac OS X file system,
> important for dual booting linux+OSX) journalling implementation
> emerging - and it just landed in Andrew Morton's tree. - That was the failed GSoC
> project I took on two years ago. I have had some discussion on kernel fs-devel
> about adapting actual Apple code via fuse - linux's file-system-in-userand - for
> inter-operability. So that's another not-printing GSoC project one might advertise on.
>
> Hin-Tak
>
>


      parent reply	other threads:[~2014-02-06 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1391601767.6086.YahooMailBasic@web172303.mail.ir2.yahoo.com>
2014-02-06 11:00 ` [Printing-architecture] GSoC, & printing & not-so-printing projects Till Kamppeter
2014-02-06 16:10 ` 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=52F3B405.4040203@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=blueroofmusic@gmail.com \
    --cc=htl10@users.sourceforge.net \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=printing-japan@lists.linux-foundation.org \
    --cc=printing-summit@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.