Slashdot Mirror


EU Report Advocates Pooling Open Source Software

bnoise writes "'European administrations should share software resources, a report published by IDA says'. IDA stands for 'Interchange of Data between Administrations' and is an European Commission initiative promoting the use of ICT in the exchange of information between EU administrations. The report extensively (147 pages) describes and comments Open Source Software licenses and promotes the use of source sharing among administrations and beyond. Its 'Legal Framework analysis' section alone is worth reading if you (still) don't know what license to choose for your next software development. Also from one of the authors: 'Study into the use of Open Source Software in the Public Sector' (June 2001)." ZDNet has a summary of the report, and the report is also available in non-PDF formats.

7 of 103 comments (clear)

  1. Open Source Development HOW-TO by Anonymous Coward · · Score: 5, Funny
    1. Introduction

    As everyone knows, Open Source software is the wave of the future. With the market share of GNU/Linux and *BSD increasing every day, interest in Open Source Software is at an all time high.

    Developing software within the Open Source model benefits everyone. People can take your code, improve it and then release it back to the community. This cycle continues and leads to the creation of far more stable software than the 'Closed Source' shops can ever hope to create.

    So you're itching to create that Doom 3 killer but don't know where to start? Read on!

    2. First Steps

    The most important thing that any Open Source project needs is a Sourceforge page. There are tens of thousands of successful Open Source projects on Sourceforge; the support you receive here will be invaluable.

    OK, so you've registered your Sourceforge project and set the status to '0: Pre-Thinking About It', what's next?

    3. Don't Waste Time!

    Now you need to set up your SourceForge homepage. Keep it plain and simple - don't use too many HTML tags, just knock something up in VI. Website editors like FrontPage and DreamWeaver just create bloated eye-candy - you need to get your message to the masses!

    4. Ask For Help

    Since you probably can't program at all you'll need to try and find some people who think they can. If your project is a game you'll probably need an artist too. Ask for help on your new Sourceforge pages. Here is an example to get you started:

    "Hi there! Welcom to my SorceForge page! I am planing to create a Fisrt Person Shooter game for Linux that is going to kick Doom 3's ass! I have loads of awesome ideas, like giant robotic spiders! I need some help thouh as I cant program or draw. If you can program or draw the tekstures please get in touch! K thx bye!"
    Thousands of talented programmers and artists hang out at Sourceforge ready to devote their time to projects so you should get a team together in no time!

    5. The A-Team

    So now you have your team together you are ready to change your projects status to '1: Pre-Bickering'. You will need to discuss your ideas with your team mates and see what value they can add to the project. You could use an Instant Messaging program like MSN for this, but since you run Linux you'll have to stick to e-mail.

    Don't forget that YOU are in charge! If your team doesn't like the idea of giant robotic spiders just delete them from the project and move on. Someone else can fill their place and this is the beauty of Open Source development. The code might end up a bit messy and the graphics inconsistant - but it's still 'Free as in Speech'!

    6. Getting Down To It

    Now that you've found a team of right thinking people you're ready to start development. Be prepared for some delays though. Programming is a craft and can take years to learn. Your programmer may be a bit rusty but will probably be writing "hello world" programs after school in no time.

    Closed Source games like Doom 3 use the graphics card to do all the hard stuff anyhow, so your programmer will just have to get the NVidia 'API' and it will be plain sailing! Giant robot spiders, here we come!

    7. The Outcome

    So it's been a few years, you still have no files released or in CVS. Your programmer can't get enough time on the PC because his mother won't let him use it after 8pm. Your artist has run off with a Thai She-Male. Your project is still at '1: Pre-Bickering'...

    Congratulations! You now have a successful Open Source project on Sourceforge! Pat yourself on the back, think up another idea and do it all again! See how simple it is?

  2. Love quote from ZD page by josh+crawley · · Score: 4, Insightful

    I just love the quote that ol' billG said.... here it is.

    "The so-called (Free Software Foundation)... says that these other countries other than the US should devote R&D dollars in the so-called open approach, that means you can never commercialise that software," said Gates.

    Well, umm, no shit BillG. As a government, would you spend your miney on a company in another country for proprietary software for internal matters, or put the money in developing better GPL/FSF type of software (where there is already base). So yes, the GPL keeps money (and code) out of your pocket.

    By the way billy, nice job on the DeToqueville (whatever) essay. You didnt pay much for it, did you?

  3. A few thoughts by PHAEDRU5 · · Score: 5, Insightful
    1. Bill's out of his gourd if he thinks telling the Europeans that OSS is anti-capitalist will get him anywhere. If anything it'll ensure the Europeans go more into the OSS camp.

    2. Is anyone worried about this tendency within the EU towards standardization and centralization? I mean, the French definitely want things back as they were in 1680, or thereabouts, with France in control of the continent. Does anyone think it's time for Europe to acquire a Bureau of Sabotage?

    --
    668: Neighbour of the Beast
  4. Re:Creating a pool doesn't guarantee swimming by ch-chuck · · Score: 4, Insightful

    Which country will want to spend money creating applications, if the rest get them for free?

    Because they're not in the software for profit business? Say I want to build a house a certain way, but there are no pre-existing blueprints for one just the way I want it. So I hire an architect and we work and work and make up exactly what I want and then built it. Does it really detract from my life just because someone else can use the same blueprints, obtained for the cost of duplication, if it just happens to work for them as well? If I have a software need, I can either 1) purchase a license for an existing product and since I'm only purchasing a license, not the rights to the software, am left dangling at their whims like a marionette (Msft: "We want you to upgrade now, be a good customer and buy our latest or greatest or we can make things difficult for you!") or 2) use existing freeware and live with the warts or 3) get into the open source game and a) use what exists and modify it to your needs or b) wait for someone else to make a version that fits your needs.

    Now one can easily complain, "Hey, we spent X amount of France's taxpayer money developing this app and Belgium gets it for free!" but the country or company that hires developers to create and maintain software the way they want it gets exactly what they want, and the freeloaders have to life with that or hire their own developers. In a way it's like the software market anyway, you can only purchase off the shelf what the majority want or what Msft research decides you shall want.

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }
  5. Or better yet, some quotes from the study by ubbe · · Score: 4, Informative
    The study (pdf) is pretty level-headed about the "viral nature" of the GPL-style licenses, check out this quote:
    "At the contrary of some declarations, this "copyleft effect" does not touch or affect other software, or software interoperating with the GPLed software. But if you really INCLUDE
    significant parts of copyleft code (e.g. GPLed components) in your software, this software must be distributed under the same license (e.g. GPL license)."
    And this paragraph:
    "As was said in the "copyleft" comments, the viral effect of a license like the GPL is a myth in the sense that it will not constraint a
    publisher to release his software as GPL if some lines of open source code where introduced in it by accident."
    The study (pdf) compare the different licenses, the pros and cons for the developer/end user. I haven't had the chance to read it all, but from what I can tell It's good reading. Great education for 'Open Source' enthusiasts.
  6. Shaking my head by theolein · · Score: 5, Insightful

    I sometimes think you Americans deserve a company like Microsoft: You complain long and loud how monopolistic, evil etc they are, but the minute someone outside the US actually does something about it, then that someone is immediately either communist (the EU in general), fascist (anything to do with Germany) or incompetent (usually some comment on France). This says more about stereotypes in American consciousness than anything else.

    The EU is definitely not paradise, but they have a fairly good record of not blowing too much money on things which the tax payers have to foot, and OSS makes a lot of sense for me as a tax payer(cost), me as a citizen(the source code) and me as a programmer(the development stays here in Europe and not in Redmond).

    The person who asked which country will pay for this: They will obviously have to work some agreement out on sharing of costs, but I see that being a lot easier to get through the various parliments than explaining that our tax money goes to a company in Washington State.

  7. Several thoughts . . . . by Aliks · · Score: 4, Interesting

    First off

    there is a LOT of bespoke software running in UK government departments, and a lot of it was developed by third parties. Consultancies involved in this work have generally retained the IP to the work and in many cases have reused code, templates, and skills elsewhere for profit.

    Nothing wrong with this in principle. The government doesn't really want to be in the software development business so it should be keen for others to reuse work as widely as possible. The larger the pool of users of a piece of code the more likely the govt will get some benefit back. The downside has been that not only does the govt pay through the nose for the initial development, they also pay a premium for future upgrades because they are now a captive user.

    Avoiding this pain far outweighs the possible profit that could be made from retaining IP and selling to the highest bidder. (I've not seen many success stories coming out of Qinetiq which I believe is the UK agency responsible for commercialising apps that the govt owns. Correct me if I'm wrong on this one!)

    Second off

    The UK civil service is a passionate defender of the UK national interest. Trouble is that they often narrow the definition down to the interest of UK companies and do things that penalise UK citizens. There is a possibility that someone unaccountable will make an decision that using common apps across Europe will disadvantage UK software developers who will have to compete for govt business with equally skilled Europeans. It is also possible that someone will decide that the UK should be closely tied to US interests and that Microsoft is the only platform to work with.

    The same debate has been heard many times on a wide range of issues such as banking law, European air traffic control, and even common weapons across the armies.

    THE GOOD NEWS is that Open Source has the potential to be a different debate. The first government to develop or mandate sharable code has the best chance of establishing a standard for whatever app it is and therefore will avoid some later redevelopment costs. By opening the source code to scrutiny they also get the chance to check that the code does what they want it to do and nothing more. Less chance of hidden back doors, spyware etc.

    And finally, it seems to me the big question is the ease or difficulty of identifying components which are truly sharable. Has anyone got any comparisons with major multi nationals that have tried to do this across their divisions?