Thanks a lot .
You all made many parts clear.
Please let me find a bit more information about this and get back to you.
Thank you,
Murthy.
On Tue, Aug 28, 2012 at 2:54 AM, Patrick Matthäi <[email protected]>wrote:
> Am 27.08.2012 23:03, schrieb Dan Dennedy:
> >> This is already done if you keep all copyright/license information from
> >> the source in your copy,
> >
> > Really? Is that how you read it? If you defer distribution of the
> > source code to upon request and distribute binary by default, then
> > copyrights in comment headers do not appear.
>
> That is the reason why I say: IANAL (I am not a lawyer), just did not
> thought about the requirement in this situation to still deliver the
> license of the used software, sorry!
>
> > He asked about a contact for the license. The copyright holder of a
> > component can make their component available under an alternate
> > license. Otherwise, how would anyone know who is the licensor and who
> > to contact? In the MLT project, there is no required copyright
> > assignment agreement for contributors, but I consider that a patch
> > submitter has only earned copyright if they are added as such in the
> > comment header.
> >
>
> To be exactly yes that is right, So if I would e.g. submit patches I
> also had to add/modify with it the copyright headers. I do not need it
> for myself to get added as contributor but at the end if you would e.g.
> decide to switch tomorrow to a closed license it still would be
> problematic for you if I would disagree (as long as you would continue
> to use my patches) at the courts. But as I said this is too detailed and
> in general not my goal :)
>
> --
> /*
> Mit freundlichem Gruß / With kind regards,
> Patrick Matthäi
> GNU/Linux Debian Developer
>
> Blog: http://www.linux-dev.org/
> E-Mail: [email protected]
> [email protected]
> */
>
>
--
Regards,
Murthy.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mlt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mlt-devel
