Oh Boy, I’m not even going to start to argue with you why a patchset isn’t a fork

Not even worth your time – Roy’s described the OpenSUSE/SLES kernel patches as a fork, and suggested that no other distro patches its kernel (!)

Obviously.

Please help me and tell me where it is because “rpm -qa | grep -i mono” returns nothing. But since you always tell the truth and I use version 3.0 of “that evil fork” ™ is has to be there.

But where?

Somebody needs to knock Sun and Novell’s collective heads together.

Both have problems.

The problem with Sun is that they have no community involvement with OOo – decisions as to what to allow are made for opaque Sun business reasons and their bug tracker is an unwelcome place for those outside Sun,

Distros use go-oo because go-oo is somewhere they can actually cooperate. Building OOo is very hard – and with every distro needing to apply identical tweaks which Sun doesn’t want to (as they don’t benefit Windows or Solaris), go-oo provides the “community” version of OOo which every distro maintainer wants and needs.

At the same time, nobody doubts that there is some degree of Novell involvement in go-oo – but there’s no active censorship of patches, or convoluted copyright assignment required. In the end, what distros would /like* is a non-profit OOo foundation to look after this stuff – but go-oo is MUCH closer to that ideal than Sun’s ivory tower product

Translate: create a UI that is functional and desirable.

It says nothing about customisation.

“Our Mission

“Create a User interface so that OpenOffice.org becomes the users’ choice not only out of need but also out of desire.”

http://blogs.sun.com/GullFOSS/entry/project_renaissance_kick_off1

I doubt they will follow the ribbon, but we’ll see.

@Roy: it’s about providing a better default UI, not about letting people tweak it more.

What is depressing is that Sun appears to now be following Novell features – witness the recent announcement on UI refresh; when Novell have already been working on XML UI definitions.

Somebody needs to knock Sun and Novell’s collective heads together.

Ted Haeger is 1 person. Jeremy Allison is 1 person. There was also one other guy from SAMBA team that left. That’s 3 people total that left because of the deal.

By some definitions, that could be considered a lot, but not by my definition.

Were there more that left? How many more? Who?

Unless someone can shine some light on those questions, we can’t really assume that more than those 3 left due to the MS/Novell deal.

As far as quality of the Go-OO team: the (7 of 12) names I recognize on the Go-OO team roster are high quality developers.

What does “a lot” mean in this case? It could mean 3 or 4 for all you know.

Is that an opinion or fact? Did you know that OpenSUSE’s big evangelist (Ted Haeger) left because of the secrecy around the Novell/Microsoft deal?

Also, the SUSE engineers weren’t the ones working on Go-OO, were they? Probably not, so it’s still irrelevant to the quality of the Go-OO team/patches.

We don’t know the answer to do.

Also, the SUSE engineers weren’t the ones working on Go-OO, were they? Probably not, so it’s still irrelevant to the quality of the Go-OO team/patches.