Is this a breach of Licence

[Arnt Karlsen]

On Thu, 30 Jul 2009 13:43:12 +0100, Greg wrote in message 
<4A719560.8050703 at salesagility.com>:

> Do you get paid for being rude and ignorant or does it just come
> naturally?

..it comes from over 6 years 
at http://groklaw.net/ .

> I made an honest enquiry ... I have nothing to do with vtiger. I am 
> competing for a contract with a company that is passing vtiger off as 
> their own work and I wondered if there was anything I could do about
> it.

..I apologise, you came across to 
me as a Microsoft shill.

..and, unless you are a lawyer, no, 
I don't see how you can help them, 
other than help them find a good lawyer, 
and, take your risks on the contract 
people, by doing the whistle blowing, 
some like people with spines, and 
some do not, so you may Burn for 
Doing the Right Thing.  Good Luck!



> Full stop.
> 
> Thank you for your help .... NOT
> 
> Arnt Karlsen wrote:
> > On Thu, 30 Jul 2009 11:42:47 +0100, Greg wrote in message 
> > <4A717927.40803 at salesagility.com>:
> >
> >   
> >> A company we are aware of 
> >>     
> >
> > ..name it.
> >
> >   
> >> has rebranded vTiger and passed it off as 
> >> there own software.
> >>     
> >
> > ..are you whining on behalf of vtiger.com?
> > You should have used the GPL, which would 
> > then have made your question relevant here.
> >
> >   
> >> vTiger is covered by the SugarCRM Public Licence and by a
> >> derivation of the MPL, the vtiger Public License Version 1.0 
> >> http://www.vtiger.com/products/crm/vtiger-public-license.html
> >>     
> >
> > ..this
> > ( http://www.vtiger.com/products/crm/vtiger-public-license.html )
> > "LICENSE AGREEMENT" contract is relevant to gpl-violations.org how?
> >
> >   
> >> Does this allow me to lift the codebase wholesale, stick my logo on
> >> it and pass it off as my own work, or does this clause come into
> >> play from the above licence?
> >>
> >> 3.3. Description of Modifications.
> >> You must cause all Covered Code to which You contribute to contain
> >> a file documenting the changes You made to create that Covered
> >> Code and the date of any change. You must include a prominent
> >> statement that the Modification is derived, directly or
> >> indirectly, from Original Code provided by the Initial Developer
> >> and including the name of the Initial Developer in (a) the Source
> >> Code, and (b) in any notice in an Executable version or related
> >> documentation in which You describe the origin or ownership of the
> >> Covered Code.
> >>
> >> greg
> >>     
> >
> > ..ask your contract law litigator. ;o)
> >
> >   
> 


-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.