Closed valencik closed 1 year ago
Given that that discussion was fairly broadly scoped, I don't see any obvious security concerns. So this looks straightforward. Someone in the maintainers
team (which I apparently am not) will need to push the button.
If I understand correctly:
I don't think any of the prior maintainer discussions have been "classified documents," and if they were, I don't know that GitHub would be the ideal way to broadcast it. Moving forward, regardless of whether we transfer the old ones or not, the public option sounds right.
We should make sure that everyone understands that it's public, but agreed.
Well, we missed the deadline, but there's a JSON archive on the team page that told me what I needed to know.
To enable the org discussions, we need to pick a repository. This one seems as good as any.
Agreed, this repo makes sense for discussions
The GitHub "Team Discussions" feature is being deprecated. https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/
We have used a the
maintainers
team discussion board. https://github.com/orgs/typelevel/teams/maintainersThe recommended action to use change our Team discussions into Organization Discussions. So instead of being at the team level, they'll be at the org level.
Edit: I've just checked all the other teams, no discussions, so it's just the
maintainers
team discussion that we'd need to migrate.