Certainly…but lets go beyond EIM for a minute.
I’ve heard a lot of people say, “why don’t they incorporate this feature or that feature”… and the reason may be quite logical. Problem is, most users get reactionary because their feature isn’t integrated.
Now to some degree, a program designed by committee isnt great either…we can’t please everyone…however, if there is a particular feature that is truly desired by the user base, it could be helpful to EITG as to where to turn their attention. I’d also like a way to focus the user base so they can properly say with a unified voice (as much as possible) that xyz feature is what we want most.
This may be impossible… but maybe its not. Although EITG makes the final decisions based off information that we don’t have that doesn’t mean we can’t come up with a method to present them with choices to help them make their decision.
Perhaps a polling method or election of features can help narrow things down…the point is, it would be nice to formally say to EITG that XYZ is the feature we really want. Can this be done within the spectrum of your plans? If it can…great…but to get that feature, it may cost us in time between upgrades or limitations on other features. If it can’t be done within EIAS framework wouldn’t it be nice to know that?
The other thing to consider is the programmers themselves. Open development tends to drive them a bit insane because they can not answer every question and if anything they remove themselves from that process because its too taxing. If we are focused, its easier to get a straight answer from them without a lot of the user posturing we see with our passionate opinions.
I just want to see if there is a mechanism we can create and employ that can make this process easier. It seems that the advisory board is our best method to get that info to EITG cause you’re interacting with your peers and there are more of us than there are of them.
