Taylor Blau shared the notes, also kept in a Google Doc, so that people who could not attend can catch up and continue the discussion on the list. Topics include the security mailing list and process, Git 3.0, documentation, Outreachy sponsorship, what to do next with the pluggable object database, an AI contribution policy, and protocol v2 for pushes.

Emily Shaffer followed with a patch adding a document on how the project makes decisions by vote when community consensus cannot settle a question. Her cover letter says the Summit showed interest in a formal community vote on whether and how to accept AI contributions, a topic she calls very contentious.

Junio C Hamano welcomed the document. He liked that it keeps technical decisions from being put to a vote and reserves voting for policy decisions. He suggested that proposals be uniquely identifiable by commit or blob ID so people can fetch the exact text. He also asked for a stronger verb than 'propose' in the patch title, since once merged the document defines the process rather than proposing it.

Shaffer listed options for running a vote. Debian's devotee appears to require hosting, and neutral hosting may be hard to find. The Linux Foundation's Technical Advisory Board has used CIVS, which uses the same tallying algorithm. jj has used a GitHub poll, which gives only simple majority and requires GitHub accounts. She said devotee and CIVS look better suited to many options.

The process document and the tool choice are still under discussion, and no vote has been scheduled in the excerpts.