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."

8 of 146 comments (clear)

  1. 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.

  2. 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
  3. 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.

  4. 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.
  5. 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.

  6. 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.
  7. 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!
  8. 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