A more appropriate question would be: what went wrong in FOSS that everyone starts with forking, renaming the project, wrapping behind their doors, refactoring, rewriting, and only then offering to maybe, you know, actually share code and avoid a fork?

Specially when upstream is still quite alive with plenty of contributors, if only slow?

The sad part is that we had the same discussion like, less than a few months ago..

But oh well, that opportunity is lost already, so let's center on the future. I personally agree on the store UI changes and dropping pre3.0 support. Slots are too annoying either way.

EDIT:
In the sense of evaluating what will be the best option ahead for users (and developers) of Pebble and Sailfish, and at this point, I believe it's 'embracing your fork'.

But no need to "act surprised" when meeting resistance after taking over the reins of still-alive project.