When can I publish a software tool written at work?

I’m working on a software problem at work that is fairly generic, but I can’t find a library I like to solve it, so I’m considering writing one myself (at least a bare-bones version). I’ll be writing some if not all of the 1.0 version at work, since I need it for the project. If turns out well I might want to bring the work home and polish it up just for fun, and maybe release it as an open-source project. However, I’m concerned that if I wrote the 1.0 version at work I may not be allowed to do this from a legal sense. Obviously I could ask my boss (who probably won’t care), but I’m curious how other programmers have dealt with this issue and where the law stands here. My one sentence question is, When is it okay (legally/ethically) to open-source a software tool originally written by you for work at work? What if you have expanded the original source significantly during off-hours?

Follow-up: Suppose I write the whole thing at home on my time then simply use it at work, does that change things drastically?

Follow-up 2: Note that I’m not trying to rip off my employer (I understand that they’re paying me to build products that they own)–I’m just wondering if there’s a fair way of doing this for all involved… It would be nice if some nonprofit down the road could use my code and save them some time. Also, there’s another issue at stake. If I write the library for a very simple, generic thing (like HTML tables in Javascript), does that mean I can never again do so on my own time without putting myself at legal risk (even if it was a whole new fresh rewrite or a segment of a larger project). Am I surrendering my right to write code for this sort of project for the rest of my life (without this company’s permission), since the code at work might still be somewhere in my brain influencing me? This seems related to software patents, as a side-note.

It is almost never OK, legally or ethically, to release products that you have created using your employer’s resources or while being payed by the employer for your time without permission.

However, it depends on your employment contract. If you were paid by the company and/or used company resources to produce the product, chances are that the work belongs to your company. You need to go through your supervisor and your legal department. Depending on your employment contract, there might also be restrictions on working on related technologies or using knowledge gained at your employer in projects, even if you work on them using personal resources on your own time.

If you are using paid time, company resources, or are developing something that might be considered related to the business of your company, always seek guidance from your manager and/or legal department to ensure that you aren’t violating any agreements and to get the appropriate permission to work on projects. Typically, it’s easier to do this before you begin work as it might change the approaches that you take on the project.

Writing products for the use at work on your own time is questionable and depends on the regulations that your employer must adhere to. At the very least, you could be interfering with your employers schedule, budget, and estimates by taking work off-line. In some cases, you could be violating the contractual regulations by creating products outside of time that is tracked and billed appropriately.

If turns out well I might want to bring the work home and polish it up
just for fun, and maybe release it as an open-source project.

You should be crystal clear with your employer about your intentions at the outset. Come to an agreement about how that’ll all work before you get started so that there are no hurt feelings, misunderstandings, disappointments, etc. The work you do for your employer is your employer’s property.

When is it okay (legally/ethically) to open-source a software tool originally written by
you for work at work?

When you have permission from your supervisor (and perhaps legal department) to distribute their property.

What if you have expaned the original source significantly during off-hours?

Doesn’t matter. You’re working with your employer’s property — changing a few lines here and there doesn’t change that fact. It may still be theirs even if you change every single line in the project. Check with your lawyer for details, but don’t expect good news.

Now, your employer may be perfectly happy to distribute the library under some open source license. If it’s not something they consider part of their competitive advantage, or if they want to have the library maintained but don’t necessarily want to do all the work to maintain it themselves, or if they want to garner some good will, or whatever, then things can work out. Just remember that it’s their decision.

Easy answer:

Never.

Here’s the problem: According to the laws of most modern countries, you hold a copyright over everything you write by default. This holds true even when you write it for someone else, such as your employer.

Obviously, this is problematic for anyone who is interested in hiring a software developer.

To solve this, software companies have you sign a Non-Disclosure Agreement (NDA). Within this NDA, it explicitly states that you relinquish the copyright of all code you write for that employer. Doesn’t matter when you did it. It’s all the same.

In other words: The code that you wrote does not belong to you. It belongs to the employer, and you are not allowed to publish it.

I’ve never heard of a developer not signing an NDA, so unless you’re in some really remote region of the world, its a safe bet to say that you signed an NDA when you were hired.

If your employer is interested in publishing it for some reason, then it is a different story (and if you’re iterested, you could also try to convince them that it is the correct thing to do). But that’s the only way.

This depends pretty much on what contractual relationship you have with your employer…

Intellectual property

By default, many organisations are now more willing to open-source generic functions/classes to benefit the wider programming/coding community, but there are those that don’t and can’t from an intellectual property perspective – to commercially protect what they have.

If your code utilises any type of reference to your employers IP, or trade secrets then it’s perhaps understandable that they may refuse.

Open source

Essentially and by default, you are entitled to release any piece of software you write in your own time and as long as it doesn’t conflict with the terms of your employment contract – or – compete with what they do in any aspect.

The best advice I could give is to approach your employer and discuss the matter openly. This will provide you with:

The attitude of your employer towards open-source/community programming
Reflect/highlight their understanding of software and it’s inherent/wider value
Your rights as to what they perceive you being able to do/not do

Any employer, who refuses to allow you to expand your thinking/learning and indeed contribute to the wider community (and solve bigger,wider problems) should tell you a lot about where you work. Companies often think more widely than they have prior about releasing code as it doesn’t just benefit them – but it has to be in a form that doesn’t threaten them in anything that they do.

My time/their time

As with other answers – you can’t use your employers time to build your own software; either ethically or principally. Treat them separately unless your employer is willing to commit to releasing code.

In some cases, programmers fuse their own time and work time to create something great – which, every party benefits from and perhaps the ideal outcome to your question.

Filed under: softwareengineering - @ 14:57

Thẻ: legal

Thiết kế website giá rẻ

Danh mục

When can I publish a software tool written at work?

Never.