<div dir="ltr">On Sun, Aug 10, 2008 at 6:39 PM, James Hawkins <span dir="ltr"><<a href="mailto:truiken@gmail.com" target="_blank">truiken@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Exactly. You open a bug stating that 'Command & Conquere Red Alert 3<br></div>
fails to authenticate' and then add in a bug comment that the problem<br>
is because of missing required winhttp functionality. Zac then sees<br>
the bug report and adds his own comment stating whether he has time to<br>
work on it or not plus any additional information he has to help<br>
others that want to work on the bug.</blockquote><div>I've submitted these kinds of bugs before and they have a tendency to get closed for not having enough information. Especially in this case, such a bug is nearly useless:<br>
1) The Red Alert 3 Beta is locked to a particular license key, which it associates with a particular PC<br>2) I do not know what is missing until I implement things, since the entire DLL is stubs<br>3) There's no guarantee that the relevant person will ever see the bug report, Zac was not on the email list for this bug even though it targeted the winhttp component (there are other bugs in this component and Zac has not replied to any of them)<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">There's really no point in arguing about policy. We don't allow<br></blockquote>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
metabugs, exactly because they serve no purpose and usually hinder the<br>
development process.</blockquote><div><div>Of the policies posted on the Wine website I have never found anything
related to this discussion (<a href="http://wiki.winehq.org/Bugs" target="_blank">http://wiki.winehq.org/Bugs</a> comes closest,
but does not discuss the issue). Even if there was such a policy posted, it is reasonable to discuss re-evaluating it when policy is incongruous with productivity. Many open source projects use metabugs, even though I would say the bug in question is not very "meta," so I'd say that there's a certain amount of burden of proof necessary before it's accurate to say that these bugs hinder the development process.<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> My original suggestion was to open a new bug<br>
report for the fact that C&C doesn't work, and that suggestion still<br>
stands.</blockquote><div>I plan on it, obviously opening a bug that does not fullfil your guidelines results in it being closed rather than clarified. I find this behavior particularly irritating, I'd much prefer to be told to re-title the bug (or have it re-titled) to say something more specifically related to the application in question.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Please don't top-post on this mailing list.</blockquote><div>Sorry, I replied to all and didn't notice the mailing list was on there (and I was not responding to a specific statement).<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
--<br>
<font color="#888888">James Hawkins<br>
</font></blockquote></div><br>Erich Hoover<br><a href="mailto:ehoover@mines.edu" target="_blank">ehoover@mines.edu</a><br></div>