From: <hbj515@sina.com>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] 回复：Re: 回复：Re: 回复：Re: [PATCH v9 5/5]_lavc,_doc:_add_libuavs3d_video_decoder_wrapper
Date: Tue, 01 Mar 2022 15:19:49 +0800
Message-ID: <20220301071949.DC5F941400A3@webmail.sinamail.sina.com.cn> (raw)
Thanks, the license has been updated. You can check it on https://github.com/uavs3/uavs3d
----- 原始邮件 -----
发件人："Jean-Baptiste Kempf" <jb@videolan.org>
收件人：ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
主题：Re: [FFmpeg-devel] 回复：Re: 回复：Re: [PATCH v9 5/5]_lavc,_doc:_add_libuavs3d_video_decoder_wrapper
日期：2022年03月01日 14点15分
Your understanding is correct. BSD-3 is fine.
On Mon, 28 Feb 2022, at 23:09, hbj515@sina.com wrote:
> Sorry, the last reply was a bit ambiguous. I want to confirm that
> uavs3d will not be flagged as "non-free", if the license is changed to
> BSD 3-clause.If so, we will change the license soon. The BSD 3-clause
> license is compatible with the GNU GPL, as the wiki says.
> (https://en.wikipedia.org/wiki/BSD_licenses)
> ----- 原始邮件 -----
> 发件人："Jean-Baptiste Kempf" <jb@videolan.org>
> 收件人：ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
> 主题：Re: [FFmpeg-devel] 回复：Re: [PATCH v9
> 5/5]_lavc,_doc:_add_libuavs3d_video_decoder_wrapper
> 日期：2022年03月01日 13点19分
>
> Yes. This is correct.
> On Mon, 28 Feb 2022, at 21:57, hbj515@sina.com wrote:
>> Thinks for your reminder. If uavs3d is BSD 3-clause, will uavs3d be
>> flagged as "non-free"? We can change the license of uavs3d.
>> ----- 原始邮件 -----
>> 发件人："Jean-Baptiste Kempf" <jb@videolan.org>
>> 收件人：hwrenx <hwrenx@126.com>, ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
>> 抄送人：hbj <hanbj@pku.edu.cn>
>> 主题：Re: [FFmpeg-devel] [PATCH v9 5/5] lavc, doc: add libuavs3d video
>> decoder wrapper
>> 日期：2022年02月26日 19点06分
>>
>> Hello,
>> On Mon, 31 Aug 2020, at 17:07, hwrenx@126.com wrote:
>>> + --enable-libuavs3d enable AVS3 decoding via libuavs3d [no]
>> uavs3d is BSD 4-clause, and is therefore not compatible with GPLv2,
>> GPLv3, LGPLv2.1 or LGPLv3
>> uavs3d should be flagged as "non-free" (and undistributable) then.
>> Best,
>> --
>> Jean-Baptiste Kempf - President
>> +33 672 704 734
>> _______________________________________________
>> ffmpeg-devel mailing list
>> ffmpeg-devel@ffmpeg.org
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>> To unsubscribe, visit link above, or email
>> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
>> _______________________________________________
>> ffmpeg-devel mailing list
>> ffmpeg-devel@ffmpeg.org
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
> --
> Jean-Baptiste Kempf - President
> +33 672 704 734
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
--
Jean-Baptiste Kempf - President
+33 672 704 734
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
reply other threads:[~2022-03-01 7:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220301071949.DC5F941400A3@webmail.sinamail.sina.com.cn \
--to=hbj515@sina.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git