Re: [Outreachy] Introduction (Ágatha)
- From
- Agatha Isabelle Chris Moreira Guedes <code@agatha.dev>
- Date
- Oct 10, 2025, 13:38 UTC
- Message-ID
- <lmg2pwd6yf5ukrjl3mtwdwih7lcywpapmey3gp6m544hx4ctab@6xw2nsncyjcw>
- In-Reply-To
- <CAPSxiM9yejQNQtw22Q=s1PrG-vUGBX5DiNQZMvyHACcXVfOtfw@mail.gmail.com>
On Fri, Oct 10, 2025 at 11:56:14AM +0530, Usman Akinyemi wrote:
> On Fri, Oct 10, 2025 at 3:39 AM Agatha <code@agatha.dev> wrote: > > > > Hello! > Hello Agatha,
Thanks for replying, Usman!
Show 28 quoted lines
> > > > 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.
Show 13 quoted lines
> 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