I've just posted two more examples on cases that I believe can't be solved without the concept of hook overriding. http://drupal.org/node/134148 Still opinions on why this feature should (or should not?) be included in drupal. Thanks for your time :-)
Ashraf, 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. Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com rob@electronicinsight.com Ashraf Amayreh wrote:
I've just posted two more examples on cases that I believe can't be solved without the concept of hook overriding.
Still opinions on why this feature should (or should not?) be included in drupal.
Thanks for your time :-)
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). If issues are not to be discussed on mailing lists, then what exactly do you propose should be discussed on the development mailing list? 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. On 4/11/07, Rob Barreca <rob@electronicinsight.com> wrote:
Ashraf,
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.
Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com rob@electronicinsight.com
Ashraf Amayreh wrote:
I've just posted two more examples on cases that I believe can't be solved without the concept of hook overriding.
Still opinions on why this feature should (or should not?) be included in drupal.
Thanks for your time :-)
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). 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.
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. I'm not trying to be a list ogre, just repeating what I've seen told to others in your position in the past. Cheers, Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com rob@electronicinsight.com Ashraf Amayreh wrote:
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).
If issues are not to be discussed on mailing lists, then what exactly do you propose should be discussed on the development mailing list?
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.
On 4/11/07, *Rob Barreca* <rob@electronicinsight.com <mailto:rob@electronicinsight.com>> wrote:
Ashraf,
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.
Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com <http://www.electronicinsight.com> rob@electronicinsight.com <mailto:rob@electronicinsight.com>
Ashraf Amayreh wrote:
I've just posted two more examples on cases that I believe can't be solved without the concept of hook overriding.
Still opinions on why this feature should (or should not?) be included in drupal.
Thanks for your time :-)
On 11.04.2007, at 23:11, Ashraf Amayreh wrote:
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).
The problem is that there are several hundred issue updates on drupal.org and several dozens of new issues every day. Now, if every developer would announce his/her newly created issue, how many e- mails would you get?
IMHO, mailing lists are pretty well known for being email intensive.
There is a difference in receiving 20 emails a day and receiving 500 e-mails a day.
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.
Nodbody tells you to not post to the development mailing list if - and only if - the issue has to be discussed on the mailing list rather than in the issue queue. Konstantin Käfer – http://kkaefer.com/
participants (3)
-
Ashraf Amayreh -
Konstantin Käfer -
Rob Barreca