hair-pulling frustration

[Richard Gaskin]

Sean Cole wrote:

> I have a suggestion for this, having just read the entire thread.
>
> How about this approach (which is nothing new - Apple use a similar
> system and I personally have had much success with it). In the
> LiveCode app itself (both Commercial and Community) in the Help menu
> should be a button to submit a report. This can either take you to a
> basic form on the web or internally in the app itself (a better
> option to keep down spam).

That's an excellent suggestion - I'll pursue that with Ben later this
morning.


> I have a bug (Bug 13801
<http://quality.runrev.com/show_bug.cgi?id=13801>) I
> reported a little while back that, because I had no time because of
> my clients demands on my time, has been marked as 'Resolved' due to
> my not responding to their request for a sample stack. When my time
> is a little more free'd up (i.e., not now, despite my ability to
> write this email - proof that what you said earlier was bumpkin and
> unfair - emails are easier to write than are sample stacks that can
> replicate issues along with recipes.) I will be able to reopen the
> report and prove that it is indeed an issue that needs resolving.

My apologies if what I wrote seemed unfair.

It's statistically accurate to note that an overwhelming majority of
issues in the bug DB do not have example stacks attached, and that
includes the 1600+ items fixed over the last year.

 From time to time a given issue may elude a simple recipe, and in those
cases it may be beneficial to provide an example stack.

It's helpful that you provided the link to the report, as we can see
there that while Hanson asked if you had a sample stack he never
required it for you to re-open the report if you choose to do so.

The one thing he did require is that you please try to see the issue in
the latest build, and given the scope of changes between builds lately
it's not impossible it may have been addressed while fixing other things.

One of the benefits of an open source project having a Community Manager
is that you get another whipping post: yours truly. :)  I'm happy to 
advocate any community concern that hasn't been sufficiently addressed 
through other channels.

In this case, however, the only action needed is to verify that the 
issue remains in the latest version, and to write one sentence there 
noting if that's the case.  I haven't seen this myself, so I'll have to 
rely on your help on that.

As Hanson wrote there, with your notice that the issue remains they'll 
devote internal resources to trying to reproduce it.

-- 
  Richard Gaskin
  LiveCode Community Manager
  richard at livecode.org