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."

Comments

Re:You need to review the MySQL licensing scheme

[Brandybuck]

so I'm having to prep to pay for licensing since we use postfix with MySQL

According to the GPL, there are no restrictions on use. So why is MySQL making you buy a license?

Re:You need to review the MySQL licensing scheme

[Alan Shutko]

The MySQL people have their own view of the GPL which may not reflect reality. Notably, you can do practically anything you want with GPL'd software if you don't distribute it. Note that "Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope." Also note that 2b only specifies that the results need be under the GPL (thus necessitating GPL-compatible licenses) if you distribute it. Their view of whether making and using copies within an organization consists distribution conflicts with the FSF's view on that matter.

MySQL's revenue model is predicated on convincing as many people as possible that they need licenses, but you should really talk to your own lawyers. Or just pay, because you get support and help its development. But be aware that MySQL will try to convince you to buy licenses even when you may strictly not need them.