From PICLIST@MITVMA.MIT.EDU Thu Nov 14 05:08:51 2002 Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-7.13) id A063FA300DA; Thu, 14 Nov 2002 05:08:51 -0800 Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <16.007D494E@cherry.ease.lsoft.com>; Thu, 14 Nov 2002 7:55:01 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 3097 for PICLIST@MITVMA.MIT.EDU; Thu, 14 Nov 2002 07:54:27 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 6989; Thu, 14 Nov 2002 07:53:12 -0500 Received: from simmts1-srv.bellnexxia.net [206.47.199.10] by mitvma.mit.edu (IBM VM SMTP Level 320) via TCP with SMTP ; Thu, 14 Nov 2002 07:53:12 EST X-Comment: mitvma.mit.edu: Mail was sent by simmts1-srv.bellnexxia.net Received: from gm ([156.34.176.102]) by simmts1-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP id <20021114125312.RFCN27043.simmts1-srv.bellnexxia.net@gm> for ; Thu, 14 Nov 2002 07:53:12 -0500 References: <3DD33141.52D59C2A@3mtmp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Message-ID: <002601c28bdc$817cc920$b64aa40a@gm> Date: Thu, 14 Nov 2002 08:51:09 -0400 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Ray Gallant Subject: [OT]: Standard contract for work? To: PICLIST@MITVMA.MIT.EDU X-RCPT-TO: Status: R X-UIDL: 277600446 X-Evolution-Source: pop://mailinglist%40farcite.net@mail.farcite.net/ X-Evolution: 000006a6-0000 Do you require a CONTRACTUAL AGREEMENT for a design, consultation/service that you are offering or are you looking for an employment type? I have some for design work that I could modify a bit and offer. In my pic driven designs, the last thing to past hands is a copy of the code. I don't mention this in the contract. I have gone to the length of setting a hit counter for prototypes when non-volatile memory was available. I believe design work should include a mutually created "scope of work" document. Anybody can create gantt charts. Congrad on the contract. {slewrate} ----- Original Message ----- From: "Josh Koffman" To: Sent: Thursday, November 14, 2002 1:14 AM Subject: [OT]: Standard contract for work? > So, here am I faced with the prospect of coming up with some sort of > contract for some work I will be doing. Does anyone here have a standard > type of contract they are willing to share? -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics