In-house Open Source

Surely one of the most common reasons for creating a piece of open source software is … ’cause you need it at work.

I’ve never been very comfortable with that — when I’ve had to fix/patch OpenSource software for work, I’ve tended to just sort of do it and hand it back.

But what is the relationship between an employer-user and an employee-vendor when the software is Open Source. The company is paying you to write software which is copyright by the company.

I’m thinking about using DBA within BE. I’ll have to do some work before it’s properly ready for that. But that’s OK. Gives me a goal.

PlayNet have OKed that, but I’d like to go into Jim’s office with a piece of paper bearing my scrawl that says “Hey, I’m not going to embrace & destroy; I’m not going to put bits of BE into my project and then post them on the intratubes; and I’m not going to see a chance to make money out of it and change the licensing on you…”

Any of you ever used any kind of boiler-plate “I’d like to share this bit of code so that from time to time someone else can fix my shit?” – erm – I mean open-source-under-employ-contract license?