From: "Pablo Sabater" <pabloosabaterr@gmail.com>
To: "Christian Couder" <christian.couder@gmail.com>,
"git" <git@vger.kernel.org>
Cc: "Git at SFC" <git@sfconservancy.org>,
"Kaartic Sivaraam" <kaartic.sivaraam@gmail.com>,
"Pablo" <pabloosabaterr@gmail.com>,
"Usman Akinyemi" <usmanakinyemi202@gmail.com>,
"Tian Yuchen" <cat@malon.dev>
Subject: Re: Participating in Outreachy's December 2026 cohort
Date: Mon, 14 Sep 2026 09:37:46 +0100 [thread overview]
Message-ID: <DLEWITFIKFFK.NSANTRY5XBCB@gmail.com> (raw)
In-Reply-To: <CAP8UFD1hAjtPuWL8asZ2LzEMJKHGh2oO73n_tsUSADtEHh9b-g@mail.gmail.com>
On Wed Sep 9, 2026 at 10:12 AM WEST, Christian Couder wrote:
> On Sat, Sep 5, 2026 at 10:26 AM Christian Couder
> <christian.couder@gmail.com> wrote:
>
>> Let me know your opinion about these and if you have other project ideas.
>
> As no other project ideas were suggested, I submitted the project
> ideas I mentioned above. You can see them in the "Approved Projects
> for Git" section of the above mentioned page
> (https://www.outreachy.org/communities/cfp/git/) as:
>
> - Improve how command arguments and options are scanned and parsed
> (https://www.outreachy.org/outreachy-dec-2026-internship-cohort/communities/git/#improve-how-command-arguments-and-options-are-scan)
> - Reduce Git’s global state to enable Git's libification
> (https://www.outreachy.org/outreachy-dec-2026-internship-cohort/communities/git/#reduce-gits-global-state-to-enable-gits-libificati)
>
> The links to these projects are currently only available to approved
> mentors and coordinators. I applied to mentor both of these projects
> as this was required to submit the projects, but I am very much
> willing to remove myself from mentoring one of these projects.
>
> So please apply to (co-)mentor one of these projects, or submit other
> projects you are willing to mentor if you prefer.
>
> Also let me know if you see things that could be improved in these
> projects or the Community Application for Git.
>
Hello,
I've applied as co-mentor for the libification one, this way we have at
least one mentor for each project.
Regards,
Pablo
next prev parent reply other threads:[~2026-09-14 8:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 10:55 Participating in Outreachy's December 2026 cohort Christian Couder
2026-08-26 11:39 ` Usman Akinyemi
2026-09-02 13:20 ` Kaartic Sivaraam
2026-09-03 10:24 ` Pablo Sabater
2026-09-05 8:26 ` Christian Couder
2026-09-09 9:12 ` Christian Couder
2026-09-14 6:38 ` Siddharth Asthana
2026-09-14 8:24 ` Kaartic Sivaraam
2026-09-14 8:37 ` Pablo Sabater [this message]
2026-09-14 9:41 ` Kaartic Sivaraam
2026-09-16 20:58 ` Christian Couder
2026-09-17 11:07 ` Kaartic Sivaraam
2026-09-19 13:43 ` Christian Couder
2026-10-05 18:19 ` Pablo Sabater
2026-10-08 13:20 ` Kaartic Sivaraam
2026-10-08 14:05 ` Usman Akinyemi
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=DLEWITFIKFFK.NSANTRY5XBCB@gmail.com \
--to=pabloosabaterr@gmail.com \
--cc=cat@malon.dev \
--cc=christian.couder@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=usmanakinyemi202@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 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.