Roadmap transparency: i.e. How many upvotes does a Feature Request need before you actually implement it/work on it?
Feature request: Roadmap/Development transparency
In scrolling through the current feature requests, and having put in a few myself, I'm curious: How many upvotes does a feature request need to get before you guys actually start working on it? Is there a certain number of votes per period of time, or how do you decide what actually gets worked on? I ask because I often see a feature request, and the response is generally something along the lines of:
If the Emby Team already agree
Hi. What you have to realize is that being "transparent" to you is being transparent to everyone - including our competition. So, that is one reason you are not going to see a lot of definite commitments on exactly what is under development at any given time or when things will be released. We usually will tell you when something is actively under development but may not be able to provide much information before then.
There is no hard and fast number for a request and, while we want the
