We have @roostorg/.github which is a special repo that GitHub uses for org repo defaults, like CONTRIBUTING.md, CODE_OF_CONDUCT.md, issue templates, etc. The nice thing is that these show up in repos when the repo doesn't have its own; the less-nice thing is that if we want this information to be included on the community site (which I do!), we have to duplicate it and try to keep it in sync—which isn't sustainable.
Instead, I propose that we move to treating the repo default files as minimal stubs that link to the appropriate community site page. This way things are still discoverable, but they're not duplicated.
We have @roostorg/.github which is a special repo that GitHub uses for org repo defaults, like CONTRIBUTING.md, CODE_OF_CONDUCT.md, issue templates, etc. The nice thing is that these show up in repos when the repo doesn't have its own; the less-nice thing is that if we want this information to be included on the community site (which I do!), we have to duplicate it and try to keep it in sync—which isn't sustainable.
Instead, I propose that we move to treating the repo default files as minimal stubs that link to the appropriate community site page. This way things are still discoverable, but they're not duplicated.