On 3/25/06, Jonathan Revusky <[EMAIL PROTECTED]> wrote:
>
> Craig McClanahan wrote:
> > On 3/25/06, Jonathan Revusky <[EMAIL PROTECTED]> wrote:
> >
> >>The question is, at the very least, broadly on-topic.
> >
> >
> >
> > This interpretation is wildly out of sync with the formal description of
> > this mailing list's purpose[1], quoted below:
> >
> >     Subscribe to this list to communicate with other developers
> >     that are using Struts for their own applications, including
> >     questions about the installation of Struts, and the usage
> >     of particular Struts features.
> >
> >
>
> So where should such a question be asked, Craig? On rec.automotive? On
> alt.politics.libertarian?
>
> It still seems broadly on-topic to me. It's certainly a legitimate,
> well-formulated question.
>
> Seriously, the only other possibility I see is struts-dev. If it's
> off-topic on both struts-user and struts-dev, then the question really
> is (as I am starting to suppose) basically taboo.


What does the mailing list description for the dev list say?

    Subscribe to this mailing list to communicate with other
    developers interested in expanding and improving the
    functionality supported by Struts itself.

So I guess it depends on your goals :-).

So, cutting to the chase, if I pose the same question on struts-dev, you
> and the others would answer it?


It wouldn't get rejected as off topic, but your rude and obnoxious behavior
has made me, speaking for myself, totally uninterested in whether you ever
receive closure on it.  So I'll most likely just ignore you there as well as
here.


Jonathan Revusky


Craig


PS:  Lest you think I'm an arrogant jerk that deigns to answer only
questions from "worthy" people, two notes of interest:

* If you count the number of questions that I've answered on
  this list alone (let alone all the other lists I participate in),
  it's in the many thousands.

* Adding you to my internal ignore list just doubled its size.
  This is the first time there has ever been more than one.

Reply via email to