Honesty I think that the examples you quoted are all border line. I mean the
answers from developers are definitely improbable, just adding an emoticon I
think it will help to express the irony that probably I am catching in that
sentence and maybe you are not.
Frankly I believe that in any context, from source Forge forums to telling your
kids why they can't have more candies, it is quite bad and ineffective to say
just Yes or No without any supporting explanation.
In my opinion explaining is the key.
Therefore it is surely a fault to reply with a one-liner because that can
hardly fit any explanations.
> On 20/apr/2015, at 13:17, Keith Willians <keithwilli...@gmail.com> wrote:
>
>> On Mon, Apr 20, 2015 at 5:31 AM, Suraj N. Kurapati <sun...@gmail.com> wrote:
>> On Sun, 19 Apr 2015 18:44:59 +0100, Keith Williams wrote:
>> > In looking at tmux and the sorts of tickets raised against it I
>> > have noticed that a lot of genuine concerns users have had are
>> > closed with terse replies such as "This is in the todo list", or
>> > "This option isn't wanted", or "This is being worked on", without
>> > reference.
>>
>> Users can still add comments to those closed tickets, so the act of
>> closing a ticket does not necessarily put an end to its discussion.
>
> I understand that but the impression that leaves is just that; discussion
> closed. The ultimate thing here is that whoever closes something has made a
> statement of intent, otherwise it is just to be left open.
>
> e.g.
>
> http://sourceforge.net/p/tmux/tickets/186/ :
>
> Some felt strongly about this. No real explanation was given. You could keep
> the mailing lists around, but host the project somewhere else.
>
> http://sourceforge.net/p/tmux/tickets/177/ :
>
> Comments like "magic ESP hat" are not welcoming.
>
> http://sourceforge.net/p/tmux/tickets/131/ :
>
> "I really don't think this is necessary" - without explanation why.
>
> There's many more examples.
>
> Keith
>
>
>> For instance, a concerned user may add a comment to a closed ticket
>> asking for a reference on how "this is being worked on" or they may
>> ask for clarification on why "this option isn't wanted", and so on.
>>
>> > the tone needs to be gentler
>>
>> See http://www.catb.org/esr/faqs/smart-questions.html#keepcool
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> tmux-users mailing list
> tmux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tmux-users
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
