From: Julia Lawall <julia.lawall@inria.fr>
To: outreachy@lists.linux.dev
Subject: [outreachy] applications
Date: Sun, 29 Oct 2023 12:23:03 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2310291216100.3136@hadrien> (raw)
Hello,
I got a question about recording non-patch contributions in the
application.
First, you must have at least one patch accepted into the Linux kernel to
be considered for an internship. You will naturally have a URL that goes
with that. Please make a separate contribution for each one of your
patches, so we can get a quick idea of how much experience each applicant
has with submitting patches to the Linux kernel and getting them accepted.
Afterwards, some projects may ask for small tasks that don't directly lead
to a patch. These would be submitted to the mentors, not necessarily to
the mailing list or the Linux kernel. If you don't see a useful way to
obtain a URL for these contributions, there should be a box for providing
additional information, and you can use that box for describing what you
have done.
Let me know if you have any questions. Remember that the applications are
due tomorrow. Check carefully on the time, especially if you live in a
place where the time changed this weekend.
The deadline is Oct. 30, 2023 at 4pm UTC.
julia
reply other threads:[~2023-10-29 11:23 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=alpine.DEB.2.22.394.2310291216100.3136@hadrien \
--to=julia.lawall@inria.fr \
--cc=outreachy@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).