All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Seyi Chamber <kuforiji98@gmail.com>
Cc: Phillip Wood <phillip.wood@dunelm.org.uk>, git@vger.kernel.org
Subject: Re: [Outreachy] Internship Applicant (Contribution Phase)
Date: Thu, 17 Oct 2024 10:53:05 +0200	[thread overview]
Message-ID: <ZxDQX47MuMED_bB6@pks.im> (raw)
In-Reply-To: <CAGedMtcf3TcaZUu3+=Kz-qXAikSjxpi-ULdwyU=Az7pmxyju4g@mail.gmail.com>

Hi,

On Thu, Oct 17, 2024 at 08:27:13AM +0100, Seyi Chamber wrote:
> Hello everyone,

one note up front: we do not top-post on this mailing list. Instead,
responses to a mail should be either inline, quoting the parts that you
directly respond to, or below the quoted mail.

> My name is Seyi Kuforiji, and I am an Outreachy applicant. I have read the
> following documents;
>  - https://git.github.io/General-Microproject-Information/,
>   - https://git.github.io/General-Application-Information/
>   - https://git.github.io/SoC-2024-Microprojects/

Nice to meet you, and thanks for your interest in the Git community!

> I want to get started on modernizing the test script:
> t/t7011-skip-worktree-reading.sh using the specifications discussed on this
> thread:
> https://lore.kernel.org/git/CAPig+cQpUu2UO-+jWn1nTaDykWnxwuEitzVB7PnW2SS_b7V8Hg@mail.gmail.com/
> .
> 
> Before I proceed, is anyone currently working on this test script? Is this
> a good first start, @Patrick Steinhardt <ps@pks.im> and
> @phillip.wood@dunelm.org.uk <phillip.wood@dunelm.org.uk>?

I'm not aware of anybody that'd currently be working on t7011, and
searching our mailing list archive [1] didn't surface any recent mails
that indicate that this is the case. So please, feel free to pick it up
:)

Patrick

[1]: https://lore.kernel.org/git/?q=t7011

> On Wed, 16 Oct 2024 at 09:50, Patrick Steinhardt <ps@pks.im> wrote:
> 
> > On Wed, Oct 16, 2024 at 09:46:04AM +0100, Seyi Chamber wrote:
> > > My Apologies Patrick. There's a second mentor on the Git project
> > > contribution page, I mixed it up :(
> >
> > No worries! I basically assumed that this is what happened, even though
> > I was confused by you mentioning MolEvolvR and not Git ;) For the future
> > it would probably be preferable to send the emails to the both of us via
> > Cc such that we don't answer to you twice. I've done that now.
> >
> > > Yes, I want to contribute to the Git project and would love your input on
> > > how to get started.
> >
> > The first step is to do a microproject in Git to demonstrate your
> > ability to adapt to the workflow of the Git project. You can refer to
> > the following links to learn about how these are supposed to work:
> >
> >   - https://git.github.io/General-Microproject-Information/,
> >   - https://git.github.io/General-Application-Information/
> >   - https://git.github.io/SoC-2024-Microprojects/
> >
> > Let us know in case you have further questions! If so, I'd recommend to
> > also put the Git mailing list into Cc with an "[Outreachy]" tag in your
> > mail's subject so that other people can chime in, as well.
> >
> > Thanks!
> >
> > Patrick
> >
> > > Best Regards,
> > >
> > > Seyi Kuforiji.
> > >
> > > On Wed, 16 Oct 2024 at 09:40, Patrick Steinhardt <ps@pks.im> wrote:
> > >
> > > > On Wed, Oct 16, 2024 at 08:52:24AM +0100, Seyi Chamber wrote:
> > > > > Hi Philip,
> > > > >
> > > > > My name is Seyi Kuforiji. I would love to contribute to MolEvolvR. I
> > am
> > > > > skilled in programming languages like C, Python, and other
> > programming
> > > > > tools.
> > > > >
> > > > > I want to join the public channel for ease of communication and would
> > > > love
> > > > > a pointer on how to get started.
> > > > >
> > > > > Thanks in advance for your help.
> > > >
> > > > I guess there must be some confusion here. I'm neither Philip, nor do I
> > > > know what MolEvolvR is. I _am_ an Outreachy mentor in the Git project
> > > > though, so if that was your goal you've got the right address. :)
> > > >
> > > > Patrick
> > > >
> >

      parent reply	other threads:[~2024-10-17  8:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGedMtfng3eqH7DY=2cnBPdrEWyPpJmEFwW5vBH3ruz=b=ym8w@mail.gmail.com>
     [not found] ` <Zw978QPS0jQMOm6I@pks.im>
     [not found]   ` <CAGedMtfo2RhrPv5BC3ci6tW0XW9ZG73yMD-_sJqe+oR4Gb_dvg@mail.gmail.com>
     [not found]     ` <Zw9-YYpbu9hMQQ7y@pks.im>
2024-10-17  7:39       ` [Outreachy] Internship Applicant (Contribution Phase) Seyi Chamber
     [not found]       ` <CAGedMtcf3TcaZUu3+=Kz-qXAikSjxpi-ULdwyU=Az7pmxyju4g@mail.gmail.com>
2024-10-17  8:53         ` Patrick Steinhardt [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=ZxDQX47MuMED_bB6@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=kuforiji98@gmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    /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.