Re: [MLO] How to handle Feature Requests

2011-01-14 Thread Gogol Module
Calendar overview +1 too Cheers NG -- You received this message because you are subscribed to the Google Groups MyLifeOrganized group. To post to this group, send email to mylifeorganized@googlegroups.com. To unsubscribe from this group, send email to

RE: [MLO] How to handle Feature Requests

2011-01-07 Thread mlo
Of Mark Levison Sent: Thursday, January 06, 2011 4:21 PM To: Mylifeorganized Subject: [MLO] How to handle Feature Requests Its wonderful that people discuss their needs and desires for features on this list, however this discussion doesn't give Andrey and his team a good sense of the priorities

Re: [MLO] How to handle Feature Requests

2011-01-07 Thread Mark Levison
On Fri, Jan 7, 2011 at 12:54 PM, m...@grantsmiths.org wrote: *Mark, Uservoice does appear to be an important step forward by giving a clear picture of the priorities of a proposed enhancement. However, the picture is flawed because it only shows how much support a proposal has, without

Re: RE: [MLO] How to handle Feature Requests

2011-01-07 Thread Lisa Stroyan
If you object to proposal X couldn't you just create a feature of not X and vote for that? That way people would be limited in their objections and they would carry a lot of weight. Lisa from mobile -- You received this message because you are subscribed to the Google Groups MyLifeOrganized

Re: RE: [MLO] How to handle Feature Requests

2011-01-07 Thread pottster
You raise an interesting point Dwight. Firstly though, all credit to Mark for setting up the MLO uservoice facility as an interim. Andrey said in the product roadmap that he will be looking at a longer term solution for feature suggestions which may or may not be uservoice. I tend to agree with

[MLO] How to handle Feature Requests

2011-01-06 Thread Mark Levison
Its wonderful that people discuss their needs and desires for features on this list, however this discussion doesn't give Andrey and his team a good sense of the priorities. After all it costs nothing to say +1 to every request that goes by. As a result we've established mlo @