Slashdot Mirror


India Cool to Microsoft Source Code Offer

indianseason writes "Economic Times, India reports on the failure of Microsoft to sign up the Indian government as part of the Government Security Program. The Print Edition carries a comment by an official: "... there was tremendous pressure on us to sign an MoU (memorandum of understanding) which would allow Microsoft access to all TDIL products (Technology Development for Indian Languages)." The government has gone ahead and put all the project initiatives in the public domain. TDIL recently released Indix : an engine for rendering Indian languages on linux."

37 of 146 comments (clear)

  1. So what's the problem? by Tsu+Dho+Nimh · · Score: 3, Insightful
    there was tremendous pressure on us to sign an MoU (memorandum of understanding) which would allow Microsoft access to all TDIL products (Technology Development for Indian Languages)." The government has gone ahead and put all the project initiatives in the public domain."

    They can still access all the technology ...

    1. Re:So what's the problem? by The+One+KEA · · Score: 3, Insightful

      The problem is that if they hadn't, M$ would have found a way to lock it up and prevent anyone from ever using it. Putting it in the public domain allows other OSes like Linux, Mac OS and the BSDs to utilize it.

      --
      SCREW THE ADS! http://adblock.mozdev.org/ Proud user of teh Fox of Fire - Registered Linux User #289618
    2. Re:So what's the problem? by flakac · · Score: 5, Interesting

      They can still access all the technology ...

      Uh, no, actually they can't. MS engineers are specifically prohibited from accessing much open-source software (in specific GPL'ed code), without first obtaining permission from the legal department. This is to avoid "contamination" of their source code base.

    3. Re:So what's the problem? by Anonymous Coward · · Score: 3, Informative

      Since when is Public Domain = GPL?

    4. Re:So what's the problem? by YU+Nicks+NE+Way · · Score: 3, Interesting

      Hmm...it would depend. We are forbidden to look at any GPL'ed code. BSD code is a grey area, and we need to consult with legal. If the indic language support is truly in the public domain, then we can certainly look at it.

      That said, I have trouble with the base story. We've had full support for all the Indic (Devanagari-based) languages since Windows 2000 and Office 2000 shipped. So I don't see why on Earth we'd need to license the Indian technology.

    5. Re:So what's the problem? by __past__ · · Score: 2, Insightful
      MS engineers are specifically prohibited from accessing much open-source software (in specific GPL'ed code), without first obtaining permission from the legal department.
      What a contrast to all the other, non-evil companies where developers are encouraged to reuse third-party code willy-nilly without having to care about the legal consequences.
    6. Re:So what's the problem? by xanadu-xtroot.com · · Score: 4, Funny

      We are forbidden to look at any GPL'ed code. BSD code is a grey area, and we need to consult with legal.

      Shouldn't you be fixing some bugs and not browsing /. if that all truly be the case??

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    7. Re:So what's the problem? by McAddress · · Score: 4, Funny
      This is to avoid "contamination" of their source code base.
      Imagine Darl McBride insisting all Windows users pay $699 to use it.
    8. Re:So what's the problem? by blibbleblobble · · Score: 2, Insightful

      "Imagine Darl McBride insisting all Windows users pay $699 to use it."

      Imagine the BSA insisting all Windows users pay $399 to use it.

    9. Re:So what's the problem? by jazuki · · Score: 2

      Regarding the assertion: We've had full support for all the Indic (Devanagari-based) languages since Windows 2000 and Office 2000 shipped. [YU Nicks NE Way]

      I seem to recall that only a subset of Indic languages use the Devanagari script. I know Bengali doesn't and I don't believe any of the Dravidian languages do. My uninformed guess would be this knocks out half of India. So, I can see what MS may have to gain from this kind of deal.

      Anyone have any information on this?

    10. Re:So what's the problem? by CondeZer0 · · Score: 2, Interesting

      OK, thanks for your contribution to /. misinformation.

      MS has used considerable amounts of BSD code in the past, and still does so, for a recent example(last week) see:
      http://www.deadly.org/article.php3?sid=20030927090 008

      You can also just do a strings of the ftp command on windows, for more details:
      http://www.everything2.com/index.pl?node=BSD%20Cod e%20in%20Windows

      The original windows TCP/IP stack was lifted directly from BSD too... and I'm sure there are many other examples that we will never know of.

      Oh, and there was zlib too, because when a hole was found in zlib MS Office and quite a few other MS products had to be patched:
      http://news.com.com/2100-1001-860328.html

      They have even publicly said that they think the BSD license is great, obviously as long as others use it and they can take advantage of it, I can't recall MS ever releasing anything under the BSD or any other open source license(no, "shared source" is _not_ open source).

      Still, as Theo says, if MS uses BSD/public-domain code it's great, that is the point of the BSD license, to improve the sorry state of the software quality in our world, if MS uses BSD code to make their software suck less, great that is what people that releases code under the BSD license want, to make software suck less, not to push any stupid political agenda.

      Best wishes

      \\Uriel

      --
      "When in doubt, use brute force." Ken Thompson
    11. Re:So what's the problem? by anandrajan · · Score: 5, Interesting

      Aaah, finally something about which I may actually know something.

      I speak and write Tamil. Characters are almost never merged in Tamil and at least to me, the script looks totally different from Devanagari scripts. This statement should hold for other South Indian languages such as Kannada, Telugu, Malayalam and a Pakistani Dravidian language Brahui (unless it uses a Devanagiri or other imported script).

      Perhaps the parent poster meant something else by character-merger which I didn't understand. Obviously there could be similarities due to proximate evolution which could be leveraged.

      --
      Anand Rangarajan anand@cise.ufl.edu
    12. Re:So what's the problem? by Haeleth · · Score: 2, Interesting

      > Parks and roads are in pub[l]ic domain.

      Depends where you live. In the UK, for example, roads are most certainly not public property; the street is a public right of way, but you do not have the right to stand still in it; that's a criminal offence known as 'obstructing the Queen's highway'.

      Public Domain, as a legal term applied to software, means "not copyrighted". GPLed software is copyrighted, and therefore is not in the public domain.

    13. Re:So what's the problem? by vidarh · · Score: 2, Insightful
      Bzzzt. Wrong. Try again. Public domain in this case refers to copyright, where it has a very specific meaning: it is the exact opposite of copyright. If a work is in the public domain, it is NOT copyrighted, and no copyright restrictions apply to it. Putting a work in the public domain means you are explicitly relinquishing your copyright protections. If you want to use a public domain work for commercial purposes, you can, as much as you want, including "making it properietary" if you are able to prevent other people from gaining access to the source.

      Comparing access to property and copyright is futile, since copyright was conceived specifically because ideas and information is so fundamentally different from property.

      Your comparison gets weaker, because parks and roads most certainly is not in the "public domain" in any sensible way. Parks and roads are owned property. Often they are owned by a national government, or a local government. Sometimes by companies or private individuals. But almost always there are clear property rights.

      An unclaimed territory would be mostly equivalent to public domain software - anybody could take it and claim ownership of it and do as they please with it. And yes, in that case, you could just occupy some space of it and start using it for your commercial purpose.

  2. Nice to see a government working as it should by Crashmarik · · Score: 5, Insightful

    The Indian government really managed to get the problem with microsofts shared source initiative. The only thing it does is create a constituency in a government or organization to promote microsoft products. It allows microsoft to get a bunch of your influential people, sign binding agreements with microsoft, and then get the potemkin village treatment of microsofts source.

    Nearly ten years have gone by with Security being a high priority at microsoft, look at the results.

  3. Windows source code, huh? by ezh · · Score: 5, Insightful

    According to recent talk of Richard M. Stallman at CERN, governments do not get Windows source code as such, but rather a means to look at it on Microsoft site.

    There is not way to determine whether what they are looking at is what really running on their computers, thus defeating the whole point of having that access anyway

    1. Re:Windows source code, huh? by flend · · Score: 2, Informative

      To be frank, the old real way they can know that the source code they have is actually running on their machine in unadulterated form, is to compile the source and then use this version on all of their machines.

      Whilst I guess a government could insist on this, reinstalling all machines after they'd be bought, presumably with Windows pre-installed, from the supplier, it would still be an undertaking.

    2. Re:Windows source code, huh? by pirhana · · Score: 5, Insightful

      Actually anybody with common sense can understand this fact. How many millions of lines of codes are there for windows and all the related software? just getting a "peep" in to this wont help you to determine whether you have back doors in it or anything for that matter. This is yet another hog wash from Microsoft. Software is not an object of voyeurism. You need to compile it and run it and look in to the source code extensively to get to know about it well. I am genuinely surprised that they got countries like China to subscribe this BS at all.

    3. Re:Windows source code, huh? by killmenow · · Score: 2, Informative

      I am in a relatively small organization. We re-image every PC we buy with a standard image of Windows 2000 Pro. Large organizations do this *all the time*.

      The undertaking is defining and maintaining the image. Re-imaging new PCs is trivial.

    4. Re:Windows source code, huh? by ojQj · · Score: 3, Informative
      This would only do it if you could also be sure your compiler doesn't have a backdoor of its own. Since I doubt their code builds anywhere other than in Visual Studio, even building the code yourself doesn't give you any guarantees.

      Disclaimer: Although clever, the idea of using a compiler to insure security holes isn't my own...

    5. Re:Windows source code, huh? by GigsVT · · Score: 2, Interesting

      But this is even worse, since the classic argument is that even with access to the source of the compiler, you can still be trojaned.

      In this case, you won't even have source for the compiler, which makes it trivial to trojan.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
  4. Third point's the kicker. by MickLinux · · Score: 3, Interesting
    Third, as the sources pointed out, if Microsoft's latest versions are so secure, they should be able to get third party assessment.

    Excellent point; and Microsoft should lose no time in calling up a well-trusted third-party security company to show that indeed Microsoft products are secure. Of course, it had better be a trusted company, because they don't want their source code getting out.

    Hmm... I wonder if I should send my resume to an industry-leading security company, such as @stake, immediately. I'm into document preparation, not security, but I should be able to learn the language reasonably quickly. ;->

    --
    Correct Horse Battery Staple: 72 bits of entropy. Enter "Correct H" into google. When it generates the phrase, that's
  5. Which Way? by 4of12 · · Score: 5, Insightful

    It will be interesting to see how the Indian government goes on this one.

    TDIL has value in making computers more accessible to much of their population. For some, this is a money-making opportunity to charge for access to the technology that will be deployed to a billion potential customers. For others, this is an opportunity to speed up introduction of technology to the country. It could be both.

    They could go with something like a GPL on TDIL that MS would detest, but would enable free software development in India, which later could be used as a platform by commercial firms in India for specific applications. But the government would not reap any immediate financial gain from this; only the long term gains from an increased tax base of a larger, faster growing economy in general.

    They could go with selling out to MS entirely, which would give the government more money in the short term, but would impede internal software development because it would necessitate all the Indian software developers acquiring MS specific tools to do their jobs and to compete with MS. Deployment of IT in the country would be less because it would be limited to those who could afford it.

    Possibly going with a BSD license would provide the biggest initial boost in software development in India, but the long term benefits are less clear.

    Personally, I'd welcome the many intelligent Indian programmers to the world of FOSS. Their contributions would help to make for improved quality and continued low cost for free software. Indigenous businesses in India would be in a better position to take more advantage of information technology and its productivity gains if there was both free software and many local programmers available for customizing it for business needs.

    --
    "Provided by the management for your protection."
    1. Re:Which Way? by iabervon · · Score: 4, Informative

      The Indian government would like to foster the growth of local computer companies with minimal employment requirements. They'd like it to be possible for an Indian company to be able to hire programmers who don't know any foriegn languages, which means that the computers have to support Indian languages conveniently. The people who produce the necessary software commercially, however, are likely to be competitors of such companies, and thus have no incentive to add this functionality. That's why the Indian govenrment had to produce it in the first place. At this point, they want to minimize the barriers to inclusion, so a BSD license is most suitable. The situation is much like that for Vorbis libraries, where even RMS has said that the BSD license is preferrable, since it helps to promote the free standard, which is more important than keeping the implementation free when embedded.

    2. Re:Which Way? by rifter · · Score: 2

      It will be interesting to see how the Indian government goes on this one.

      TDIL has value in making computers more accessible to much of their population. For some, this is a money-making opportunity to charge for access to the technology that will be deployed to a billion potential customers. For others, this is an opportunity to speed up introduction of technology to the country. It could be both.

      They could go with something like a GPL on TDIL that MS would detest, but would enable free software development in India, which later could be used as a platform by commercial firms in India for specific applications. But the government would not reap any immediate financial gain from this; only the long term gains from an increased tax base of a larger, faster growing economy in general.

      They could go with selling out to MS entirely, which would give the government more money in the short term, but would impede internal software development because it would necessitate all the Indian software developers acquiring MS specific tools to do their jobs and to compete with MS. Deployment of IT in the country would be less because it would be limited to those who could afford it.

      Possibly going with a BSD license would provide the biggest initial boost in software development in India, but the long term benefits are less clear.

      Personally, I'd welcome the many intelligent Indian programmers to the world of FOSS. Their contributions would help to make for improved quality and continued low cost for free software. Indigenous businesses in India would be in a better position to take more advantage of information technology and its productivity gains if there was both free software and many local programmers available for customizing it for business needs.

      While I agree that this is an insightful description of the situation at hand, I think it is funny you got a +5 insightful without reading the article.

      If you do get round to doing so, you will find that "how the Indian government goes on this one" is that they have put TDIL in the public domain. IF India Times is correct on this and not making the common mistake of Free Software License == Public Domain, it means that Free software and Microsoft can both use the technology without any restrictions whatever.

  6. Now's a good time... by GillBates0 · · Score: 3, Insightful
    to recap an an earlier story about the Indian President advocating OSS over Windows.

    "I am sure this is a first. The President of India has urged Indian IT Professionals to develop and specialise in OSS rather than Windows. To be noted is that he made the speech (look for the "Think Different" section) at the famous Indian Institute of Information Technology (India's foremost academic institution equivalent to MIT). Also he reminisces that his meeting with Mr.Gates were difficult due to differing views concerning OSS and Security. What should be noted about him is that he is not a politician, but a scientist and an independent thinker foremost."

    --
    An Indian-American Hindu committed to non-violent thought/speech/action alarmed by the global explosion of radical Islam
  7. In the public domain? not! by Anonymous Coward · · Score: 5, Insightful
    One would think that on slashdot the typical submitter would understand that publically available != public domain:

    This software is copyright (C) 2000-2001, NCST

    That ain't public domain. There's more, of course:

    All Rights Reserved except as specified below. Permission is hereby granted to use, copy, modify, and distribute this software (or portions thereof) for any purpose, without fee, subject to these conditions:

    (1) If any part of the source code for this software is distributed, then this README file must be included, with this copyright and no-warranty notice unaltered; and any additions, deletions, or changes to the original files must be clearly indicated in accompanying documentation.

    (2) If only executable code is distributed, then the accompanying documentation must state that "this software is based in part on the work of the IndiX system".

    (3) Permission for use of this software is granted only if the user accepts full responsibility for any undesirable consequences; the authors accept NO LIABILITY for damages of any kind.

    These conditions apply to any software derived from or based on the IndiX code, not just to the unmodified library. If you use our work, you ought to acknowledge us.

    That looks an awful lot like a BSD license...and is obviously not GPL!

  8. Indix? by IamTheRealMike · · Score: 2, Interesting

    Correct me if I'm wrong, but isn't Pango supposed to be able to render and edit Indian text correctly these days? I'm certain I've seen screenshots if GTK2 apps doing that

    1. Re:Indix? by rocketfairy · · Score: 3, Informative

      Pango is still pretty ugly in Devanagri (the Hindi script); Indix seems a little better at displaying conjoined letters, which are a big pain. I'm not sure of the status, but Pango was working on complex text layout, so the framework should eventually be better at laying out Devanagri.

  9. "Cool" in what sense? by Junks+Jerzey · · Score: 2, Informative

    "Cool" as in "agreeable to"?

    Or "cool" as in "less interested?"

    Yeah, RTFA. But what a lousy headline.

  10. Acess to ALL products? by nurb432 · · Score: 2, Interesting

    Isnt that a bit on the illegal side?

    "here i sell you a tool, but i get to look at EVERYTHING you do, and profit from it, regardless of its relation to the orginal tool.."

    Only a monopoly would even have the balls to demand such a concept.

    They need to be closed. Im not for governmental influence, but they have gotten out of hand and need to be terminated as a company.

    --
    ---- Booth was a patriot ----
  11. MS is hot on OSS by WindBourne · · Score: 4, Interesting

    They have been all over the place picking up all the OSS and coding initives that they can
    Project mercury was brought under .net, TRON yesterday.
    I wonder what China promised them?

    --
    I prefer the "u" in honour as it seems to be missing these days.
  12. What third-party certifier would they trust? by burgburgburg · · Score: 4, Interesting
    The article suggests that if the code was so secure, it could pass review by a third-party certifier and that would be sufficient.

    What organization is:
    a) smart enough to properly assess the security of the Microsoft code and
    b) independent enough to publicly fail them if their code wasn't up to snuff and
    c) acceptable to Microsoft?

    Without all three, you got nothing.

  13. Re: Quidquid id est timeo danaos et DONA ferentes by Mjlner · · Score: 2, Interesting
    ...the word in CAPS missing.

    For those of us whose latin is a bit rusty ;-): "Whatever it is, I fear the Greeks, even when they bring gifts."

    Words of warning uttered (in ancient Greek) by Laokoon as a warning to the Trojans when they found the wooden horse. The horse was, of course, the infamous Trojan horse, presented by the Greeks as a gift to the Trojans. The horse was full of Greek soldiers, who crept out of the horse in the night and conquered Troy from within.

    --
    Lemon curry???
  14. Don't read this post... by tjwhaynes · · Score: 4, Interesting
    as it contains code licensed under the GPL.


    /*
    * Structure of a directory entry
    */
    #define EXT2_NAME_LEN 255

    Copright Remy Card, Linus Torvalds

    Now that all the MS engineers are gone, I'll continue... :-)

    Hmm...it would depend. We are forbidden to look at any GPL'ed code. BSD code is a grey area, and we need to consult with legal. If the indic language support is truly in the public domain, then we can certainly look at it.

    Don't you feel that this is a ridiculous rule? Ok - if you read GPL'd code, you are now in the position that anything you write of similar functionality is "at risk" of being contaminated by this knowledge. I have to be careful not to view, say, any code in Postgresql as it might affect any coding decisions I might make in the future (I can feel someone about to post some Postgresql code in reply to this ...). That said, almost every piece of code contains the same ideas - maths, caching strategies, data transport. Coming from a scientific background, being able to build on the vast store of knowledge of those who have gone before me is a natural process. Having to walk the boundaries of copyright law, patents and other legal straight-jackets is a confining and ultimately unproductive method.

    Just where would we be today if we could treat source code in the same way we treat mathematics?

    Cheers,

    Toby Haynes

    --
    Anything I post is strictly my own thoughts and doesn't necessarily have anything to do with the opinions of IBM.
  15. Well, think about it: if YOU were India... by crazyphilman · · Score: 5, Interesting

    Would you go with Microsoft? Probably not.

    Consider this from the point of view of the Indian government. They can:

    A) Let Microsoft come in with low initial prices, taking over the Indian software market and then exerting absolute control later on, or

    B) Assign teams at whichever Indian college has the best research facilities, provide them copies of Linux and the BSDs, and have them roll out a purely Indian Linux and/or BSD that can be used across the board as an Indian National O/S. It could be completely pre-vetted for security holes, OpenBSD style, and it could be engineered to support all Indian languages natively alongside English, instead of having them as add-ons. Also it could be used throughout the entire Indian infrastructure, freeing them from any reliance on foreign concerns. Updates could come from the team that rolled it out in the first place. Couple this with a cheap homegrown computer, of course...

    Seriously. If you were in the Indian government, what would YOU do?

    --
    Farewell! It's been a fine buncha years!
  16. Wrong. by The+Cydonian · · Score: 5, Insightful
    We've had full support for all the Indic (Devanagari-based) languages since Windows 2000 and Office 2000 shipped.
    You probably know this, but let me clarify it for others:-

    Win2k had support for exactly two Indic scripts, Devanagari and Tamil. WinXP has support for four more, Telugu, Kannada, Gujarati and Gurmukhi. Till date, MS does not have support for Malayalam, Oriya, Bengali, Sinhala, Burmese or other Indic (that's 'South Asian', not just 'Indian', or 'Devanagari-based') languages.

    So I don't see why on Earth we'd need to license the Indian technology.

    And even in that, it's pretty shoddy; as anyone who's typed in Telugu/Kannada in MS Office will tell you, there's a mysterious space that gets added after the end of each word. Telugu/Kannada characters mysteriously change into boxes every now and then. Again, mysteriously, {Telugu, Kannada} characters change into boxes when placed along with {Tamil, Devanagari} characters on MSN. That's only TWO of the bugs I've sighted so far; trust me, there are many more.

    Your company knows about it and all others; I reported it by email to one of your personnel. Understandably, it's not one of your priorities; obviously, you have other, bigger markets to garner. Which, of course, is precisely the point here; if the source is open, concerned techie Indians can easily look into it and implement according to their needs and schedules, and would not be dependent on some faceless corporation's benevolence.

    While I'm not sure it was Indix that I saw in action, but I'll say this:- I've seen Kannada and Devnagari in Emacs, and it's a much much MUCH better rendering than what WinXP offers.

    And oh, before I end, you still use the Inscript keyboard layout and complex rendering algos in your Indic implementations, don't you? Guess who developed that, hmmm.