11.06.07
Posted in Novell at 9:08 pm by Dr. Roy Schestowitz
Richard Seibt seems to have found a new role, which is possibly just a casual or part-time occupation. Regardless, he is no longer involved with Novell, based on the following new bit of text.
Richard Seibt currently focuses on Open Source projects and serves as an Advisor to Open-Xchange, Inc. Previously, Richard served as CEO of SUSE Linux as well as President of Novell Europe, Middle East and Africa (EMEA), where he was responsible for leading all aspects of Novell’s operations in EMEA.
David Patrick seems to have quietly left, but it doesn’t say when. Admittedly, this may have happened quite some time ago.
In conjunction with the funding, Xkoto named David Patrick as the company’s new CEO. Patrick was previously vice president and general manager of Waltham-based Novell Inc., which he joined in 2003 as part of Novell’s acquisition of Boston-based Ximian Inc., where Patrick was president and CEO.
It remains interesting to see the movement of high-profile figures at Novell. Quite a few of them left some time in the past year. The list below is very incomplete, but it gives a sample of stories we have covered.
Related items:
Permalink
Send this to a friend
Posted in Asia, Novell at 2:24 pm by Dr. Roy Schestowitz
Shortly after major reorganisations in India, Novell closes down its branch in Israel as well.
Novell Israel Software Ltd. has been operating for 12 years, and its activity will be transferred to REL Ltd., the company’s local distributor.
We are yet to see if rumours about 1,100 jobs being axed are true.
Permalink
Send this to a friend
Posted in ECMA, Microsoft, Office Suites, Open XML, Standard at 12:31 am by Dr. Roy Schestowitz
Recall the earlier post about Microsoft not committing to even its own proprietary ‘standards’. Now, read the following article from CIO.com, which is a reputable source.
Whither OOXML?
[...]
Strangely, however, Microsoft appears to be soft-pedaling its own standard. At GOSCON last week there was a panel on document formats, with reps from IBM, Sun, Adobe, and Microsoft present. Each of the company representatives got to speak for five minutes and present his company’s perspective on document formats.
In his presentation, Matusow appeared to be backing away from OOXML as a key technology. If you look at the slide he presented …
…you can see that the positioning now is that the tool is key, and the document format secondary, which, to my mind, is a bizarre assertion, although it’s one that aligns with a positioning that, above all, must keep Microsoft’s tools in a predominate position.
It appears to me that, having realized that the force-feeding of OOXML into an international standards body is problematic, Microsoft is now trying to present a soft TCO story which emphasizes sunk costs and pre-existing product versions as a reason to stay on the Microsoft path, along with an incomprehensible assertion that two document standards would be a good thing (this last is the most oddball position of all; how can anyone state with a straight face that the world would be well-served by having two incompatible editable file formats?).
Permalink
Send this to a friend
11.05.07
Posted in Finance, Free/Libre Software, GNU/Linux, Microsoft, Novell, OIN, Patent Covenant, Patents at 9:23 pm by Dr. Roy Schestowitz
Here is a new article that advises open source developers to fight fire with fire. Is it clever? Probably not.
The United States patent and legal system has turned into a battlefield where companies and technology developers can be attacked. Open source and free software developers have historically ignored this secondary battlefield, focusing instead on the primary battlefield of development and proliferation of their project. This omission leaves open source projects and individual developers vulnerable to patent infringement lawsuits. By creating its own defensive patent portfolio as commercial companies do, the open source community can arm itself for this battle.
OIN definitely comes to mind here. That’s what everyone should have done. Novell, however, was too vain to only offer its portfolio to OIN (which is did). It took a shot at the trolls and then also shot itself in the foot when it signed a ‘protection’ deal and exchanged patents with Microsoft.
The following new article on the “strange bedfellows” describes how Microsoft and Novell liaised to compete. But who against? Each other? Probably not, they both fight against common rivals and Microsoft is likely to eliminate Novell when Novell’s hand is no longer useful. Microsoft uses Novell against Linux and Novell uses Microsoft against… well… GNU/Linux, apart from SUSE Linux — for now.
Here is Novell’s take on the relationship with Microsoft.
“There’s always that desire to do what’s best for the relationship, but I want to make sure what I’m doing is helping my company,” said Novell lab manager Suzanne Forsberg.
Good job, Novell. Great job. Not helping Linux, but only helping Novell at the expense of Linux. Patent deals are only good for Novell, and their benefit won’t last for much longer. How foolish a move.
Hopefully, Microsoft will stop giving Novell its ‘precious’ Linux ‘coupons’. Then, Novell will wake up and realise what a mess it has gotten itself into, along with others. Maybe Novell can still escape this deal somehow, or at least reduce the damage done.
Image from Wikimedia
Permalink
Send this to a friend
Posted in Deception, Formats, FUD, Microsoft, Office Suites, Open XML, OpenDocument at 8:53 pm by Dr. Roy Schestowitz
OpenDocument Foundation != ODF Advocates
It was less than a week ago that we complained about a pattern in eWeek. This pattern apparently continues to live on unaltered. Journalism is biased and unbalanced, so this ought to make everyone worried.
To be fair, the latest FUD comes from different directions, not just eWeek. This time it’s OpenDocument format which grabs the spotlight and it’s actually a site dedicated to squashing FUD that rebuts.
So to sum up – really, Mr Gilli [should be "Galli"], stop trying to make out there’s a major controversy and massive fighting amongst the Open Document Format advocates, because in reality there is none. The only thing which has happened is that a from what I can tell extremely minor participant in the Open Document Format committees has basically gone away in a hissy fit because they didn’t get their own way – that’s how I personally see it anyway.
An observation has just been made and it is particularly interesting. Quotes from Microsoft (on ODF) are aligned against the words of the Foundation as though they are conflicting and peer-balancing views. They are not. The Foundation wants funding from CIOs. Bashing ODF is one possibility for achieving this. Microsoft wants to maintain a proprietary format which is nothing but a matter of its financial interests (by its own admission). At the end of the day, as far as standards go, it’s all about the money. It is neither about the consumer’s needs, nor is it about the requirements set by governments.
Image from Wikimedia
Permalink
Send this to a friend
Posted in GNU/Linux, Hardware, Microsoft, OLPC, Windows, Xandros at 8:31 pm by Dr. Roy Schestowitz
We have already mentioned the ASUS Eee a while back. We talked about its uncomfortable technical assocation with Xandros. Ars Technica, among other high-profile publications, characterise Asustek’s choice of Xandros Linux as a loss to Microsoft. It’s not entirely the case however. Here’s what one of the most recent articles says:
Intel wins, and Microsoft loses
Thanks to its combination of Intel hardware and a non-bloated Linux install, reviewers found that Asus’s little laptop performs just as well as much larger and more expensive Windows notebooks. And the company spent enough time tweaking the unit’s default Linux distro that Windows users will supposedly feel right at home.
If you look closely, you’ll find that parts of the interface in this variant of Xandros were significantly changed. They almost perfectly mirror the looks of Windows XP. The artwork’s similarity makes the resemblance uncanny (see this video and judge for yourself). This makes the software used sensitive not only to software patents — however negligible they may be — but to other types of ‘violations’. What were they thinking?
Here is why Linux was chosen:
Asustek decided that the Windows operating system was out of the question. The licensing costs would have been the most expensive part of the computer. So it decided to use Linux and build its own user interface, and that became the most time-consuming part of the project.
It is clear, based on another product from Asus, that the company can handle other distributions of Linux or even roll its own. Just consider this recently-unveiled product for example. It doesn’t use Xandros. I know this because I’ve inquired with sources that are close to the company.
”Asustek ought to re-consider its selection process and choice of this KDE-based distribution.“Sadly enough for the Eee, Asustek chose Xandros Linux to work with. Xandros is among those that send Microsoft royalties for the use of Linux (probably per units that is sold, which contradicts the ideology of Free software). Xandros was virtually ‘bribed’ by Microsoft to play along with the ‘mythical patent plot’. Xandros betrayed the very same people that gave it 20+ years of work (GNU and Linux code).
Asustek ought to re-consider its selection process and choice of this KDE-based distribution. The next models of the Eee will be out early next year. There’s time to accommodate underlying changes. There are many other (and better) options if the company insists on using Linux. These options are likely to be less expensive, too. Microsoft has already given discounts to ‘fight’ this Linux threat, but that’s not surprising. Just look what happened in Nigeria last week.
Whether the Eee is worth buying or not, that’s up to the average consumers, who probably don’t know (and could not care less) about the behavior of Xandros. The least one can do is making all this information public and educating/advising buyers. There are several other low-cost laptops that come with Linux preinstalled. None of them (with the exception of SUSE in Dell China and SUSE in Lenovo) is plagued by the ‘Microsoft Windows/patent tax’. Definitely not OLPC, which serves a charitable cause.
Permalink
Send this to a friend
Posted in GNOME, GNU/Linux, Mono, Novell at 2:10 pm by Dr. Roy Schestowitz
Here is an interesting nugget of information. Slated, a reader of this Web site, wishes to share his new discovery with us.
I was horrified to discover the following, just moments ago:
~]# yum update
[snip]
--> Processing Dependency: libbeagle.so.0 for package: yelp
”Therefore the core of Gnome is now Mono dependent, just as I predicted it would eventually become.“As you may or may not know, Novell’s Beagle search tool is built on Mono technology, and Yelp is Gnome’s built-in help system (i.e. a core part of Gnome). Therefore the core of Gnome is now Mono dependent, just as I predicted it would eventually become.
It’s hardly surprising that this infestation comes to us via Novell, since Miguel de Icaza is deeply connected to all three entities; Novell, Gnome and Mono. And again as you may or may not know, Icaza is a hair’s breadth away from being a Microsoft MVP in his activities, regularly attending Microsoft developer conferences and private meetings. Indeed, it would not at all surprise me if de Icaza had MSCE certification by now.
I’m going to blog this, but before I do, I’ll need some confirmation. Specifically: Every build is unique to the build host, and this version of Yelp is built by a third party who maintains recent versions of Firefox for Fedora Core 6 (Fedora’s /official/ Firefox release on FC6 is stuck on the 1.x branch. They only maintain Firefox 2.x for Fedora 7 and above).
Since Yelp is also dependent on Firefox (it uses Gecko) then a Firefox update pulls in a Yelp update by dependency, and the version of Yelp required to utilise Firefox 2.x support libraries is different from the official 1.x release for FC6. Thus the maintainer must also rebuild and release newer versions of Yelp on his repo, to satisfy that dependency.
The only Fedora 7 system that I have is a headless server, and thus devoid of many things like Firefox and Yelp, but I might easily assume that the official Fedora 7 builds of Firefox and Yelp do also pull in libbeagle as a dependency. I’ll have to verify.
It is possible that this third party has enabled a configure option that is not the default. Even so, I am deeply troubled by this discovery, since it is at least suggestive of the future direction that Gnome intends to follow – just as I suspected – with Mono fully integrated into Gnome. The mere fact that such a configure option is even there at all, would suggest that there is a concerted effort to poison Gnome with Mono at the core developer level.
FYI: The third party repo is here:
http://dribble.org.uk
I’ll be contacting the repo maintainer today, to ask him what’s going on, but I suspect he’ll be blissfully ignorant of the problem, if he’s running an automated buildsystem. I’ll also check the SRPM; the spec file may have comments that reveal the truth.
As a side note; I would just add that this repo maintainer is also in violation of Mozilla Corporation’s trademark policy, since he is distributing a modified build of Firefox that retains the Firefox® trademarked name and logo. Between encumbered components like Mozilla products and Mono, the so-called Free Software tree is being slowly poisoned, and there doesn’t seem to be many who care this is happening.
My instincts tell me that this is a very sad day for the Gnome project; the turning point at which Gnome essentially became Microsoft property.
This seems to shatter Jeff’s argument, after he requested a correction. For all it seems, GNOME is indeed becoming dependent on Mono.
Update: mind the following ongoing discussion (ignore the trolls too)
It seems like it’s getting harder and harder to avoid Microsoft IP, thanks to people like you and de Icaza. Thankfully there are those who are prepared to do the work to undo the damage you’re doing.
And even if Gnome /does/ become infested with Mono, that’s no big deal, right? After all, Mono /is/ “Free Software”, isn’t it? And it has /nothing/ whatever to do with Microsoft, and I’m sure Microsoft /will/ keep their non-legally binding “Reasonable And Non-Discriminatory” “promise”, right Jeff. Microsoft would /never/ dream of using their IP claims to undermine Free Software, now would they? Nor would they ever make exclusionary deals to “protect” /one/ GNU/Linux vendor from .NET patent litigation, but not others … right?
Oh wait…
So once you’ve finished poisoning the Free Software tree with encumbered Microsoft technology, just make sure to send me the invoice, so I know who to write the cheque out to. I wouldn’t want to be caught running an “illegal” GNU/Linux distribution without paying Microsoft the correct “protection” fee, now would I?
Permalink
Send this to a friend
Posted in ECMA, Formats, Microsoft, Novell, Open XML, OpenDocument, Standard at 5:26 am by Dr. Roy Schestowitz
“Nothing in life is to be feared. It is only to be understood.” –Marie Curie
An anonymous reader contributes the following piece of analysis.
Microsoft benefits from standard bodies, then breaks/drops the standards
This is what Microsoft does, and proof of how much respect Microsoft has for standards and standards bodies: When it best suits its interests, it relies on ECMA (replace ECMA with any standards body) as has been the case with MSOOXML. On the other hand when ECMA standards are supported by the competition (like Mozilla and Javascript/ECMAScript), they try to break them (Extend, Embrace, and Extinguish) or come out with something different and utterly incompatible.
Links of interest:
Microsoft Mozilla Disagree Over JavaScripts Future
Open Letter to Chris Wilson [of Microsoft]
Brendan Eich, the creator of JavaScript, writes:
“The history of ECMAScript since its beginnings in November 1996 shows that when Microsoft was behind in the market (against Netscape in 1996-1997), it moved aggressively in the standards body to evolve standards starting with ES1 through ES3. Once Microsoft dominated the market, the last edition of the standard was left to rot — ES3 was finished in 1999 — and even easy-to-fix standards conformance bugs in IE JScript went unfixed for eight years (so three years to go from Edition 1 to 3, then over eight to approach Edition 4). Now that the proposed 4th edition looks like a competitive threat, the world suddenly hears in detail about all those bugs, spun as differences afflicting “JavaScript” that should inform a new standard.”
It reminds me too much of the way Microsoft has recently used ECMA in order to advance their competing office format and tried to avoid/derail adoption of the (truly) open standard already approved by ISO: ODF/ISO26300.
”…they will for sure “break” the standard or drop it altogether in order to keep its monopoly…“So, even if the ISO had passed MSOOXML as ISO standard, or if it eventually does so (remember there will be a “political” ballot held in February 2008 in order to decide on MSOOXML being granted an ISO Standard, as opposed to the previous “technical” one, where MSOOXML failed miserably despite Microsoft attempts to stuff the technical committees and other various maneuvers intended to hijack the process) This recent ECMAJavascript example should serve as proof that, should at any time become convenient for Microsoft to disengage from that format in the future, they will for sure “break” the standard or drop it altogether in order to keep its monopoly and lock-in on the application market in question (In ECMA case, it is Internet Browsers, in the MSOOXML case, it is Office Productivity Suites).
Mind the following previous coverages of ours:
The first item shows that Microsoft hasn’t strong intentions of sticking to its own ‘standards’. The second is another quick analysis involving this recent development that revolves around JavaScript. It was only about a week ago in this Web site that I said I cannot trust Chris Wilson. It finally turns out that these suspicions were justified.
We have covered Microsoft’s perversion of Web standards many times before and Novell’s role in this mess is made most apparent because of their Silverlight support. They lend Microsoft a hand and essentially serve as a GPL proxy at the same time.
When it comes to ‘extension’ and corruption of well-established consensus, it’s not just the Web, let alone OOXML. Think about HD/JPEG. As we have argued in the past, Microsoft will possibly have MS-DRM ‘addons’ as soon as this direction suits its financial interests. The same goes for XPS, so let’s keep our eyes open.
Permalink
Send this to a friend
« Previous Page — « Previous entries « Previous Page · Next Page » Next entries » — Next Page »
Content is available under CC-BY-SA