From: Agatha <code@agatha.dev>
Date: Thu, 09 Oct 2025 22:09:54 GMT
Subject: [Outreachy] Introduction (Ágatha)
Message-ID: <qbehd3whkgrofsmvkrtgbfo3tiqhyv3friz56xrehkgduld3ou@e4ck6nfloaq3>

Hello!

My name is Ágatha Isabelle (pronouns she/her) and I'm (yet another)
outreachy applicant for this cohort. I have some experience with C,
developing mostly device drivers, a couple of patches in the mainline
linux kernel, etc. I also do some assembly (x86/x64 & riscv a little)
and C++. My goal at outreachy is to regain experience to work in
software development again after some personal setbacks took me out for
some years, while also contributing to an interesting open source
software project like git.

I'm looking forward to interacting with the git community once again
within the next few weeks during the application period.

Currently I'm looking through the documentation to get a better grasp of
what is expected of us during this period. The doc says I'm supposed to
send an introduction e-mail, so here I am. But I don't want to just do
that, I would like to let you know I'm also working on choosing a
microproject -- right now I am exploring some intersections between
git's object model where objects are immutable and tightly linked to
author metadata, and possible privacy concerns. Especially for people
who would like to exercise their right to be forgotten and transgender
individuals who might fear former name exposure in places where this
information is protected by laws, tackling cases where a simple mailmap
entry won't be enough and rewriting history would be way too disruptive.

I want to see if I can work on a microproject that helps to tackle those
privacy concerns while keeping objects immutable and preserving git's
design principles. As it's supposed to be a "micro" project, I plan to
explore a small, concrete first step rather than attempting a full
solution. Yet I would appreciate any input on that. I have a couple of
ideas in mind to check if they are applicable too.

I think this would be of actual significance for several groups of
individuals, especially for transgender software developers who face a
lot of challenges to get in the tech industry, even when they have years
of experience. While in some places linking their current names to their
former names might even be dangerous, or at least lead to embarrassment,
losing credit for their contributions to avoid exposing deadnames could
also be a limiting factor towards obtaining employment in tech.

I’d be happy to discuss whether similar ideas have been explored before,
or hear pointers to related prior discussions.

Best,
Ágatha Isabelle