Quote: They got rid of him to be able to develop without maintaining a proper test suite? To focus on competing with Microsoft Office instead of getting the product ready to use first? Talking about unreasonable...
This is bullshit!
* The drive towards end user readiness was proposed one year before Thomas at the KOffice sprint in Oslo. By me, in fact. At that point Thomas was dead against it, wanting to work on the libraries instead.
* The so called new features that "were in the way of making KWord user ready" were mostly bugfixes. For instance, in one of Calligra / KOffice the keys PageUp and PageDown works, in the other not. I will let you guess which community has implemented this "advanced feature".
* Calligra is not focused on mobile. We want to create an architecture that allows many different user interfaces. One of them is a UI that works for mobile. However, we also maintain the desktop version. If you look into the mailing list of Calligra Suite right now, you will see several usability improvement initiatives that are not done or even wanted in KWord.
* It is true that a lot of effort was put into import filters for MS formats. I fail to see why that isolated effort would impact end user readiness for the applications.
Finally, regarding end user readiness, I think it consists of two parts: lack of bugs and a usable user interface. The text layout a year ago was very bad with lots of bugs. A lot of the effort at that point went into fixing text layout bugs, leaving the KWord maintainer to fix problems in the user interface. In no way did the bugfixes impact any user visible parts of the UI except for improving rendering of document contents. Needless to say, we hardly saw any such UI improvements.