Feature description
I'm not sure if this is the right repository for this suggestion, but I think the Morphe ecosystem could benefit from a separate community-run website(maybe implement it in exisiting morphe patches site) for patch requests.
Users could search for an app, create a request if one doesn't already exist, or upvote an existing request.
Requests would be ranked by vote count, giving third-party patch developers a centralized view of which apps have the highest community demand.
Motivation
Currently, patch requests can be scattered across GitHub issues, repositories, chats, and different communities. This makes it difficult to know how many people actually want patches for a particular application.
A centralized voting system would provide an actual demand signal instead of developers having to judge interest from individual requests.
For users, it provides one place to request an app and vote for existing requests instead of repeatedly asking different developers.
For developers, it provides a ranked list of applications that the community is most interested in, helping them prioritize development effort toward patches that could benefit the largest number of users.
It could also reduce duplicate requests across third-party patch projects and make coordination between users and patch developers much easier.
Acknowledgements
Feature description
I'm not sure if this is the right repository for this suggestion, but I think the Morphe ecosystem could benefit from a separate community-run website(maybe implement it in exisiting morphe patches site) for patch requests.
Users could search for an app, create a request if one doesn't already exist, or upvote an existing request.
Requests would be ranked by vote count, giving third-party patch developers a centralized view of which apps have the highest community demand.
Motivation
Currently, patch requests can be scattered across GitHub issues, repositories, chats, and different communities. This makes it difficult to know how many people actually want patches for a particular application.
A centralized voting system would provide an actual demand signal instead of developers having to judge interest from individual requests.
For users, it provides one place to request an app and vote for existing requests instead of repeatedly asking different developers.
For developers, it provides a ranked list of applications that the community is most interested in, helping them prioritize development effort toward patches that could benefit the largest number of users.
It could also reduce duplicate requests across third-party patch projects and make coordination between users and patch developers much easier.
Acknowledgements