acoustic-carpenter-78188
01/20/2023, 7:20 PMflyte repo.
In order to centralize the community-related information like Governance, communication methods, Code of Conduct, contribution guides, among others, a flyteorg/community repo would be useful. Also it would help with issue tracking, avoiding having community-related issues stored alongside a number of issues related to the codebase.
The overarching goal is to make easier for new and established community members to discover and track any progress on making the Flyte community even more welcoming for users and contributors.
Also, if there would be additional OSS projects in the future hosted under flyteorg (even in a monorepo), /community could still be the place to centralize all the procedures for the flyteorg community
What if we do not do this?
With the use of labels we could filter out the community-related issues, but we would have to create new labels for this to happen.
If someone new to the project explores current issues, it would probably not be evident that community-related discussions/ideas are also located there
Related component(s)
No response
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyte