Re: policies, slightly OT
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 59659
interpreted = N
texte = Terry Wilson wrote: > 1) that they don't own the code, I do; that they're only buying a > service that happens to present their information in a web browser, or > something to that affect. It's definitely important to get this in writing, as well as to place this information in the source code. You can consider encrypting the templates (which WebDNA makes easy to do), but the copyright notice should be in plaintext. > 2) if I die or otherwise am unable to continue doing this, that they get > the source code This is considered "code escrow" and you will probably need to have a trusted third party retain an unencrypted copy in order to act as your agent after you are unable to do so. You will also need to deal with what happens if you and your client sever your business relationship on unfriendly terms, so that they don't try and execute the escrow terms. You should see these articles: http://www.kslaw.com/library/articles.asp?196 http://www.devx.com/projectcool/Article/20043 http://web.archive.org/web/20040214022056/http://www.digidem.com/legal/wda/wda.html (watch for line wraps on that last one). You can also Google for other "WEBSITE DEVELOPMENT AGREEMENT" examples... HTH John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Terry Wilson wrote: > 1) that they don't own the code, I do; that they're only buying a > service that happens to present their information in a web browser, or > something to that affect. It's definitely important to get this in writing, as well as to place this information in the source code. You can consider encrypting the templates (which WebDNA makes easy to do), but the copyright notice should be in plaintext. > 2) if I die or otherwise am unable to continue doing this, that they get > the source code This is considered "code escrow" and you will probably need to have a trusted third party retain an unencrypted copy in order to act as your agent after you are unable to do so. You will also need to deal with what happens if you and your client sever your business relationship on unfriendly terms, so that they don't try and execute the escrow terms. You should see these articles: http://www.kslaw.com/library/articles.asp?196 http://www.devx.com/projectcool/Article/20043 http://web.archive.org/web/20040214022056/http://www.digidem.com/legal/wda/wda.html (watch for line wraps on that last one). You can also Google for other "WEBSITE DEVELOPMENT AGREEMENT" examples... HTH John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
John Peacock
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[searh] or [shownext]problem (1998)
Webcat/Webmerchant part II (1998)
Search for 20 finds 2000, 200 Why? (1997)
How can I Add several Items into the cart at once? (1997)
Encrypting Credit Card Numbers (2004)
[HIDEIF] inside [FOUNDITEM] (1997)
Summ=T Problem (1997)
Re:no [search] with NT (1997)
Database Structuring (again) (2003)
serial number dishing (1997)
SEARCH Peram (2003)
Max Record length restated as maybe bug (1997)
Cookie problems using Mozilla and Camino browsers (2004)
sort on categories (DBEdit) (2001)
[OT] FTP client (2003)
Almost a there but..bye bye NetCloak (1997)
New Cost Field (1999)
Signal Raised error (1997)
WebCat2.0 [format thousands .0f] no go (1997)
WC2b15 - [HTMLx]...[/HTMLx] problems (1997)