Slashdot Mirror

← Back to Stories (view on slashdot.org)

Open Source Sofware Policies And Politics

Posted by timothy on from the benefit-the-commonwealth dept.

Jason Keiber writes "I work at the Center for Strategic and International Studies (CSIS), a think tank in D.C., and I recently compiled a chart that provides information on the number and type of Open Source (OS) software policies and legislation considered by national, regional or local governments around the world. It looks at whether the policy or legislation mandated the use of OS, expressed a preference for OS software, encouraged its use or commissioned research into OS software. General purchasing decisions were not included. This is a work in progress, but seeing how I was having diminishing returns in my research, we decided to post it and welcome comments."

8 comments

  1. Great stuff by Qwavel · · Score: 2, Interesting

    Appears to be very comprehensive and well documented.
    Thanks to the author.

    I've noticed in the past that Canada is remarkable for its absense from this whole debate. Note that Canada isn't even mentioned in this document.

    1. Re:Great stuff by Tezkah · · Score: 2, Funny

      we're too busy trying to stay warm, eh?

  2. skolelinux by ZorroXXX · · Score: 3, Informative
    One project not mentioned in the report is skolelinux (school linux).

    This is fair enough since there is no offical policy of having to use it, but the project is partially financed by the Norwegian education department, Utdannings- og forskningsdepartementet.

    --
    When you are sure of something, you probably are wrong (search for "Unskilled and Unaware of It").
  3. Neat project. by einer · · Score: 2, Interesting

    Thanks for releasing your work. I think it would be useful if someone produced a website with updated information. If only for searchability.

  4. Canada and other feedback by Anonymous Coward · · Score: 0

    This is the author of the table here. Thanks for the feedback! We just heard from someone in Canada's Chief Information Officer Branch pointing us to their policy, which is pretty accessible and clear. I missed their policy just because the type of searches I was using. The table is updated and source info provided. All the feedback on this is welcome.