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,
	Linux Foundation Staff <lf_staff@lists.linux-foundation.org>,
	Tso Ted <tytso@MIT.EDU>
Subject: Re: [Printing-architecture] [Printing-summit] Google Summer of Code 2008: Application period for mentoring organizations: March 3-12
Date: Fri, 29 Feb 2008 00:35:21 +0100	[thread overview]
Message-ID: <47C74539.90302@gmail.com> (raw)
In-Reply-To: <47C5A86B.2030602@licquia.org>

Jeff Licquia wrote:
> Till Kamppeter wrote:
>> As agreed with Jeff Licquia, the Linux Foundation will enter as one 
>> mentoring organization, with projects from all workgroups, especially 
>> also LSB.
> 
> [...]
> 
>> Should we schedule a conference call about the application for the 
>> Google Summer of Code?
> 
> We probably should. 

I suggest Wed March 5, 9pm CET (3pm Eastern, noon Pacific). This was the 
time when we had regular meetings of the OpenPrinting workgroup.

> As it turns out, it seems likely that OpenPrinting 
> will have far more GSoC projects than LSB will have; there's even the 
> possibility that the LSB will have none.
> 
> So we should decide how we will coordinate the LF GSoC application as a 
> mentoring organization in order to ensure maximum success.

If there is at least one non-OpenPrinting project, the mentoring 
organization will be the Linux Foundation, otherwise it should perhaps 
better be OpenPrinting.

According to our GSoC page

https://www.linux-foundation.org/en/Google_Summer_of_Code

there are non-OpenPrinting projects.

We should also have a look at

http://code.google.com/soc/2008/faqs.html#0.1_org_apply

and answer all these 17 questions in the list, so that we can submit the 
application in time and so that we have good chances to be accepted.

I could do the admin's or backup admin's job as OpenPrinting is one of 
the main contributors of projects. I will also be mentor of some of my 
suggested projects.

We also need to do some more detailed project descriptions to be more 
attractive to students applying for a project.

So let's prepare our application.

    Till

  parent reply	other threads:[~2008-02-28 23:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 15:55 [Printing-architecture] Google Summer of Code 2008: Application period for mentoring organizations: March 3-12 Till Kamppeter
2008-02-27 23:09 ` [Printing-architecture] [Printing-japan] " TORATANI Yasumasa
2008-02-27 23:19   ` Till Kamppeter
     [not found] ` <47C5A86B.2030602@licquia.org>
2008-02-28 23:35   ` Till Kamppeter [this message]
2008-02-28 23:48     ` [Printing-architecture] [Printing-summit] " Till Kamppeter
     [not found]     ` <47C78897.6080307@licquia.org>
2008-02-29 21:19       ` Till Kamppeter
2008-02-29 22:34         ` Ira McDonald

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=47C74539.90302@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=jeff@licquia.org \
    --cc=lf_staff@lists.linux-foundation.org \
    --cc=lsb-discuss@lists.linux-foundation.org \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=tytso@MIT.EDU \
    /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.