- Notifications
You must be signed in to change notification settings - Fork302
-
As GitHub is now supporting discussions I think we should consider using it. I have enabled it for now so we can get a feeling on how well it works. I think we need to be careful though on what we want to use it for. Main goal should be to make communication within DJA more convenient for users and easier to maintain for the maintainers. For me the issues are basically work items which can be worked through and then closed. Currently issues are also used for questions and new feature request proposal. Those two types do not really work well with issues as there might be more then one answer to a question or idea how to implement a feature. Discussion work much better as there are open ended and answers can be marked. So for this I would use discussions for and for some other not code relevant talk. I would be glad to hear your opinions about it. |
BetaWas this translation helpful?Give feedback.
All reactions
🎉 1
Replies: 1 comment 1 reply
-
We have only been using discussions for three weeks but I really started to like them. From a maintainer perspective I want to keep the issues clean so what I would love to see in the future:
I have created PR#941 with issues templates to move us into this direction. Clean up of the current issues need to follow. Any comments are welcome. |
BetaWas this translation helpful?Give feedback.
All reactions
-
As an update I went through all the issues and except the once which are marked with labelneeds-information do I think that all are ready for any contributor to pick up and implement. As GitHub suggests, I've introduced the labelgood first issue to guide new contributors where to start. This has already shown its fruits as new contributors picked up some I marked. What remains is to update our contribution guidelines (see#985) to reflect that any issue can be picked up and worked on and guidance to good first issue etc. |
BetaWas this translation helpful?Give feedback.
All reactions
👍 1