On 3/8/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
...well, the vote was started. and the outcome has a potential to significantly impact projects that are running in prod or are very close to it. so i figured it would be important to get user feedback on this since they are the ones affected...
With my mentor hat on, I'd suggest having a [POLL] on the users list, not a [VOTE]. I'm talking about a general rule: I don't want to interfere with this particular issue. IMHO, decisions are made by developers by voting, and for some important issues like this one it's good to poll users first. For complex/important/life threatening issues, developers might need to agree what the poll will be about first, so a developer vote -> user poll -> developer vote pattern might be good in some cases. Hope I'm not being pedantic - just trying to help based on experiences in other projects. -Bertrand (wondering how a mentor hat looks like, by the way ;-) On 3/8/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Igor Vaynberg: > THIS VOTE NEEDS TO GO ON USER LIST ...Can we slow down the rate at which new proposals are raised, and at least agree on wicket-dev before proposing something on wicket-user?..
