I'm really curious... Why do you want to join the SFML Team anyway? There is really nothing that Team members can do that non-Team members can't.
If you ask me, it has more to do with responsibility and accountability than anything else.
SFML has reached the point where just as many contributions are made to the codebase by non-maintainers (i.e. non-Team members) as the maintainers. Maybe at some point, non-maintainers might even make more contributions.
Being part of the Team simply means that we take care of the "dirty work" that just has to be done e.g. release management, CI, website/documentation maintenance etc. It really isn't a flattering job if that is what you were expecting. Any time something breaks really bad, we are more or less the ones who get shouted at.
The internal discussions mentioned above are also more about the "status quo" of development and general maintenance issues than anything else. Any time we want to discuss new features or implementations/bugs, we start publicly visible threads. Most of the communication between Team members actually takes place in public places such as the forum/GitHub/IRC as opposed to internal ones.
Considering what I've said, I hope you can see now that being in the Team isn't a privilege, it's more of a formal designation. The Team was originally created out of the need for secondary maintainers since Laurent could no longer invest as much time as he previously did and as such, general progress was slowing down a bit more than the community was ready to accept. We offered to help with maintenance tasks (such as the website and reviewing feature requests/PRs etc.) and he accepted. The rest, as they say, is history...
