A licence is just a bunch of legalese. You can use existing licences but it
doesn't mean you cannot make your own licence from scratch. As long as
clients are informed pre-development what restrictions will be applied there
shouldn't be a problem. Of course, bear in mind that really restrictive
Keep your code under subversion, and guarantee only your code.
Tell them also that any release will not include modifications out of SVN.
So, keep controled your sourcecode (SVN = who, when, why) and guarantee only
your work.
Responsabilize the (evil) client.
Good luck,
2009/11/17 Gareth
Hey Gareth,
this is somewhat how it's currently working.. our own core plugins are
the same for every project, and the real product the clients are
paying for is the application-level customization/configuration/
additions. We're just concerned that with every app we deliver, we
also deliver our
Why not do that restriction at the sale contract? There´s a lot of licenses
that forbid to use the code inside for another applications, but do let to
customize the application.
Andre.
2009/11/17 Richtermeister nex...@gmail.com
Hey Gareth,
this is somewhat how it's currently working.. our
Let's keep this on topic. Thanks.
On Nov 16, 12:18 pm, Gábor Fási maerl...@gmail.com wrote:
Quote from the bottom of *every* mail you get from this levlist:
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
