Slashdot Mirror


Challenges in Releasing Open Source Software?

Chris Vaughan asks: "Me and my Co-Workers at the Advanced Computing Research Lab are just about ready to release our first Open Source package on SourceForge.net I ask the Slashdot community what hurdles they had to overcome and how much involvement do they still have in their project years later. Also what types of licensing did you pick and why did it suit your project best? Our project, MyPBS is a PHP/MySQL/Perl frontend accounting package for the Portable Batch System (PBS). Which is used to account for super computing usage. I appreciate any comments you may have."

2 of 24 comments (clear)

  1. You need to review the MySQL licensing scheme by millisa · · Score: 5, Informative

    MySQL has changed their licensing recently and they are very restrictive about which OSI Approved licenses are acceptable for use with their product (without paying the licensing fee). If it's not GPL, you are likely going to have issues. They have a very short list of what does and does not qualify. However, they are responsive when you write them at licensing@mysql.com (albeit it took several days) when you need clarification.

    Apparently PostFix's OSI Approved IBM Public License does not qualify so I'm having to prep to pay for licensing since we use postfix with MySQL (confirmed with their licensing folks). They did assert that they were still in the process of reviewing other licenses.

  2. Open Source Development HOWTO 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?