Commentary

Dave Methvin
 

Microsoft Copy-Wrong Yet Again

It was just last month when Microsoft got into an embarrassing incident with a utility they offered in their store site -- it was filched from open-source code. This month we find that the design and code for the MSN Juku service offered in China was mostly copied from a small startup named Plurk.

It was just last month when Microsoft got into an embarrassing incident with a utility they offered in their store site -- it was filched from open-source code. This month we find that the design and code for the MSN Juku service offered in China was mostly copied from a small startup named Plurk.How could this happen? Well, I covered some of the reasons a month ago. The work was done by a Chinese contractor, not by Microsoft employees. That makes a lot of sense; the product is intended for the Asian market and the contractor would at least theoretically have a better handle on the cultural issues involved. Microsoft has said that the copying that the contractor did was a violation of the contract that MSN China had with them, and I believe that. Yet the damage is done.

When I mentioned the issue in the previous blog entry, a commenter took me to task for "raising the tired old bogeyman of the foreign contractor." I don't think it's an exaggeration to say that the chances of this type of wholesale copying are higher with offshore developers, for at least a couple of reasons.


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Countries like India and China have historically had a lax attitude towards intellectual property. Given that background, it might be a somewhat innocent mistake by some low-level developer who thought it was fine to Google around for some code they could start from to get the job done faster. Developers generally don't see the the contracts, so it's management's job to make sure that the developers follow the terms of the contract.

Everyone knows that America is the king of litigation. There are a lot of negative implications of that, but one of the positive ones is that few companies would be foolhardy enough to attempt the wholesale copying that took place here. Even a low-level developer knows enough to think twice about copying most of the code and design from another site. Could this happen in a US company? Sure, but I don't think it's as likely.

Perhaps incidents like this are the "poisoned toys and toothpaste" moment of software development, spurring positive action to address the problem. Microsoft has certainly learned their lesson about contracting this year, and I'm sure they'll conduct even more oversight on projects they farm out to contractors.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links