Just a few things I would like to clarify:

- bugfixes change behaviour, always, otherwise they would not be 'fixing', 
that you rely on a buggy behaviour is a different issue than 'is this 
really a bug'
- before responding to you Sivel check around with other committers to make 
sure he was not imposing HIS opinion but a broad consensus (most committers 
do this before responding, unless they already know the consensus)
- we have form responses to try to avoid individuals (like me) from 
communicating in a way that can be considered harsh or impolite. We do add 
specific comments to the ticket in those forms.
- We have 2 community meetings a week, in which we are happy to discuss any 
issues and hear any extra arguments in the community, specifically to 
address what some perceive as a bad decision
- sivel locked the ticket for your benefit, we don't see/get notified on 
closed tickets, so any further discussion is lost (we should actually do 
this more often as many post to closed tickets and get no answers).  You 
already had an invitation and a link in his response to this forum as a way 
to continue discussion. I'm unsure what else he should have done.

I hope this clears things up, 

Brian Coca

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/f739f464-aff3-4288-8d4e-06c6c9604a54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to