Re: How do I approach this?
- From: BobF <rNfOrSePeAzMe@xxxxxxxxxxx>
- Date: Sat, 13 Aug 2005 13:33:32 -0500
On Sat, 13 Aug 2005 14:20:17 +0000 (UTC), Phil wrote:
> Bob,
>
> You wise old owl you!! :-)
>
> During my brief discussion with the s/w development manager, he did (perhaps
> tongue-in-cheek) suggest that he would be happy for me to be seconded to his
> dept. for 6 months as long as my dept. paid the wages!!! Mmmmmmm, I don't
> think that will happen. In fact I know it won't because I mentioned it to my
> boss! Anyway, unfortunately right now I am not in a position to relocate and
> the s/w dept. is not commutable.
>
> So, not only do I see your point of view, I agree with it. And I would think
> that this should suit both parties.
>
> I have a question, you state in point (1) of 'What I would
> recommend'.............Gives the company perpetual license to use
> ................The license is intended for the company's internal use only.
>
> What is this 'license'? Is it a legal document in as much as does it have to
> be done through solicitors etc? Can it be a simple letter head from the
> company making some relevant statements regarding intended use and my
> ability to distribute further (other than competitor)?
>
> Thanks again and looking forward to your response.
>
> Phil
>
>
As Michael suggested, you should have the agreement written down and signed
by you and a company representative.
Unless your company sells the same kind of s/w as you've written, I
wouldn't get too formal. Plain language is the approach I would take.
This is something you'll have to decide for yourself.
However formal, the "license" is the statement of purpose and conditions
under which you're granting permission to use and/or modify your s/w.
EULA's abound as examples of intent, but IMO are written too formal for
your situation.
Good luck!
.
- References:
- How do I approach this?
- From: Phil
- Re: How do I approach this?
- From: Steven Wilmot
- Re: How do I approach this?
- From: Phil
- Re: How do I approach this?
- From: Phil
- Re: How do I approach this?
- From: Michael Latta
- Re: How do I approach this?
- From: Phil
- Re: How do I approach this?
- From: BobF
- Re: How do I approach this?
- From: Phil
- How do I approach this?
- Prev by Date: Re: How do I approach this?
- Next by Date: DLL: Using msvcrtd.dll instead of msvcrt.dll
- Previous by thread: Re: How do I approach this?
- Next by thread: Re: How do I approach this?
- Index(es):