[iamjason89]

Well we have no contract about anything what so ever. My salary position or the PHP program. I modified the opensource PHP application for a tool for ME to use. Here's my non-tech real world example.

Sam sorts papers for a company. There ask him to sort them alphabetically. He is only given a flat table to work with. He decides to build a filing rack as it would be a lot more efficient and allow him to get's things done quicker. The other people in the office see this device and would like to use it as it seems to work way better as well.

Now given Sam leaves the company, that filing rack he built is his. He used no funding from the company to make it. They did not ask him to build it. If they want one like it, they need to build one them selves or purchase it from Sam.

This is my interpretation.

[lutusp]

> Well we have no contract about anything what so ever.

Actually, with respect to OSTicket, you do. OSTicket is licensed under the GPL, which means that anything you write based on it is also GPL-licensed. Which means you cannot publish or offer it without also releasing your own source for anyone else to use or modify.

In GPL open source, everyone needs to acknowledge everyone else's copyrights, but no one is prevented from using the code in any way they please -- as long as they release their own source code.

> If they want one like it, they need to build one them selves or purchase it from Sam.

Before you get into trouble, you need to learn the rules of open-source.

[johnsonmax]

I'm sorry mate but that simply isn't how this works.

If you come up with an idea while working for a company, and apply it at that company, then the company owns the idea. That's always the way it's been, and I think it's quite natural.