From: Greg KH <gregkh@linuxfoundation.org>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: Alexey Khoroshilov <khoroshilov@ispras.ru>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
"lsb-discuss@lists.linux-foundation.org"
<lsb-discuss@lists.linux-foundation.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Open Printing <printing-architecture@lists.linux-foundation.org>,
dl9pf@gmx.de
Subject: Re: Google Summer of Code 2018 - Project ideas page for the Linux Foundation online
Date: Sat, 20 Jan 2018 09:40:48 +0100 [thread overview]
Message-ID: <20180120084048.GA24220@kroah.com> (raw)
In-Reply-To: <3d45f9e8-0c83-ae44-855e-e3550cefb5df@gmail.com>
On Thu, Jan 18, 2018 at 10:59:14AM -0200, Till Kamppeter wrote:
> Hi,
>
> I have set up a page for project ideas for the Linux Foundation's
> participation in the Google Summer of Code 2018:
>
> https://wiki.linuxfoundation.org/gsoc/google-summer-code-2018
>
> Please add your ideas to the sub-page of your work group. If you have
> problems mail me with your project idea.
>
> The ideas list is in the Linux Foundation Wiki. If you want to edit, please
> tell me and I give you edit rights.
Looks good to me, thanks!
> Please also take into account that the deadline for our application as
> mentoring organization is Jan 23 and after that Google will evaluate the
> applications. So have your ideas (at least most of them, ideas can be posted
> up to the student application deadline) in by then to raise our chances to
> get accepted.
Are we supposed to sign up as mentors on the GSoC site yet? I tried and
got an error saying "something went wrong".
thanks,
greg k-h
prev parent reply other threads:[~2018-01-20 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 12:59 Google Summer of Code 2018 - Project ideas page for the Linux Foundation online Till Kamppeter
2018-01-18 12:59 ` [Printing-architecture] " Till Kamppeter
2018-01-20 8:40 ` Greg KH [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=20180120084048.GA24220@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dl9pf@gmx.de \
--cc=khoroshilov@ispras.ru \
--cc=linux-wireless@vger.kernel.org \
--cc=lsb-discuss@lists.linux-foundation.org \
--cc=mcgrof@gmail.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=till.kamppeter@gmail.com \
/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.