From: Mark Heim <questioneight@gmail.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: outreachy@lists.linux.dev
Subject: Re: [Outreachy Info] Ask for help finding cleanups
Date: Wed, 15 Mar 2023 01:44:10 -0600 [thread overview]
Message-ID: <20230315074410.GB224213@gmail.com> (raw)
In-Reply-To: <ZBEIAKymniRkamjr@aschofie-mobl2>
On Tue, Mar 14, 2023 at 04:49:20PM -0700, Alison Schofield wrote:
> Hi Applicants,
>
> We want to support you finding cleanups. Today I spent some time
> looking through staging and am working up a small todo list that
> may be useful.
I'm interested in doing the required demo for the kernel. Let
me know what I should do next presupposing there is a list of tasks.
>
> I posted one such cleanup to Menna because I saw them submit a
> couple of attempts at a first patches.
>
> I think that Kloudifold, Khadija, and Sumitra are busy iterating on
> their first patches. Keep going! Ask for help finding your second
> patch if needed.
>
> Anyone else who wants help in finding their first patch, please reach
> out. I imagine their are some folks exploring here, that I haven't
> met on the list yet.
Hello, that's me! I was originally working on the Outreachy LLVM
project but had short term health problems, and that meant I let
that opportunity get away.
>
> Finally, it seems we won't be holding to the traditional 10 cleanup
> patch requirement this round! Please continue your efforts and I'll
> redirect you towards projects after a 'few' cleanup patches are
> accepted into staging.
>
I have some catching up to do. I dug through a little more
than a page of Linux mailing list messages but was able to
glean a bunch of things that were helpful. These are things like
patch creation best practices, posting on code style, joining
a mailing list, and documentation.
Hope to hear from everyone later.
(here's a question: is it best practice to include 100 percent
of the message pre-insertion of comments, or can I delete some
of the original message?)
> Thanks,
> Alison
>
>
>
next prev parent reply other threads:[~2023-03-15 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 23:49 [Outreachy Info] Ask for help finding cleanups Alison Schofield
2023-03-15 7:44 ` Mark Heim [this message]
2023-03-15 18:12 ` Alison Schofield
[not found] ` <CALfc2nhr7fWD33T5000kJt9stcgQ3fJM8YNTQhRgozxFYDxyYw@mail.gmail.com>
2023-03-16 14:53 ` Alison Schofield
[not found] ` <CALfc2nioOy+T7GyV==Akr5WY5gC_awadai77k4tqr-NGNhaR+A@mail.gmail.com>
2023-03-17 1:51 ` Alison Schofield
2023-03-15 9:10 ` Menna Mahmoud
2023-03-15 9:19 ` Julia Lawall
2023-03-15 9:25 ` Menna Mahmoud
[not found] ` <CAOHb_39SAEOwJOCNqsvND5w81MbAHLROf+sRAu0AWi911teidA@mail.gmail.com>
2023-03-15 16:19 ` Alison Schofield
2023-03-16 13:16 ` Sumitra Sharma
2023-03-16 15:07 ` Alison Schofield
2023-03-16 15:27 ` Sumitra Sharma
2023-03-16 15:41 ` Fabio M. De Francesco
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=20230315074410.GB224213@gmail.com \
--to=questioneight@gmail.com \
--cc=alison.schofield@intel.com \
--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 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.