All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Jeff Licquia <jeff@licquia.org>
Cc: printing-architecture@lists.linux-foundation.org,
	lsb-discuss@lists.linux-foundation.org
Subject: [Printing-architecture] Re: [lsb-discuss] Google Summer of Code
Date: Fri, 08 Feb 2008 11:42:10 +0100	[thread overview]
Message-ID: <47AC3202.4040809@gmail.com> (raw)
In-Reply-To: <47A9F3AA.5070106@licquia.org>

I also want to offer some projects for OpenPrinting in the Google Summer 
of Code. How should we proceed here? Should the Linux Foundation be one 
mentoring organization entering the GSoC with both LSB and OpenPrinting 
projects? Or should there be two mentoring organizations, the LSB and 
OpenPrinting? WDYT?

    Till

Jeff Licquia wrote:
> We talked a little bit today on the conference call about whether the 
> LSB should participate in the Google Summer of Code program.  Before we 
> can do that, though, we need projects to propose.
> 
> I've started a project proposal list on the wiki:
> 
> https://www.linux-foundation.org/en/Google_Summer_of_Code
> 
> It's pretty bare-bones at the moment, but feel free to add to it.  Real 
> proposals probably deserve their own page, or may already have their own 
> page; feel free to link to those or create those, or add your own ideas.
> _______________________________________________
> lsb-discuss mailing list
> lsb-discuss@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/lsb-discuss
> 


           reply	other threads:[~2008-02-08 10:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <47A9F3AA.5070106@licquia.org>]

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=47AC3202.4040809@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=jeff@licquia.org \
    --cc=lsb-discuss@lists.linux-foundation.org \
    --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.