> **Merge Poem extension into MediaWiki core**
Well now.... I've found the most interesting patch to watch for 2015.  If //$paragraphStack// is going to have a [greater] role when it comes to Poem's application - I'm sure no harm can ever come of it.
</sarcasm off>

Seriously - I hope whenever this move goes through, its given a week of vetting on test/test2 before its deployed to the usual suspects in a formal build. And, while I'm of like mind in the assessment it should have never existed in the manner that it has to date & the //lines// alternative would be the best route to follow - there are sooo many people that depend on it on an almost daily basis just on Wikisource alone that I would not have the nuts to screw around with it like this.

Truthfully, the issues with the tag to date have mostly been over the User:s response on occasion to the parser's `<p><br /></p>` effect compounded by the esoteric formatting typically done via template are both really where the ''blame'' should go than anything found in the extension itself. Admittedly, the choice //not// to force the opening and closing poem tags to always reside on their __own lines__ upon save & rendering starting on day-one with it's introduction sure hasn't helped matters either.

I implore you to mirror `.mw-body`s definition of `P` rather than the one(s) found in `Elements.css` -- those values are all long usurped by the time the page finishes loading its 1st click-in of the session. You'll find that `0.1`//em// less between the two definitions in //margin-top// is hard to catch initially... until the `1.5`em `line-height` setting is replaced [again?]  -- setting it  [back?] to //inherit// that is.

The last thing that comes mind would be more of an enhancement (like in T15644) than a bug . //Had// Poem been crafted to force it's tags to their own line/line-starts, the closing tag of the previous stanza would ''land'' right above the opening tag of the stanza that followed more often than not. This would be desirable because the ''gap'' between verses or stanzas are rarely as small as the predefined paragraph's are. Contributor's frequently came up with all sorts of ways to use empty inline-blocks to ''handle'' not only stanza spacing; but indentation and eol padding as well. Making attribute manipulation easier through the opening (//margin-top//) or closing (//margin-bottom) tags of //Line// itself could dramatically cut down on stuff like that.