(In reply to comment #28)
> bug 52723 is a recent bug to deploy Legoktm's MassMessage extension as a
> solution to bug 35306, it is less than a month old there has been little
> public
> discussion [...]

For your following points, it seems you're implying that the desiderata and requirements for this extension are not clear. This couldn't be less clear: the requirements are to take over EdwardsBot (a successful product) in the least impactful way possible.

> 
> The problem with moving on bug 52723 as a solution to bug 35306 is it commits
> Features Engineering to maintaining an extension that is a stop gap solution
> with no or very little discussion in a manner that doesn't serve a broad
> strategic goal about how messages, notifications, etc. should be handled on
> the
> wikis. [...]

This appears to be a false problem. If Echo or something else in a future provides equivalent or better features, the extension will fall into disuse and/or it can be undeployed.

> [...] After discussion during that Friday
> meeting among the EPMs, I compromised to let it to go out on two test wikis,
> but not on mediawiki. Nobody made the case that it should go out on
> mediawiki.

AFAIK, this is a MediaWiki extension. Do you mean "not on mediawiki.org"?

> [...]
> 
> For example, features in MassMessage and EdwardsBot need to be addressed in a
> Must-Have, Should-Have, Could-Have, Won't-Have (MoSCoW) framework. 

Isn't this what dependencies are for? I see one dependency and it's fixed.

> [...]
> 
> 1) wait for some things to happen: legoktm to get an RfP, Echo to be on all
> wikis, and Benny to do an entire Flow only sprint and balancing his time more
> effectively wrt Echo.

I don't understand how keeping to use a bot for the very same things this extension would do helps Echo.

> 2) MoSCoW other features of MassMessage/EdwardsBot for integration into Echo
> 3) Enhance and deploy a first pass to Echo to allow some sort of mass
> notification from a wiki list
> 4) Some sort of cross wiki notification enhancement (requires a design pass)
> 5) Discuss how to implement must-have or should-have features of EdwardsBot
> that can't live in Echo (permanent log of events)?
> 6) Add those to plan and be done.

I don't get these points. If you're responsible for Echo, it's your responsibility to decide what Echo is going to incorporate, it's not the others' responsibility to guess it and be blocked for years while you figure it out. Are you saying you're going to figure it out so that people can understand how to work with/for Echo without being just blocked by it?

> The above can occur independently or in parallel to the above. If Product
> thinks it cool to commit Platform's constrained engineering resources to
> deploying and supporting MassMessage Extension forever 

This is one thing,

> and use it to take
> advantage of Echo when the features roll out in some undefined future,

this looks like an unreasonable requirement (are you going to shutdown message bots too if they don't use Echo?).