No explanation for what being on a team means for new contributors

[lolbinarycat]

Ideally we would have a section in the forge where we explain this, and then we could link that section from the README in case any new contributors find their way here (could happen if they join the triage team early on)

This was a major source of confusion for me coming from nixpkgs, where teams are mainly just exist as a list of who to contact about certain things and don't convey any additional authority.

[apiraino]

After having scrolled through the toml-schema.md I think this could answer the question:

• earn permissions on repositories as defined in [access.*]
• earn more permissions as defined in the [permissions]
• become a member of mailing lists defined in the [[lists]]
• (optionally) assume a role on the Discord server as defined in [[discord-roles]]

I am probably forgetting other points, now I am used to be a member. @lolbinarycat Do you want to submit a patch with more details of what was confusing?

[lolbinarycat]

the main one that is confusing IMO is the merge permissions, as that's the part that's not universal to all of open source, in some projects teams exist soley for communication purposes.