Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Government Open Source Software IT

India Mandates Use of Open Source Software In Government 64

jrepin writes The Indian government announced a policy yesterday that makes it mandatory to use open-source software in building apps and services, in an effort to "ensure efficiency, transparency and reliability of such services at affordable costs." The new policy (PDF) states that all government organizations must include a requirement for their software suppliers to consider open-source options when implementing e-governance applications and systems. The move will bring the Indian government in line with other countries including the US, UK and Germany that opt for open-source software over proprietary tools.
This discussion has been archived. No new comments can be posted.

India Mandates Use of Open Source Software In Government

Comments Filter:
  • This is it! (Score:3, Funny)

    by Anonymous Coward on Monday March 30, 2015 @09:20AM (#49370239)

    This is the year if Linux!

  • by Anonymous Coward

    Open source can be desirable. However, as we've seen in the recent acquisition of FoundationDB by Apple, without a strong foundation to serve as a home for the project, open source software is in danger of both poor code quality or being taken private and yanked by a proprietary buyer.

    • by Anonymous Coward

      It can't be taken propriatory if it's GPL.

      • by new_01 ( 4014887 ) on Monday March 30, 2015 @10:03AM (#49370537)
        There's nothing stopping the copyright holders of a GPL'd project from taking it proprietary. It's not much different than if the people running a permissive licensed project (BSD/MIT) decided to take it proprietary. Everything up to that point will still be available barring any patent issues. If one of the copyright holders decides they don't want their code proprietary then the project leaders can just rewrite their portion of the code and still take it closed source.
        • by Grishnakh ( 216268 ) on Monday March 30, 2015 @11:14AM (#49371199)

          There's nothing stopping the copyright holders of a GPL'd project from taking it proprietary. It's not much different than if the people running a permissive licensed project (BSD/MIT) decided to take it proprietary. Everything up to that point will still be available barring any patent issues.

          Two points:

          1) As you said, this doesn't remove the actual project from accessibility in the FOSS-sphere. You just can't have any new versions that the copyright owners decide to publish under a proprietary license. You can still use the existing code all you want, and you can fork it too if you want.

          2) This isn't really a big fear among people. Honestly, how many times has this happened? The advantage of GPL over BSD licenses is that with GPL, only the actual copyright holder can do such a thing. With BSD, anyone can do this, so you have cases like Kerberos, where a giant company with lots of resources grabs some FOSS code, "extends" it with proprietary extensions, and then pushes the new version so it's effectively been hijacked. This can't happen with GPL; there, the big corp would have to buy the copyrights from the original holders (which may be very difficult if there's a lot of contributors; with Linux (kernel), for instance, it's probably impossible to get all the contributors to agree to selling or even to a license change to GPLv3), before they could pull such a move.

          • Re: (Score:3, Interesting)

            by new_01 ( 4014887 )
            Yep, good points all around. The GPL does constrain the amount of people that fork a proprietary version. I've always been torn on the benefits of one or the other. The BSD license proponents would say that proprietary forking is a net benefit if it means more people are on a similar platform. I have noticed that FreeBSD is used quite a bit in proprietary realms, but it doesn't seem to detract from FreeBSD much. However there are great benefits to the share-alike idea the GPL promotes. I suppose if a projec
            • by Anonymous Coward

              I think it depends on the project and its development model.

              A big enough open source project will never really be at risk of hijacking because the community exists to carry on a free fork.

              A smaller project, though, especially if the core team can be hired on to work on the proprietary fork, is more at risk.

            • I agree with the AC who responded here. I will point out, however, that the BSDs were around before Linux, yet Linux (kernel) is the one which now powers most of the world's smartphones, countless embedded devices, and countless servers (including most webservers), plus a fair number of desktop computers. By contrast, I've never actually seen FreeBSD in use anywhere personally. I know Hotmail used to run on it more than a decade ago, and that's all I can think of; I sure don't see it in any embedded syst

          • by Phillip2 ( 203612 ) on Monday March 30, 2015 @03:53PM (#49374283)

            "How many times has this happened"

            MySQL is the obvious example, I think. It can happen with GPL, but it can only happen with the agreement of all the copyright holders, which is, in practice, unlikely. So, for instance, the linux kernel is unlikely to ever be released under any license other than GPL because there are so many copyright holders. Projects with a single copyright holder, usually through a copyright assignment policy could be relicensed.

    • Open source can be desirable. However, as we've seen in the recent acquisition of FoundationDB by Apple, without a strong foundation to serve as a home for the project, open source software is in danger of both poor code quality or being taken private and yanked by a proprietary buyer.

      true. however experience has shown that ALL software (open and propitiatory) are subject to crude work, poor support, and/or NSA nuggets

    • by iamacat ( 583406 )

      Huh? FoundationDB was closed source. The company published some supporting open source projects on github. Those are surely mirrored and will be reuploaded by others. If a truly open source database like cassandra was taken down by primary contributor, others would just take over.

  • "Consider" (Score:5, Informative)

    by Anonymous Coward on Monday March 30, 2015 @09:29AM (#49370295)

    The devil is in the detail - a requirement to "consider" open source software is not the same as mandating open source software.

  • And no backdoors (Score:3, Interesting)

    by Anonymous Coward on Monday March 30, 2015 @09:34AM (#49370327)

    You mean software without the NSA 5-eyes backdoors?

    Face it, who the f*** wants US made kit when they're talking about compulsory backdoors, and its clear there may be a lot of backdoors in their kit already present.

    It's not just the intentional backdoors, US companies report their zero day vulnerabilities to the NSA, and they use them in things like Stuxnet, so even buying kit from decent careful closed-source US companies is a risk.

    If they go ahead an eliminate encryption, then technically no business in the world will be able to use US made kit, because they'd be exposing their business secrets, their financials details, their confidential customer records, everything to everyone.

    • by Anonymous Coward

      That hasn't stopped them from pirating all the Microsoft products they have been using all these years. India's level of respect for copyrights rivals China's.

  • by Chacham ( 981 )

    This open source policy is open for comments. :)

  • All that is needed is a rule that all the code that is required to fulfill a government requirement is open to inspection.

    • by bobbied ( 2522392 ) on Monday March 30, 2015 @09:51AM (#49370445)

      All that is needed is a rule that all the code that is required to fulfill a government requirement is open to inspection.

      You know, that's a great idea except... Usually there is no way to map from the source code you are given to the executable you where provided unless you have instructions on how to *build* the executable for your self.

  • by Anonymous Coward

    Not trying to be a Debbie Downer, but there are just some functions that are not in the open source world:

    1: Active Directory. Sorry... OpenLDAP does not scale well, and would fall flat on its face if trying to deal with hundreds of thousands to millions of objects.

    2: Exchange. Yes, E-mail has historically been handled by UNIX... but messaging is more than E-mail and requires servers with replication capabilities. Other solutions just are not going to scale.

    3: Managing desktops. Show me a solution th

    • Re:Good luck... (Score:5, Informative)

      by Anonymous Coward on Monday March 30, 2015 @09:54AM (#49370469)

      #1: AD isn't necessary except to do things the way AD wants them done. They don't have to be done that way. The only thing I've EVER had told me that AD did that wasn't replaced by SAMBA was to undo the dumbfuck way Windows treats a computer, where it wants things installed on the C: drive and locally installed with the registry set up. That's not what's needed, but it only exists to undo some of the dumb ideas that were implemented by Windows. But you don't have to use AD to undo them: you don't require it to operate outside its usage. And then AD isn't needed.

      #2: Exchange doesn't scale anywhere near as well as the UNIX stalwarts. Even MS found they couldn't do it without massive and specific effort. You have no chance.

      #3: UNIX manages desktops fine, better than Windows, because it was always a multi-user, non-owned user system, unlike Windows. So there's nothing to this "point" either.

      #4: There's massive amounts of stuff to do backups for UNIX. Who knows what the hell you're thinking of to make you think Windows does it better.

      #5: Managing and delegation of privileges are better on UNIX and Linux especially than it is on Windows. They're equal when you're talking about out-of-the-box normal privileges, excepting the Windows system wanting to execute anything, even if the execute flag isn't set, if it THINKS it should be executed. You have to do extra work to stop that, and you don't have to do that with Linux.

      #6: NFS has no problems doing what you need to do with the filesystem too. Just because you don't know what they are doesn't make them nonexistent.

      #7: It's easy-peasy to do what you demand on Linux. Issue a key to log on that only allows access 9-5, only from pre-configured systems, and always encrypted communication.

      Not to say closed software hasn't got a place or doesn't work, it just doesn't work the same way. Between other closed source software or open sourced software. And demanding that what you do on one platform must be available on another otherwise "It just doesn't replace my system" is ridiculous and self-confirming fake incompatibility.

      But demanding that just because the way you do something isn't done on another doesn't mean that the usage you want isn't available. It just isn't done with the same command as you're used to.

      • #4: There's massive amounts of stuff to do backups for UNIX.

        That's odd.. I use Linux Mint/ddrescue to backup/restore images of Win OS partitions/disks all the time. WIndose doesn't have anything even close. I can even mount those NTFS file images as partitions and modify the contents as needed. Have you tried to mount a Ext-3/4 FS on windows lately?

        M$ has a nasty habit stripping out long established features, obfuscates, cripples/breaks, and/or removes them, then monetizes it as a paid feature. I.E. Net

    • by ruir ( 2709173 )
      If you do not know how to do it, others might...nevertheless the article is quite vague, and full of backdoors. I could very well maintain all the desktop environment in windows because "it works better", and only provide applications and servers in Linux.
    • Re:Good luck... (Score:5, Insightful)

      by bobbied ( 2522392 ) on Monday March 30, 2015 @10:09AM (#49370595)

      Gee, most of what you claim is not possible truly IS possible on Linux/Unix solutions IF you know what you are doing.

      With the possible exception of the Active Directory vrs OpenLDAP gripe of yours (and I'm just not prepared to argue that point with you, I think it's possible if properly managed and configured that OpenLDAP would scale just fine) everything you complain about are not issues without solutions, but solutions that you may not understand how to setup and use.

      Linux generally has solutions to the above problems which do work and work well for the back of house stuff. What Linux doesn't have though is the developed "tribal knowledge" of skilled administrators who understand the solutions and how to properly implement them. (Not that the tribe of Windows administrators always understand their OS of choice either.)

      Your complaints seem more born of frustration with people who didn't know what they where doing or what tools did what you are accustom to seeing than being actual limitations with Linux. Or perhaps you have had some bad experiences with Linux because somebody thought it was going to be cheaper to forget the license costs of Windows and run some half baked Unix solution instead. I can tell you that if you do the Linux thing because it is cheaper up front, you are sadly mistaken and wasting your time and money. Usually Linux requires as much budget up front as the Microsoft solution and only saves you money in years to come. Much pain is caused by half understood, improperly implemented and under funded efforts in either Microsoft or Linux worlds...

    • With UNIX, there is god and the peasant.

      If you set sudo up correctly (i.e., nobody has unrestricted use of sudo and the admins are expected to use su instead.) you have God(s), the nobility and the peasants. The nobility, of course, consists of those users who are allowed limited access to sudo to manage their own boxes, but their privileges don't include doing the really dangerous stuff and the peasants neither have nor need even that limited access to elevated privileges.
  • The govt mandates using open source but one of the largest online repositories of Open Source Software, GitHub, is still blocked in India because "cut and paste services" are *very dangerous*
    http://t.co/P0f3LVj2tD [t.co]

    • Re: (Score:1, Funny)

      by Anonymous Coward
      Not a problem, they'll offshore the work to H-1Bs in the US
    • Wow that article is like reading an Onion parody. To be clear, the article states websites were blocked on advisory by the "Anti Terrorism Squad." Allow me to cut and paste the entire quote because it is so stunning everyone should see it.

      "These [sites] are all providing very dangerous kind of cut and paste services..You can take code, cut it, paste it, remove it, delete it," said one government official who requested anonymity.

      That just blows my mind.

  • His friend Warren Buffet didn't want to trust software for earnings in the long term.

  • The new policy (PDF) states that all government organizations must include a requirement for their software suppliers to consider open-source options when implementing e-governance applications and systems.

    Yeah, we considered it for several seconds. But we decided against it.

  • if it's developed, implemented, and maintained by straight, white, god fearing Christians.

  • That's news to me... I'm watching about 2000 machines all running all sorts of close-source stuff with equivalent (and sometimes better) open-source stuff is available. Example: Oracle LDAP

  • Some nerds have now sold them this idea, but when it eventually comes to deployment, everyone will realize "Oh my god the desktop is buggy, and LibreOffice constantly screws up the formatting of documents. We can't actually use something like this." After that, there will just be the ugly flag symbol and a spinning pearls animation when people start their computers.

    Any counterarguments?

  • Unfortunately, Indian schools still require learning to code with Turbo C++, which is ancient and incompatible with any modern open source code.

    Sad but true: http://google.com/search?q=Ind... [google.com]

Avoid strange women and temporary variables.

Working...