From: Andrew Lunn <andrew.lunn@ascom.ch>
To: "Kumar, Vivek" <Vivek.Kumar@zeevo.com>
Cc: "'Andrew Lunn'" <andrew.lunn@ascom.ch>,
Vivek Kumar <vivek@employees.org>,
ecos-maintainers@ecos.sourceware.org
Subject: Re: Assignment query
Date: Fri, 27 Aug 2004 06:56:00 -0000 [thread overview]
Message-ID: <20040827065555.GB17010@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <0175EEA85416D811893E009027D0F5D7938A05@MAILHOST>
On Thu, Aug 26, 2004 at 04:03:03PM -0700, Kumar, Vivek wrote:
> Hi Andrew,
>
> After some negotiation and emails it seems that the management is ok with me
> putting my flash driver code in open source. I talked to my manager and he
> said the email from them saying "Go Ahead With This" (Attached) will
> suffice. Do I still need to get more stuff from them.
Jifl should give the final word on this, but i would prefer it if the
company signed the normal paperwork.
> Also I was thinking if I rewrite the drivers at home from scratch, can I put
> them in open source. Is there a standard letter I can send the management
> saying I am working from home on something similar and if they are OK with
> that.
You should check your contract. Some contracts say that everything you
do is theres, no matter if you do it at work or at home. Since we
don't know what your contract says, we prefer to have an agreement
from your employer anyway, just to be safe.
Andrew
next prev parent reply other threads:[~2004-08-27 6:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 23:03 Kumar, Vivek
2004-08-27 6:56 ` Andrew Lunn [this message]
2004-08-27 10:20 ` Alex Schuilenburg
2004-08-27 12:25 ` Jonathan Larmour
-- strict thread matches above, loose matches on Subject: below --
2007-06-25 13:10 Rutger Hofman
2007-07-05 13:07 ` Jonathan Larmour
2006-01-09 15:35 Chase, Thomas
2006-01-12 15:41 ` Jonathan Larmour
2004-08-27 16:47 Kumar, Vivek
2004-08-09 22:54 Vivek Kumar
2004-08-10 7:04 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040827065555.GB17010@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=Vivek.Kumar@zeevo.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=vivek@employees.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).