limitation of 3 collaborators

AFAIK, this is not true anymore.

All our teams posts whent public... not what I understood a migration was. It's event tagged as "Team posts"

Thanks for the feedback here! We're actively working to fix this now.

Hm ran into this one as well

I agree as well with the consolidation between Team Discussions and Repository Discussions.

One thing that would be useful though would be to be able to mark a team repository as the one holding team discussions — pretty much like we do for the organization. This would give a super useful and consistent user interface to hold smaller scale team discussions in a similar way you do for the organization.

Would totally welcome this.

They do not all need to be in a single project board and can be in separate repository for each team.

Hey @stephantamminga for your case, it probably makes the most sense to have a team-level repository (which can be private) and move your Team Discussions to a Repo-level Discussion there instead!

Hmmm, that doesn't feel like a working solution. The team discussion would always be on the landing page of the team, a repo discussion would be buried somewhere. Is there an option to place announcements on a team page?
To be more specific: I'm using the team discussion function to put guidelines and such on the landing page. About that: what will be the landing page if discussions are removed?

Thanks for sharing this. Team Discussions weren't really designed for announcements this way. Any new discussion would cause previous ones to get buried on the landing page, so something like guidelines would quickly get buried. In Repo Discussions however, we have a category specifically for announcements. Also, many users of Repo Discussions use pinned discussions for things like guidelines to stay on the landing page. Team Discussions doesn't have those features. Since most of GitHub works around repos, we've found Repo Discussions to be far more discoverable than Team Discussions by most users, and they have seen significantly higher usage for that reason. I'd encourage you to try it out!

To answer the other question you have - the landing page of Team Discussions after deprecation will show a list of members in that team.

Thanks for sharing this. Team Discussions weren't really designed for announcements this way. Any new discussion would cause previous ones to get buried on the landing page, so something like guidelines would quickly get buried.

Discussions can be pinned, which serves perfectly as an announcement.

They do not need to be at the org level you can have individual discussions on separate repositories.

💯, but that really isn't a "team" discussion IMO. I tend to keep discussions in repos to be specific to that repo, "next to the code" if you will. Having "yet another repo" as a team repo is something that would then require us to go through security audits (cause it's a repo 🤷🏼 ), keep code owners documented, etc. Some are things that I'm trying to change in our org but it'll take time.

Being able to select some discussions to be private to the team or available to the general org was also useful.

This is all "me issues", but it's where I'm at 😅