From: Taylor Blau <me@ttaylorr.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
git <git@vger.kernel.org>, Derrick Stolee <stolee@gmail.com>,
Victoria Dye <vdye@github.com>,
Hariom verma <hariom18599@gmail.com>
Subject: Re: GSoC 2023
Date: Tue, 24 Jan 2023 14:18:32 -0500 [thread overview]
Message-ID: <Y9AvCPC4+37XIZug@nand.local> (raw)
In-Reply-To: <CAP8UFD32nDLR8BrhmeTpyraX3QBrc=U1ody+qgyMVY+_-HrASA@mail.gmail.com>
On Tue, Jan 24, 2023 at 05:38:31PM +0100, Christian Couder wrote:
> Actually you were already an Org Admin last year and it looks like
> they didn't remove people from the roles they had last year, so you
> are still an Org Admin.
I think that puts me in the same boat, though I can't remember if I am
actually an org admin or not. If I'm not, and you folks need some extra
help, I'm happy to participate.
I am going to pass on mentoring this year, though. It was a fun
experience for me last time, but took more time than I had planned for.
If someone needs or wants a co-mentor, though, I'm happy to help there
as I think it will end up taking less time.
Thanks,
Taylor
next prev parent reply other threads:[~2023-01-24 19:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 9:34 GSoC 2023 Christian Couder
2023-01-23 17:41 ` Kaartic Sivaraam
2023-01-24 16:38 ` Christian Couder
2023-01-24 19:18 ` Taylor Blau [this message]
2023-02-05 19:50 ` Hariom verma
2023-02-06 17:44 ` Kaartic Sivaraam
2023-02-07 11:58 ` Christian Couder
2023-02-06 16:58 ` Victoria Dye
2023-02-06 17:48 ` Kaartic Sivaraam
2023-02-07 21:04 ` Taylor Blau
2023-03-09 10:17 ` Christian Couder
2023-03-09 17:19 ` Kaartic Sivaraam
2023-03-09 18:45 ` Hariom verma
2023-03-10 0:56 ` Kaartic Sivaraam
2023-03-10 12:38 ` Christian Couder
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=Y9AvCPC4+37XIZug@nand.local \
--to=me@ttaylorr.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=stolee@gmail.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 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.