From: Usman Akinyemi Date: Fri, 10 Oct 2025 06:26:14 GMT Subject: Re: [Outreachy] Introduction (Ágatha) Message-ID: In-Reply-To: On Fri, Oct 10, 2025 at 3:39 AM Agatha wrote: > > Hello! Hello Agatha, > > 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. Nice to hear you are interested in the Git project and hopefully you will regain experience while contributing to the Git project. > > 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. > At Git, you are free to work on anything that interests you. Meanwhile, the Outreachy contribution phase is not that long enough to work on some issues/tasks/projects so, you might want to take that into consideration while picking a microproject to work on. To iterate, the main purpose of Microproject is to get new contributors acquainted with the Git project workflow. [1] gives a good description of our expectation for microproject. [2] Gives the examples of Microproject done by previous contributors. Other important information can be found in [3] and [4]. Just to iterate, you can always work on anything that interests you as a microproject or after the microproject. Most of the selected past interns whether Outreachy and GSoC finds Git interesting and they do send more patches after their microproject. > 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. While I do might not have much information about this, I will allow other contributors to answer it. > > Best, > Ágatha Isabelle [1]: https://git.github.io/General-Microproject-Information/ [2]: https://git.github.io/SoC-2025-Microprojects/ [3]: https://git-scm.com/docs/MyFirstContribution [4]: https://git.github.io/Hacking-Git/