Consolidate github discussion places

[lzap]

I just learned that the osbuild project has this discussion and then several sub-discussions scattered around the project. Not a single place is promoted on the main page tho. I believe that a single place that would be promoted across our channels would help our community to grow.

Therefore I would like to propose transferring all (about 30) threads over to this discussion place and disabling discussions in all projects that have it (I counted 5 in total). Finally, I would go ahead and promote the new place on the project website footer.

To keep things nice and clean we can leverage labels or categories for different interest areas. What you think? The full proposal:

• Tranfer all discussions from all projects into this discussion place and label them correctly.
• Disable discussions on all projects.
• Disable issues and PRs on the community project which serves this discussion itself.
• Promote the new place both on the web page and READMEs.

Please upvote if you like this idea or provide arguments in the discussion below.

[achilleas-k]

I'm wondering if there is value in having repo-specific discussions, if there is anything that would be covered by keeping those enabled that isn't covered by issues or org-wide discussions.

Generally though, I'd be in favour of this.

[lzap]

Good call, I was thinking tighter integration with issues/prs but it looks like this almost works seamlessly. Let me try to link a composer PR, in fact PR no #1: osbuild/osbuild-composer#1

[lzap]

Ah there is one feature called "Create issue from discussion" on the right side, this leads to creating new issue in the community project which holds the discussion itself. I would suggest to disable PRs and issues for this repo, it is a technical repo only for the discussion itself.

Other than that, I cannot think of anything.

[supakeen]

I don't think there's much added value; the line between issues (which don't exist on organisation level) and discussion is already small.

However, I would say we'd want to mention the discussions on the organisation-link in all our README's similar to how we mention our mailing list and matrix channels :)

[lzap]

So if there are no objections, I will move discussions from all osbuild subprojects into the main org-level discussion and set labels appropriately. Then I will ask someone with org permissions to disable discussions on those projects (number of open threads in brackets).

• https://github.com/osbuild/images/discussions?discussions_q= (0)
• https://github.com/osbuild/legacy-website/discussions?discussions_q= (0)
• https://github.com/osbuild/osbuild/discussions?discussions_q= (3)
• https://github.com/osbuild/osbuild-composer/discussions?discussions_q= (16)
• https://github.com/osbuild/cloud-cleaner/discussions?discussions_q= (0)
• https://github.com/osbuild/image-builder/discussions?discussions_q= (2)
• https://github.com/osbuild/image-builder-frontend/discussions?discussions_q= (1)
• https://github.com/osbuild/bootc-image-builder/discussions?discussions_q= (4)
• https://github.com/osbuild/weldr-client/discussions?discussions_q= (1)
• https://github.com/osbuild/otk/discussions?discussions_q= (1)

Here is an example of moved thread:

https://github.com/orgs/osbuild/discussions/9

[supakeen]

I think @ochosi can take care of turning off the discussions elsewhere. Will you also update the README's (it's not mentioned here).

[supakeen]

Since I have the rights to do so I've moved the discussion that was in the otk repository and have turned off discussions on that repository.

[lzap]

Thanks, will do followups like READMEs and web page.

[ochosi]

Done ✅

[supakeen]

Very happy about this; thank you @lzap!

[lzap]

Move is complete, link is published at https://osbuild.org/ and I will now file PR change for README files for the top 10 projects. Thank you all for help, let’s grow our community!