<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>
<blockquote type="cite">IMHO the development mailing list is the best
place to point out these
issues and elicit interactions from people who aren't routinely going
through issues all day long, who are not yet aware of that particular
issue or perhaps of drupal's ability to subscribe to them (I didn't
know about that for a very long time).
</blockquote>
On occasion, it's good to point out to the list that there is a
critical issue that needs some love. Then after the first email,
discussion continues in the issue queue. So /sometimes/ this is
appropriate.<br>
<br>
You did send an email to the list a week or so ago stating that you
created that same issue in the queue and then got some valid feedback
and reviews. IMO that is enough to get people's attention and a follow
up email to dev isn't necessary to say you've updated that issue.<br>
<br>
I'm not trying to be a list ogre, just repeating what I've seen told to
others in your position in the past.<br>
<br>
Cheers,<br>
</tt>
<pre class="moz-signature" cols="72">Rob Roy Barreca
Founder and COO
Electronic Insight Corporation
<a class="moz-txt-link-freetext" href="http://www.electronicinsight.com">http://www.electronicinsight.com</a>
<a class="moz-txt-link-abbreviated" href="mailto:rob@electronicinsight.com">rob@electronicinsight.com</a></pre>
<br>
<br>
Ashraf Amayreh wrote:
<blockquote
cite="mida53d1b3b0704111411w21ea3e0fof9a37c3d5c097ad5@mail.gmail.com"
type="cite">IMHO the development mailing list is the best place to
point out these issues and elicit interactions from people who aren't
routinely going through issues all day long, who are not yet aware of
that particular issue or perhaps of drupal's ability to subscribe to
them (I didn't know about that for a very long time).
<br>
<br>
If issues are not to be discussed on mailing lists, then what exactly
do you propose should be discussed on the development mailing list?<br>
<br>
IMHO, mailing lists are pretty well known for being email intensive. A
not totally well formed mail is - in my opinion - much better than
having people thwarted for fear of *clogging* other people's mail
boxes. But of course that's my opinion. Others may disagree.
<br>
<br>
<div><span class="gmail_quote">On 4/11/07, <b
class="gmail_sendername">Rob Barreca</b> <<a
href="mailto:rob@electronicinsight.com">rob@electronicinsight.com</a>>
wrote:</span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"><tt>Ashraf,<br>
<br>
People who are interested in that issue will subscribe to it and get
email notifications when it is updated. If everyone sent an email to
dev when they posted/updated an issue we'd all drown in emails. Let's
try and keep the signal/noise ratio high like Moshe is talking about.<br>
</tt>
<pre cols="72">Rob Roy Barreca
Founder and COO
Electronic Insight Corporation
<a href="http://www.electronicinsight.com" target="_blank"
onclick="return top.js.OpenExtLink(window,event,this)">http://www.electronicinsight.com
</a>
<a href="mailto:rob@electronicinsight.com" target="_blank"
onclick="return top.js.OpenExtLink(window,event,this)">rob@electronicinsight.com</a></pre>
<div><span class="e" id="q_111e264bf33a3bd3_1"><br>
<br>
Ashraf Amayreh wrote:
<blockquote
cite="http://mida53d1b3b0704111315o57288472x96ecc834a533908c@mail.gmail.com"
type="cite">I've just posted two more examples on cases that I believe
can't be solved without the concept of hook overriding.<br>
<br>
<a href="http://drupal.org/node/134148" target="_blank"
onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/node/134148</a><br>
<br>
Still opinions on why this feature should (or should not?) be included
in drupal.<br>
<br>
Thanks for your time :-)<br>
<br>
<br>
</blockquote>
</span></div>
</div>
</blockquote>
</div>
<br>
</blockquote>
</body>
</html>