Prototype maintainers file

[TrueDoctor]

Adds a MAINTAINERS file which serves as an map to figure out who is responsible for which part of the codebase

[gemini-code-assist]

Summary of Changes

Hello @TrueDoctor, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a foundational MAINTAINERS file to the repository. Its primary purpose is to establish clear ownership and contact information for key contributors, as well as to delineate responsibilities for different sections of the codebase. This will help streamline communication, clarify who to contact for specific areas, and improve overall project organization and maintainability.

Highlights

• Introduction of MAINTAINERS file: A new MAINTAINERS file has been added to the repository. This file clearly lists individual maintainers with their Discord, GitHub, and email contacts.
• Defined Ownership for Codebase Sections: The MAINTAINERS file also outlines specific maintainers for various folders and subsystems within the project, such as 'Frontend Code', 'Libraries', 'Editor', 'Node Graph', and 'Tooling', providing a clear structure for code ownership.

Changelog

• MAINTAINERS
  • Added a new file to define project maintainers and their contact information.
  • Included a section mapping specific codebase folders and subsystems to their respective maintainers.

Activity

• No activity has been recorded on this pull request yet, as it has just been opened.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a MAINTAINERS file to document code ownership, which is a helpful addition. My review has identified a critical issue with incorrect contact information that needs to be fixed. I've also pointed out several formatting inconsistencies and a typo that should be addressed to improve the file's readability and correctness. Additionally, please note that the pull request description template has not been filled out; please provide a description of the changes as requested by the contribution guidelines.