Basil, http://wiki.mozilla.org/Update:Remora_Meeting_Notepad#April_9th: “I’ve posted to the very heated debate on MozillaZine, there are some reasoned replies coming thru now.”

There were reasoned replies long before you posted, Basil. You just needed to read between the disappointment and frustration. Please do your best to at least not patronise all your users.

Not sure if this has been mentioned here or elsewhere (and damned if I’m going to try and find it – due to the very issue I’m about to describe): communication for AMO is horribly fragmented:

* there are half a dozen personal blogs that I’ve encountered over the last few weeks which have each provided fragments of what is going on (and universally not responded in their comments threads about AMO 3.2 criticism)
* there’s Mozilla wiki ‘meeting notepad’ (http://wiki.mozilla.org/Update:Remora_Meeting_Notepad) which I just found
* there’s this forum (which I didn’t know was unofficial until I first posted in this thread)
* there’s bugzilla which exposes my email if I create an account – no, thanks. Bugzilla suggests I create a new email account just for bugzilla – yeah, right!
* there’s an IRC channel (so Mike Morgan tells us in a recent post on his personal blog). I don’t have time or inclination to set up and monitor IRC channels… and I think the same sentiment is felt by most users
* there’s http://blog.mozilla.com/webdev/ which transmits a small subset of what appears on dev’s personal blogs

And none of these are linked from AMO, which makes it kinda tough for the ‘average’ user to know there’s a new version on the way – or where to go to provide feedback.

The massive addon community, user and dev, deserves better.

Solution: create an AMO blog, link it from AMO. Each person involved with AMO dev should post to the official blog and copy to their personal one, if they choose. This is the only solution that makes sense if you are genuinely committed to engaging with the people who use AMO.

Thanks for listening.

(Now I better cross-post this to your blog in case you don’t return to read it here!)