Announcing sigs merge on TiDB community

[tison]

Hi community members,

Following the previous proposal below we’re now in a stage merging sigs into teams which owns one or more repositories.

Proposal: Lightweight and GitHub Friendly Special Interest Group

What is the problem SIGs meet? SIGs divide repository Generally SIGs own one or more repository, but sig-sql-infra, sig-planner, sig-execution, sig-migration, and so on share the main repo pingcap/tidb. It hurts that we artificially break GitHub repo into several parts while database internals are interrelated. Most of our contributors are looking forward to a GitHub repo granularity governance that can be easily understood. SIGs are apart from GitHub permission model SIG members’ permission…

See also the pull request below for the whole decision making process.

sig: merge

The steps remaining are:

• Create GitHub teams according to the decision and membership.
• Update lgtm config to let the bot respects new organization.

[tison]

Done creating GitHub teams according to the decision and membership.

[tison]

Done update lgtm config to let the bot respects new organization.

We’re now in a new era

[xxchan]

Thank you, tison. This is exciting!

[feitian124]

good news and congratulations to us all

likes the readme in teams folder, which makes the who, where, what quite clear.

[feitian124]

what is the usage of github teams here?
are they sub orgnazation of pingcap?
who can join?

[xxchan]

An example from beyondstorage community may help you get it.

[feitian124]

thank you.
in case someone else don’t know github teams, see here
https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams

[tison]

Thanks for helping explanation