[horde] Fwd: [Tickets #12069] Re: Kronolith meetings don't show Organizer

[Michael M Slusarz]

Quoting Michael J Rubinsky <mrubinsk at horde.org>:

> Quoting simon at simonandkate.net:
>
>> Anyway, moving on... is there a way to "+1" feature requests or  
>> bugs or similar, as some places have, to provide opportunity for  
>> your user community to give input on what they think important? How  
>> do you prioritise what is in the queue and is getting attention? Do  
>> you publish this information?
>
> We prioritize things pretty much the way I already described them.  
> While I can't speak for other developers, I'm sure we all do similar  
> prioritizing for the code we are responsible for.

For the record: if there is an active bug report and/or enhancement  
request open on bugs.horde.org that has existed for more than a few  
days (read: it has been reviewed by at least one developer and not  
rejected), this is all the indication needed that the project agrees  
that something needs to be fixed/improved.

Adding a '+1' comment that is NOT followed by either "Here is a  
patch...", or "Here is how you can duplicate...", or (ideally) "Here  
is funding..." is borderline spam.  We already know and agree there is  
an issue so this kind of comment provides no further information (or  
incentive) to look at the ticket further.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]