git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [Outreachy] Introduction (Ágatha)

From
AGAgatha 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

Previous: Usman AkinyemiNext: Christian Couder
Message 7 of 8 in “[Outreachy] Introduction (Ágatha)”
  1. AgathaOct 9, 2025
  2. Immaculate AtimOct 9, 2025
  3. Agatha Isabelle Chris Moreira GuedesOct 9, 2025
  4. Usman AkinyemiOct 10, 2025
  5. Immaculate AtimOct 10, 2025
  6. Usman AkinyemiOct 10, 2025
  7. Agatha Isabelle Chris Moreira GuedesOct 10, 2025
  8. Christian CouderOct 14, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.