From: Alison Schofield <alison.schofield@intel.com>
To: Outreachy Linux Kernel <outreachy@lists.linux.dev>
Cc: "Mickaël Salaün" <mic@digikod.net>, "Paul Moore" <paul@paul-moore.com>
Subject: Outreachy - Log your contributions
Date: Tue, 26 Mar 2024 10:37:39 -0700 [thread overview]
Message-ID: <ZgMH4zPt9rHC45Pc@aschofie-mobl2> (raw)
Hi All,
GregKH seems to have caught up on the staging backlog of patches.
I see a bit of disconnect between who is posting patches for
review to this list and what I see in my Outreachy Dashboard
of interested applicants. Please try to sync that up in the
next couple of days.
If you have patches merged by GregKH, please add those to your
Outreachy online application. That is your application expressing
interest in the Landlock project. It does not need to be 'final'
until April 2.
Why it matters to start an application before April 2:
- If we close the project to new applicants, only those who've
started an application can be considered.
- It may help the Landlock mentors tend to their Outreachy applicants
versus other folks interested in contributing to Landlock. (ie. Outreachy
has deadlines)
All contributions are welcomed! I'm just asking for your help in
focusing our attention now through April 2.
Email any questions.
--Alison
reply other threads:[~2024-03-26 17:37 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=ZgMH4zPt9rHC45Pc@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=mic@digikod.net \
--cc=outreachy@lists.linux.dev \
--cc=paul@paul-moore.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 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).