From: Christian Couder <christian.couder@gmail.com>
To: Taylor Blau <me@ttaylorr.com>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: git@vger.kernel.org, Hariom verma <hariom18599@gmail.com>,
Victoria Dye <vdye@github.com>
Subject: Re: Git in Outreachy? (December, 2023)
Date: Tue, 29 Aug 2023 22:38:45 +0200 [thread overview]
Message-ID: <CAP8UFD2CGf8efBHquS=LJP8uQ5ivuDryqGz96PZ81oDtrNgNXw@mail.gmail.com> (raw)
In-Reply-To: <ZO4wxU1ilpa6/3EW@nand.local>
On Tue, Aug 29, 2023 at 7:54 PM Taylor Blau <me@ttaylorr.com> wrote:
>
> On Tue, Aug 29, 2023 at 11:14:38PM +0530, Kaartic Sivaraam wrote:
> > BTW, I think the deadline to sign up for Outreachy is approaching soon I
> > believe. The community page [1] seems to indicate that we haven't signed up
> > yet. Given that there was an interest in us participating in Outreachy, I
> > just wanted to check whether we've signed up our community ?
>
> Indeed. I was waiting to see if interested parties had the resources to
> sponsor an Outreachy student, since we have to pay Outreachy for each
> student we accept.
It will take some time before I can confirm whether or not GitLab is
willing to sponsor one Outreachy intern.
> If you (or others) are interested in mentoring but don't have a way to
> pay Outreachy, we could certainly discuss allocating some of the
> project's funds to support one or two students.
I clicked on the "Community will participate" button, but this leads
to a page saying "Outreachy internship funding is required" and where
we have to list the sponsors we have, the amount of funds they are
willing to sponsor, if the funding is secured and the funding decision
date. I think I will fill this out saying that we have 3 (potential)
sponsors: the Git project, GitHub and GitLab. I will not check the
"funding is secured" checkbox and say that the decision date is
October 5 (so just one day before the deadline for "Project list
finalized"). This will leave time to find out if we can indeed sponsor
at least one intern.
Let me know if that works for both of you.
By the way, Kaartic, do you still want to be an org admin? And Taylor
are you Ok with Kaartic being an org admin?
It seems that I received an email asking me to confirm Kaartic as an
org admin, but I couldn't confirm then and later when clicked to the
link to confirm it looked like it wasn't possible anymore to confirm
that. So not sure what happened, but maybe we could try again to
register you as an org admin.
Best,
Christian.
next prev parent reply other threads:[~2023-08-29 20:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 1:07 Git in Outreachy? (December, 2023) Taylor Blau
2023-08-18 15:10 ` Christian Couder
2023-08-18 15:17 ` Taylor Blau
2023-08-22 6:14 ` Kaartic Sivaraam
2023-08-23 18:40 ` Taylor Blau
2023-08-29 17:44 ` Kaartic Sivaraam
2023-08-29 17:54 ` Taylor Blau
2023-08-29 20:38 ` Christian Couder [this message]
2023-09-02 6:06 ` Kaartic Sivaraam
2023-09-21 20:46 ` Taylor Blau
2023-09-22 6:19 ` Christian Couder
2023-10-29 18:23 ` Kaartic Sivaraam
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='CAP8UFD2CGf8efBHquS=LJP8uQ5ivuDryqGz96PZ81oDtrNgNXw@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=me@ttaylorr.com \
--cc=vdye@github.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).