Extension talk:MobileFrontend/Remove existing HTMLFormatter code from MobileFrontend extension

RFC?

Any reason why this isn't an RFC? -- RobLa-WMF (talk) 18:18, 17 September 2013 (UTC)

It's only rough notes for the time being. A lot is still in our control and can be achieved without an RFC. We are not sure what a RFC would look like but will raise one if and when one is necessary and we know what it looks like. Jdlrobson (talk) 18:26, 17 September 2013 (UTC)

So if we're concerned that the RFC process is too heavyweight for this we can make this an RFC and promise ourselves we'll jam it throught the process quickly. I dunno how quickly is quickly, but quickly. I'm waiting on this for CirrusSearch so I'll bang heads to get it through. Anyway, making this an RFC would force us to rethink exactly what we are getting out of this other than code reuse. For instance, the page mentions regressions but the patch in gerrit for moving HTMLFormatter into core doesn't hook into the parser in such a way that it'd catch parser changes that'd cause a regression. In other words, I think just the HtmlFormatter move is enough to deserve an RFC. Or it could be, if we promise to go fast. NEverett (WMF) (talk) 17:37, 18 September 2013 (UTC)