# [Outreachy] Introduction (Ágatha) 8 messages from 2025-10-09 to 2025-10-14. Participants: Agatha, Immaculate Atim, Agatha Isabelle Chris Moreira Guedes, Usman Akinyemi, Christian Couder. Thread: https://gitlist.dev/t/64288 ## Agatha, 2025-10-09 22:09 Subject: [Outreachy] Introduction (Ágatha) Message-ID: URL: https://gitlist.dev/e/qbehd3whkgrofsmvkrtgbfo3tiqhyv3friz56xrehkgduld3ou%40e4ck6nfloaq3 ``` 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 ``` ## Immaculate Atim, 2025-10-09 23:35 Subject: Re: [Outreachy] Introduction (Ágatha) Message-ID: URL: https://gitlist.dev/e/CAJXmEzTVJiDLe_9gv-6MkNcztAezQJob90S%3DHW7r_AkVZUMukA%40mail.gmail.com In-Reply-To: ``` Hello Agatha, Welcome here. Please feel free to reachout to this mailing list or the mentors in case you get challenges while working on your micro project. Best regards, On Fri, Oct 10, 2025 at 1:15 AM Agatha wrote: > > 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 > -- Immaculate! ``` ## Agatha Isabelle Chris Moreira Guedes, 2025-10-09 23:59 Subject: Re: [Outreachy] Introduction (Ágatha) Message-ID: URL: https://gitlist.dev/e/iob5tcve2ca2v6424l7cxszvsxktkze2mumhdaqzb5ifp4sn7f%40u6bslll7szla In-Reply-To: ``` Hello, Immaculate! On Fri, Oct 10, 2025 at 02:35:42AM +0300, Immaculate Atim wrote: > Hello Agatha, > > Welcome here. Please feel free to reachout to this mailing list or the > mentors in case you get challenges while working on your micro > project. Thanks a lot! ``` ## Usman Akinyemi, 2025-10-10 06:26 Subject: Re: [Outreachy] Introduction (Ágatha) Message-ID: URL: https://gitlist.dev/e/CAPSxiM9yejQNQtw22Q%3Ds1PrG-vUGBX5DiNQZMvyHACcXVfOtfw%40mail.gmail.com 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/ ``` ## Usman Akinyemi, 2025-10-10 06:31 Subject: Re: [Outreachy] Introduction (Ágatha) Message-ID: URL: https://gitlist.dev/e/CAPSxiM_nkXDaieL%2B2oq9%3DKqG9eMkKjMhHzQz7SzEQ96bN%3Dq%3Dvw%40mail.gmail.com In-Reply-To: ``` On Fri, Oct 10, 2025 at 5:05 AM Immaculate Atim wrote: > Hi Immaculate, > Hello Agatha, > > Welcome here. Please feel free to reachout to this mailing list or the > mentors in case you get challenges while working on your micro > project. Thanks for this. Importantly and I hope other contributors can see this, We do not "top post" when replying to email in Git. You can find more information about this in [1]. Thank you. [1]: https://git.github.io/General-Microproject-Information/ > ``` ## Immaculate Atim, 2025-10-10 09:21 Subject: Re: [Outreachy] Introduction (Ágatha) Message-ID: URL: https://gitlist.dev/e/CAJXmEzQERNzSdW1kBaZiFi35NuA28jDtB5CEhQEm6csnCBn-%3DA%40mail.gmail.com In-Reply-To: ``` On Fri, Oct 10, 2025 at 9:31 AM Usman Akinyemi wrote: > > On Fri, Oct 10, 2025 at 5:05 AM Immaculate Atim > wrote: > > > Hi Immaculate, > > Hello Agatha, > > > > Welcome here. Please feel free to reachout to this mailing list or the > > mentors in case you get challenges while working on your micro > > project. > Thanks for this. > > Importantly and I hope other contributors can see this, > We do not "top post" when replying to email in Git. You can find more > information about this in [1]. > > Thank you. > [1]: https://git.github.io/General-Microproject-Information/ > > Thanks for the clarification, Usman! I’ve read through the link you shared and I have learned more. I’ll make sure to follow this format in all my future mailing list messages. Best, -- Immaculate! ``` ## Agatha Isabelle Chris Moreira Guedes, 2025-10-10 13:38 Subject: Re: [Outreachy] Introduction (Ágatha) Message-ID: URL: https://gitlist.dev/e/lmg2pwd6yf5ukrjl3mtwdwih7lcywpapmey3gp6m544hx4ctab%406xw2nsncyjcw In-Reply-To: ``` On Fri, Oct 10, 2025 at 11:56:14AM +0530, Usman Akinyemi wrote: > On Fri, Oct 10, 2025 at 3:39 AM Agatha wrote: > > > > Hello! > Hello Agatha, Thanks for replying, Usman! > > > > 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. > Alright then, while I would like a lot to work on that I'll hold on for now. > 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 will. First will do a microproject from the list, then, and later will try to work on that. I thought the list from GSoC was possibly outdated so didn't give a look, but I see now that the suggestions are generic enough and likely apply to several cases. Best, Ágatha Isabelle ``` ## Christian Couder, 2025-10-14 09:14 Subject: Re: [Outreachy] Introduction (Ágatha) Message-ID: URL: https://gitlist.dev/e/CAP8UFD136SoQn-Tip_MQ4zxfs5a060MTOU_Hgj34ppjes%2BRogw%40mail.gmail.com In-Reply-To: ``` Hi Agatha, On Fri, Oct 10, 2025 at 12:09 AM Agatha wrote: > 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. One recent related discussion was about the following commit: 1f0fed312a (SubmittingPatches: allow non-real name contributions, 2025-07-16) (See https://lore.kernel.org/git/20250706163009.335780-1-sandals@crustytoothpaste.net/#r) I think there were previous related discussions about the mailmap file, but I don't remember about any specific one. Thanks for your interest in contributing to Git. ```