ansible-collections / news-for-maintainers

Announcements of changes impacting collection contributors and maintainers
27 stars 4 forks source link

💡 Idea: migrate issues to discussions and surface them to the org level #39

Closed webknjaz closed 1 year ago

webknjaz commented 1 year ago

Observations

This repository's README calls out the possibility to use both Issues and Discussions but does not give any guidance as to when to use each. I feel like this contributes to the confusion in the decision making. Moreover, when one tries to create an issue, they are presented with a selection of issue templates that are derived from the org config and have nothing to do with the purpose of this repository — every one of them is asking for Ansible/collection versions/OS/STR/etc. I've clicked through a few of the old issues and haven't found any, following said templates. This means that every single issue creator was forced to clean up the template or notice that tiny Open a blank issue. link at the bottom. FWIW, it doesn't seem like the posts here do need any templates at all.

Issues represent problems/bugs/something to be worked on in the project. But this repository seems to exist for having discussions and announcements. Also, https://github.com/ansible-collections/news-for-maintainers/discussions/4#discussion-3845807 mentions that earlier expectation of using discussions over issues.

Problems

I think, the current setup causes more cognitive load, than it should.

Proposal

samccann commented 1 year ago

Hi @webknjaz ! This is an interesting idea. Can you please include it as a comment to the existing community-topic that is up for active vote on using Discourse as a forum for Ansible. See https://github.com/ansible-community/community-topics/issues/202

I don't wish to be heavy-handed as you have some great points, but going to close this issue for now so we don't split the conversation. Thanks for the ideas!