Gotta agree with Rule #1 ;) ALWAYS have a contract, always, if you want to get paid on time and properly have a signed and ready to go contract.
However its not always the case that the code base is property of the client. IF you use some other classes/tools/proprietary code to complete the project there can be stipulations that need to be made apparent to the buyer beforehand. For example if you were to incorporate ANY licensed scripts you should let the buyer know this beforehand especially if they are expecting to retain the code base. If you can keep your intellectual property however thats always best. I prefer to retain code until all payments have been made - something to the effect of "source code will be made available within 30 days of receipt of final payment" [this allows for time to make sure the check clears ;) ] I also like to add in a 5% 10 NET 30 to all my invoices (and make people aware up front). It gives people a little incentive to pay faster but allows them 30 days before I start more drastic measures (only had to once but they paid up FAST). Yeah I can loose a little at times but the faster I get my money the happier I am. -CD On Wed, May 28, 2008 at 2:55 PM, John Grden <[EMAIL PROTECTED]> wrote: > always use a contract - even with friends (especially with friends) - Rule > #1 > > Personally, I would NEVER release source until final bill is paid. Doesn't > matter if you don't have a contract or you didn't stipulate that upfront. > Fact is, you haven't been paid, and that's the only thing you have to force > their hand. > > I don't agree about keeping source - I think it's pretty well customary > that the intellectual property invested in the code base is that of the > client - IE: they paid for you to develop it, so therefore, it's theres. > That's how's its been on ever gig I've done on the past 7 yrs +. > > my 2cents. > > > On Wed, May 28, 2008 at 4:47 PM, Stephen Hepworth <[EMAIL PROTECTED]> > wrote: > >> Everyday :) -- >> >> Keep your source code. >> >> Contract w/retainer 75% upfront - 25% to release code after completed. >> That's my basic stance on most issues regarding client special site >> requests. >> >> Keep them honest!!! >> >> >> >> ----- >> >> *From:* Schell <[EMAIL PROTECTED]> >> *To:* Open Source Flash Mailing List <[email protected]> >> *Sent:* Wednesday, May 28, 2008 2:42 PM >> *Subject:* [osflash] Commercial Work >> >> I'm having a little issue with a client. They hired me for a web >> application and have not yet paid, but want the source code to integrate it >> with one of their online shops. What kind of copyright, license, etc. do you >> guys use in these situations, or, what is your policy on dealing with >> clients [ do you give them source code, compiled executables, both? Do you >> make contracts or work with an honor system?] Has anyone been seriously >> burned by a client stealing code or not paying? Thanks in advance. >> >> -- >> Schell Scivally >> 600 Santa Rosa Ave. >> Santa Rosa, CA >> 95404 >> [EMAIL PROTECTED] >> http://blog.efnx.com >> >> ------------------------------ >> >> _______________________________________________ >> osflash mailing list >> [email protected] >> http://osflash.org/mailman/listinfo/osflash_osflash.org >> >> >> _______________________________________________ >> osflash mailing list >> [email protected] >> http://osflash.org/mailman/listinfo/osflash_osflash.org >> >> > > > -- > [ JPG ] > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > > -- ----------------------- Chris Duke
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
