I propose relocating most issue discussions from GitHub to lemmy.ml/c/feature_requests to optimize developer time and foster increased user engagement and collaboration. This transition would allow developers to focus on critical tasks while leveraging the voting system on Lemmy to sort comments and identify the most valuable ideas. Moreover, Lemmy’s nested comments feature would enable a more organized discussion than on GitHub, where comments can become difficult to follow. By reserving the GitHub issue tracker for concise summaries and effective problem-solving, we can enhance the development process and improve the overall user experience. This approach aligns with the preference expressed by developers to minimize interactions on issue trackers [1]. Additionally, by reducing the flood of comments on GitHub, we can ensure that developers’ time is not wasted and that they can efficiently address important issues.
Software projects rarely have a shortage of good ideas. They often have a shortage of good implementers, or people who can make ideas into reality.
Which is why we should make the implementer’s job easier by providing only the relevant information instead of wasting their time with a flood of comments on the issue tracker.