Web 2.0 Open Source Development - The Rules of Engagement

My company <a href="http://www.softwiredweb.com" title="Softwired Websites with Joomla!">Softwired</a> specializes in building web 2.0 websites with Joomla! which is an open source content management system.  This is the model that I use to describe the process for creating this type of software. Here are some basic fundamentals on how developers work together to create open source software: Do your homework The community is very forgiving for newbies.  It is not tolerant of basic ignorance or the inability to learn a process. Contribute first, worry about how you’ll benefit later The basic idea is you should contribute to benefit from the fruits of the collective effort either by offering software or giving donations.  Those who try to take advantage of other people’s work will quickly be labeled or banned.  Those who offer their work as open source and ask for donations are heralded as heroes. Your primary mission is NOT to make money OK this one is still hard for people to understand.  We all need to make money but that isn’t our primary mission.  By collaborating with others you are creating a community with a common vision.  That vision is NOT to make money but to provide something of value. Stay current Resiliency will pay off in the long run.  Too many get in and get out but those who stay with it can become mentors and regarded with some expertise. The culture of open source software development process requires a high degree of integrity.  Considering the effort from the founders who volunteer their time they have a very protective attitude toward their work. Here’s an example of what not to do: I was working hard last year gathering and learning how to work with Joomla!  Part of that process is to see how other companies online are doing it and how my company compares for value. I ran across a company that was promoting a “simple website” which was taking all of the open source components (created by other developers) and wrapping them up and selling them cheap, i.e. a low monthly fee rather than the normal cost of construction.  My immediate reaction was, “that’s not fair!”  My second thought was, “is that even legal?” The open source license is very specific about commercial use.  The software is free as long as you don’t modify it and sell it as your own.  In addition, you must buy a license from each developer for any extensions that are used.  Based on the price it didn’t seem like this would be possible.  I thought about alerting the watchdog group for license violations. Well as it turns out the site is still up but changed the product in such a way as to be compliant with the general public license.  They had originally included extensions (added features) along with the core content management system.  Now, after checking, the extensions are not included with the basic website.  Someone blew the whistle. What this demonstrates are a couple of things: <ol> <li>Those involved in the community are emotionally tied to the product so thousands of eyes are watching.</li> <li>Because of the emotional involvement violators will be found quickly and forced into compliance or face legal ramifications.</li> </ol> This is why it works. 2009-01-14T19:53:40Z

-12.6887

414 2824

true

19584

web-20-open-source-development-the-rules-of-engagement

2009-01-15T16:23:20Z

With any open source software collaboration there are certain rules that everyone must abide by in order to participate within the community. These groups have a common goal and have little patience for those who aren’t following those rules.

Web 2.0 Open Source Development - The Rules of Engagement

2009-02-24T09:48:30Z