Issue Tracker

169 readers

1 users here now

Welcome to the Lemmy Issue Tracker!

Here you can share your ideas and report issues related to the Lemmy project. We welcome all feedback and suggestions to help us improve the platform.

Guidelines for submitting issues

Please write a single idea or issue per post/comment.
Use the following format for your post title:
- [BE] or [UI] for backend or web-ui issues.
- The type of issue: [Bug], [Feature Request], etc.
If the issue is resolved, please add [Closed] at the start of the comment.

How to contribute

If you want to contribute to the development of Lemmy, please check out our GitHub repository. You can also join our Matrix chat to discuss ideas and issues with the community.

Thank you for your support and contributions to the Lemmy project!

founded 2 years ago

MODERATORS

[email protected]

Moving Issue Discussions to Lemmy (lemm.ee)

submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

1 comments fedilink hide all child comments

I propose relocating most issue discussions from GitHub to [email protected] 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.

[^1]: Update from Lemmy after the Reddit blackout

issue_tracking_bot
The issues of deleted 'ghost' accounts haven't been posted. Need to figure out why.
Should edit posts and comments if the corresponding issue content changes.

top 1 comments

sorted by: hot top controversial new old

[–] [email protected] 18 points 2 years ago

I think this could be very valuable for the community and the Lemmy devs. However, I believe to be successful, there needs to be a volunteer(s) who “sync” the community to the GitHub issues. We could automate this but that would make the situation worse. Here’s how I could imagine this working:

When a new feature or bug is posted, the mod determines if this is duplicated or not. If so, they will reply to the post with a link to the previous post and lock the current one. If it is truly new, the community can vote and comment. After a week or so, if the community supports the new feature or fixing the bug, the mod will open a new GitHub issue with a summary of the community discussion and link to the discussion.

This is a lot of work for the mods, but I believe it would really add value for both the Lemmy community and the devs.

https://lemmy.sdf.org/comment/1061832