Skip to content

Conversation

@Ivorforce
Copy link
Member

@Ivorforce Ivorforce commented Nov 7, 2025

An update over the current teams page (https://godotengine.org/teams/).

Adds the current maintainers to each team.

SCR-20251107-pgwd

My workflow was the following:

Hopefully, we'll be able to keep this list updated, since it would basically just mean going through the GH teams again.

Notes

I've omitted the handle links (see current page) on purpose. We don't want people to write individual people when they need something from a team, we want them to write the team via the listed communication channels. Linking the handles might send the wrong message.

I've also omitted team leads, since I have no up-to-date reference for who's team lead of what. I'll have to query that in a follow-up.

I've also left some comments in the page in hopes that it will keep some order in the page going forwards.

The only team where i've yet omitted some people is bugsquad, since it has some people who aren't maintainers. I'm open to suggestions on that front (for example, we could call it "Members" there instead?).

@Ivorforce Ivorforce requested review from a team and AThousandShips November 7, 2025 16:28
@Ivorforce Ivorforce added the enhancement New feature or request label Nov 7, 2025
@Mickeon
Copy link
Member

Mickeon commented Nov 7, 2025

One "problem" with the current PR is that team leaders are entirely undocumented here. I'm not sure what the consensus on that was.

Linking the handles might send the wrong message.

Good call, kinda? It's a subtle deterrent, but we should really also explicitly say the "right message" at every opportunity it is appropriate to. And we already kinda do that.
I personally wouldn't mind a link to my own handle, but I get it.

The only team where i've yet omitted some people is bugsquad, since it has some people who aren't maintainers. I'm open to suggestions on that front (for example, we could call it "Members" there instead?).

Oh yeah, this is a fascinating case. There's a bunch of people I know on top of my head that aren't qualified as maintainers, but they're always happy to contribute in specific areas of expertise on the occasion, and their contributions should be acknowledged.
Although, one could see it as some sort of official endorsement beyond AUTHORS.md. Depending on how you look at it, it's not always respectful. Hmm...

@Ivorforce
Copy link
Member Author

Ivorforce commented Nov 7, 2025

One "problem" with the current PR is that team leaders are entirely undocumented here. I'm not sure what the consensus on that was.

None that I know of. I don't think there's any documentation on who 'team leaders' are right now, besides https://godotengine.org/teams/ which i think is a bit outdated. Following up on that will definitely require some communication with maintainers.

Linking the handles might send the wrong message.

Good call, kinda? It's a subtle deterrent, but we should really also explicitly say the "right message" at every opportunity it is appropriate to. And we already kinda do that. I personally wouldn't mind a link to my own handle, but I get it.

I should note, this decision isn't set in stone. It's just my suggestion for dealing with the problem. But I'd be open to link the profiles if that becomes a consensus.

The only team where i've yet omitted some people is bugsquad, since it has some people who aren't maintainers. I'm open to suggestions on that front (for example, we could call it "Members" there instead?).

Oh yeah, this is a fascinating case. There's a bunch of people I know on top of my head that aren't qualified as maintainers, but they're always happy to contribute in specific areas of expertise on the occasion, and their contributions should be acknowledged. Although, one could see it as some sort of official endorsement beyond AUTHORS.md. Depending on how you look at it, it's not always respectful. Hmm...

It would be nice to attribute everyone, but I don't think we'll stay up to date long with that. Listing the maintainers as endorsed by the foundation is probably the best we can do.

@Ivorforce Ivorforce force-pushed the area-maintainers branch 4 times, most recently from a380dd8 to ee18d82 Compare November 8, 2025 16:44
Copy link
Member

@Mickeon Mickeon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's fine as is and anything further can be discussed later?

@Ivorforce Ivorforce merged commit 2ce5f8e into godotengine:main Nov 10, 2025
@Ivorforce
Copy link
Member Author

Thanks!

@Ivorforce Ivorforce deleted the area-maintainers branch November 10, 2025 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants