Issue Tracker - lemm.ee
lemm.ee
## 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 comment. - Use the following format for your comment: - [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 [https://github.com/LemmyNet/lemmy]. You can also join our Matrix chat [https://matrix.to/#/#lemmy:matrix.org] to discuss ideas and issues with the community. Thank you for your support and contributions to the Lemmy project!

Hey everyone! Exciting news: there’s now a Lemmy Issue Tracker community where you can share your ideas, suggestions, and collaborate with others. This community is more flexible than the GitHub repository when it comes to duplicate posts, so feel free to share any great ideas you come across. With nested comments and a voting system, discussions on Lemmy are more organized and easier to follow compared to GitHub.

By moving most issue discussions from GitHub to Lemmy, we can optimize developer time and foster increased user engagement. This approach aligns with developers’ preference to minimize interactions on issue trackers[1]. By reducing the flood of comments on GitHub, we can ensure that developers can efficiently address important issues.

So, what are you waiting for? Head over to the Lemmy Issue Tracker community and start sharing your ideas today!

[email protected]

  1. Update from Lemmy after the Reddit blackout ↩︎

  • RandomBit@lemmy.sdf.org
    4·
    1 year 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.