5 ms·

I've actually got a slight variation of this question. There is an open source project that I created, and it is starting to get some traction. I also have a

by derekp7 12y ago

I've actually got a slight variation of this question. There is an open source project that I created, and it is starting to get some traction. I also have a need at work that I can fill using this project (not customer facing, just internal IT related). And there's a number of additional open source projects that I'd like to extend, and use for work too (such as adding a better database backend to Nagios for example). The problem I have, is if I bring this up to management, I take the chance that they will think I worked on it during business hours (I actually coded it up during a 2-week holiday break), or that they otherwise own the IP for the code. Not that I think I'll have a major problem with it, but it could be a bit awkward. Is there any guides out there of how to approach this subject with management?

sukilot 12y ago
Everywhere I have worked, you would have to completely separate your employee time from the project (not even talk about it) and leave it to other employees to decide if appropriate to contribute.
cplease 12y ago
Most salaried software engineers have contracts that any software IP they create belongs to their employer, whether they do it on company time/computers or not. You are correct that this is especially hairy if you wrote a project that could be applied to your employer. Check your contract and tread carefully.
- derekp7 12y ago
  I'm a systems admin/engineer, not hired specifically for software. However, I actually had that type of contract when I worked at Motorola ("Anything you conceive solely by you or jointly with others, at any time of the term of your employment..."). The company I work for now did not have that in any of their paperwork, at least not that I've signed directly. Unless it is hidden in the employee handbook, then I only signed a paper that says I've received the handbook. But still...
mikekchar 12y ago
I used to have serious problems with working on free and open source projects due to my contract at work. Even though my employers said that they would evaluate things on a "case by case" basis, it was often "Write it first and we'll tell you if you can distribute it". Then if I wrote it they would always say "no". Eventually I learned that working in an environment I like is more important to me than the size of my paycheck. Every job I've worked at has always given me more than enough to live comfortably, even if it wasn't always at market rate. Like other people on this thread, I give steep discounts for compatibility with free and open source development. I am much happier as a result. But to answer your question, just request time with your manager and explain the situation pretty much exactly as you have done here. If they say that you can't distribute the code, I would abide by the decision. Make sure to explain how important it is to you, but be civil and don't make any ultimatums. This is much better than having them take legal action on you after the fact (which has happened to many unsuspecting developers). If they can't accommodate you, consider what I said at the beginning. It took me years to transition to a type of work that made me happy, but it was worth it. You don't have to do anything drastic, but it never hurts to think about your options and work towards your dreams.

by derekp7 12y ago

sukilot 12y ago

Everywhere I have worked, you would have to completely separate your employee time from the project (not even talk about it) and leave it to other employees to decide if appropriate to contribute.

cplease 12y ago

Most salaried software engineers have contracts that any software IP they create belongs to their employer, whether they do it on company time/computers or not. You are correct that this is especially hairy if you wrote a project that could be applied to your employer. Check your contract and tread carefully.

derekp7 12y ago
I'm a systems admin/engineer, not hired specifically for software. However, I actually had that type of contract when I worked at Motorola ("Anything you conceive solely by you or jointly with others, at any time of the term of your employment..."). The company I work for now did not have that in any of their paperwork, at least not that I've signed directly. Unless it is hidden in the employee handbook, then I only signed a paper that says I've received the handbook. But still...

mikekchar 12y ago

I used to have serious problems with working on free and open source projects due to my contract at work. Even though my employers said that they would evaluate things on a "case by case" basis, it was often "Write it first and we'll tell you if you can distribute it". Then if I wrote it they would always say "no". Eventually I learned that working in an environment I like is more important to me than the size of my paycheck. Every job I've worked at has always given me more than enough to live comfortably, even if it wasn't always at market rate. Like other people on this thread, I give steep discounts for compatibility with free and open source development. I am much happier as a result. But to answer your question, just request time with your manager and explain the situation pretty much exactly as you have done here. If they say that you can't distribute the code, I would abide by the decision. Make sure to explain how important it is to you, but be civil and don't make any ultimatums. This is much better than having them take legal action on you after the fact (which has happened to many unsuspecting developers). If they can't accommodate you, consider what I said at the beginning. It took me years to transition to a type of work that made me happy, but it was worth it. You don't have to do anything drastic, but it never hurts to think about your options and work towards your dreams.