public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Aveek Basu <basu.aveek@gmail.com>
Subject: Google Summer of Code 2026 - Project ideas page for the Linux Foundation online
Date: Wed, 14 Jan 2026 23:16:13 +0100	[thread overview]
Message-ID: <2ce9b56f-edb0-4c3f-8fdf-251a20f103bf@gmail.com> (raw)

Hi,

the Linux Foundation will apply again as mentoring organization in this year's 
Google Summer of Code.

Perhaps also this year security-related projects and projects about AI/ML are 
especially welcomed by the organizers at Google, like in 2025.

Everything is going as last year, especially allowance of open source newcomers 
and not only students and flexibility with the end of the coding period and the 
3 project sizes, large (350h), medium (175h), and small (90h).

On January 19, 2026 (in 5 days) the application period for mentoring 
organizations for the Google Summer of Code 2025 will start and the deadline 
will be Feb 3.

To be successful, we need a rich project idea list so that we will get selected 
by Google.

I have set up a page for project ideas for the Linux Foundation's participation 
in the Google Summer of Code 2026:

https://wiki.linuxfoundation.org/gsoc/google-summer-code-2026

Please add your ideas to the sub-page of your work group. Also remove project 
ideas which are already done in one of the previous years or not needed any more 
and make sure that all contact info is up-to-date and all links are working.

At each idea please tell for which project size (Large (350h), Medium (175h), 
Small (90h)) it is intended, the level of difficulty (Easy, Intermediate, Hard), 
and mark clearly your security-related and AI/ML-related project ideas (with 
something like "**SECURITY**", "**AI**", "**ML**").

Having security and AI/ML project ideas and also not only large-sized projects 
raises our chances to get accepted.

Make sure to not talk about "students", but about "contributors" instead. I 
have, at least partially, taken care of this when I have copied your sub-group 
pages from last year.

Also make sure to remove the "**TO BE UPDATED**" phrase after having updated 
your project ideas.

If you have problems mail me with your project ideas and other editing wishes.

The ideas list is in the Linux Foundation Wiki. If you want to edit and did not 
have the edit rights already from previous years, please tell me and I give you 
edit rights. I need your name and e-mail address for that. If you have an 
account at the Linux Foundation, use preferably that e-mail address, but having 
an account at the Linux Foundation is not required.

Please also take into account that the deadline for our application as mentoring 
organization is Feb 3 and after that Google will evaluate the applications. So 
have your ideas (at least most of them, ideas can be posted at any time up to 
the contributor application deadline) in by then to raise our chances to get 
accepted.

Please also tell us if you do not want to participate any more with your 
workgroup, so that we can remove your sub-page.

    Till

                 reply	other threads:[~2026-01-14 22:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2ce9b56f-edb0-4c3f-8fdf-251a20f103bf@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=basu.aveek@gmail.com \
    --cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox