workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: workflows@vger.kernel.org
Cc: Till Kamppeter <till.kamppeter@gmail.com>,
	Aveek Basu <basu.aveek@gmail.com>
Subject: Explore ideas on workflows improvements with Google Summer of Code mentoring program?
Date: Tue, 14 Jan 2020 19:07:12 +0100	[thread overview]
Message-ID: <CAKXUXMy3_4vBeVS42c4AGYVNHzcP2iO0FxWN6MnncT0uc_ZKKw@mail.gmail.com> (raw)

Dear all,

Till Kamppeter and Aveek Basu organize the Google Summer of Code
student mentoring program in the name of the Linux Foundation. They
have set up a page for project ideas for the Linux Foundation's
participation in the linuxfoundation wiki:

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

I believe many ideas discussed here on this list, e.g., extensions to
patchwork, public-inbox, further bots, scripts, etc., are well suited
to be prototyped or implemented by students in the GSoC program.

If you agree and have some good ideas, please add your ideas to this
currently still empty draft page:

https://wiki.linuxfoundation.org/gsoc/2020-gsoc-kernel-workflows

Ideas should be roughly described in five to six sentences, possibly
with a list of expectations on required knowledge a student should
show for its application. Within the application period later,
interested students have to write a much more extensive project
proposal as part of their application, by exchanging with the group to
refine the rough idea to a proper task and student project.

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

If you have any questions concerning GSoC organisation, you can reach
out to Till, Aveek or me.

Best regards,

Lukas

             reply	other threads:[~2020-01-14 19:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 18:07 Lukas Bulwahn [this message]
2020-01-15 22:07 ` Explore ideas on workflows improvements with Google Summer of Code mentoring program? Michael Turquette
2020-01-15 23:03   ` Bjorn Helgaas
2020-01-16 19:39     ` Michael Turquette
2020-01-17  1:34     ` Stephen Boyd
2020-01-16  0:59   ` Daniel Axtens
2020-01-16 19:35     ` Michael Turquette
2020-01-17  2:19       ` Daniel Axtens
2020-01-17 20:25   ` Lukas Bulwahn
2020-01-17 20:38     ` Michael Turquette
2020-01-18  7:18       ` Lukas Bulwahn
2020-01-21 22:14         ` Michael Turquette
2020-01-22  6:18           ` Lukas Bulwahn
2020-01-22 22:22             ` Michael Turquette

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=CAKXUXMy3_4vBeVS42c4AGYVNHzcP2iO0FxWN6MnncT0uc_ZKKw@mail.gmail.com \
    --to=lukas.bulwahn@gmail.com \
    --cc=basu.aveek@gmail.com \
    --cc=till.kamppeter@gmail.com \
    --cc=workflows@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;
as well as URLs for NNTP newsgroup(s).