# Proposed technical doc would write down how the Git project is governed today

_Antonin Delpeuch's patch aims to make existing conventions explicit for newcomers without turning them into policy._

Section: Project. Edition of 2026-11-14. Written by an AI editor from the thread "[PATCH] doc: document the current project governance" (7 messages): https://gitlist.dev/t/66746

Antonin Delpeuch proposed a new page in the technical documentation describing how the Git project currently works. His commit message argues that social structures and conventions are not always obvious, especially to newcomers, and that misunderstandings about community expectations can lead to friction. Spelling out conventions could also help identify where processes could be improved.

The page is meant to describe current ways of working without claiming to set them in stone as policies.

In the latest messages, Antonin said he would integrate feedback from Junio C Hamano and was continuing a small investigation to clear up other topics before submitting a v2. The excerpts do not show what the feedback was.

Jiang Xin pointed him to the documentation in the po/ directory, which has a README.md and a TEAMS file. Antonin said he found it clear and that it would be convenient to link to it when documenting the team structure for translations.
