From: Christian Couder <christian.couder@gmail.com>
To: Naomi Ibe <naomi.ibeh69@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Outreachy Internship Project Timeline
Date: Mon, 23 Oct 2023 16:47:49 +0200 [thread overview]
Message-ID: <CAP8UFD2EXVmHb88rch0zsyA0v7vkitYVcONzJzGVc-DAVBvgyA@mail.gmail.com> (raw)
In-Reply-To: <CACS=G2zPH4+R6L8bQ8w=b8u1i6Zsj6xwMibghPKzPX7oGko_tw@mail.gmail.com>
On Sun, Oct 22, 2023 at 7:17 PM Naomi Ibe <naomi.ibeh69@gmail.com> wrote:
>
> On the Outreachy website under the "Final application section", this
> statement appears:
> "Please work with your mentor to provide a timeline of the work you
> plan to accomplish on the project and what tasks you will finish at
> each step. Make sure take into account any time commitments you have
> during the Outreachy internship round. If you are still working on
> your contributions and need more time, you can leave this blank and
> edit your application later."
> Is there a link to where I can access the project timeline and
> subsequently edit it?
We don't provide a timeline. Providing one is part of writing an
application for the project and I am Ok to work with you on your
application by reviewing it.
I recently reviewed Isoken's application, see the thread starting with:
https://lore.kernel.org/git/CAJHH8bEfM8KmwhHX_Fmcb0A2zpr8L75vgNhfvZy-uitpSXNUvQ@mail.gmail.com/
and Luma's application, see the thread starting with:
https://lore.kernel.org/git/CAFR+8Dz717pcc2Lm_J29xxiBt-kUrMP4JAUbm=3XaJuJPYseHg@mail.gmail.com/
Hopefully my comments on these applications can help you get a better
idea of what we would like to see in your application.
See also https://git.github.io/General-Application-Information/,
especially the "Application (required)" section, about what should or
could be in your application.
Best,
Christian.
prev parent reply other threads:[~2023-10-23 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 17:16 Outreachy Internship Project Timeline Naomi Ibe
2023-10-23 14:47 ` Christian Couder [this message]
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=CAP8UFD2EXVmHb88rch0zsyA0v7vkitYVcONzJzGVc-DAVBvgyA@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=naomi.ibeh69@gmail.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 NNTP newsgroup(s).