<br><br><div class="gmail_quote">On Mon, May 9, 2011 at 12:41 PM, Kevin Kuphal <span dir="ltr"><<a href="mailto:kkuphal@gmail.com">kkuphal@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div><div></div><div class="h5">On Mon, May 9, 2011 at 9:00 AM, James Le Cuirot <span dir="ltr"><<a href="mailto:chewi@aura-online.co.uk" target="_blank">chewi@aura-online.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div>On Mon, 9 May 2011 08:12:24 -0500<br>
Kevin Kuphal <<a href="mailto:kkuphal@gmail.com" target="_blank">kkuphal@gmail.com</a>> wrote:<br>
<br>
> > I wish to express my concern at how tickets are sometimes being<br>
> > handled by the developers, in particular with regard to how<br>
> > PulseAudio users are being treated as second-class citizens. Now I<br>
> > know that some of you have strong opinions about PulseAudio and you<br>
> > are obviously entitled to those opinions. You are even entitled to<br>
> > refuse your time to work on PulseAudio issues yourselves but please<br>
> > do not lock such tickets without good reason. This prevents users<br>
> > from talking about these issues or even providing possible fixes<br>
> > without posting to this list as I am doing today.<br>
> ><br>
><br>
> My only comment on this is that this is *exactly* why the ticket is<br>
> locked. It has been said time and time again. Discussions occur on<br>
> the discussion list. The TRAC system for this project is not to be<br>
> used as a conversation archive or discussion forum and, as such,<br>
> tickets are locked when it occurs. This is not a slight against the<br>
> ticket reporter, commenter, or the bug in question. It is simply a<br>
> mechanism to keep the ticket record clear of excess comments.<br>
<br>
</div></div>That's fair enough and I'll be sure to come here in future. As someone<br>
who hasn't subscribed to these lists before and simply found the ticket<br>
through Google, I was not aware of that. Simply locking the ticket<br>
doesn't really come across that way, especially when you also see<br>
comments like "I highly recommend nuking all traces of pulseaudio from<br>
any system where you intend to use audio." You could forgive me for<br>
thinking that the developers were being less than helpful. Thank you<br>
for clearing this up anyway.<br></blockquote><div><br></div></div></div><div>It may not be spelled out quite so specifically, but the general sentiment is in the TicketHowTo linked at ticket creation. It may be worth considering for the project to add a link to this on existing tickets since, as you point out, may be coming to the "party" late and have missed that part.</div>
</div></blockquote><div><br></div><div>Nevermind my obvious overlooking of the link at the top of the page. Given that, I amend my suggestion to linking it down by the comments :)</div><div><br></div><div>Kevin</div></div>