Hello Yegor,
You wrote on Tue, Jun 04, 2019 at 02:09:24PM +0200:
> > > some files in libftdi mention additional licenses: src/ftdi_stream.c
> > > (MIT), cmake/UseLibFTDI1.cmake (LGPL 2.1) etc.
> > >
> > > Could you reflect all this in the LICENSE file like dropbear does [1]?
> > >
> > > It would be also great if the project can provide a file containing
> > > all copyright information that is needed for a FOSS compliance
> > > (attribution).
> > >
> > > Have you already used such tools as FOSSology [2] or scancode [3]?
> > >
> > > [1] https://github.com/mkj/dropbear/blob/master/LICENSE
> > > [2] https://www.fossology.org/
> > > [3] https://github.com/nexB/scancode-toolkit
> >
> > See our discussion on the BR mailing list:
> > http://lists.busybox.net/pipermail/buildroot/2019-May/251173.html
> >
> > FYI: https://spdx.org/ids-how
>
> FYI: I have found this really interesting paper about license
> compliance for FOSS projects [1]. In the light of [2] FOSS compliance
> is getting more and more important. And for now it means a lot of
> manual work :-(
>
> [1]
> https://www.linuxfoundation.org/publications/2018/03/license-scanning-compliance-programs-foss-projects/
> [2]
> https://opensource.com/article/17/8/patrick-mchardy-and-copyright-profiteering
thanks for the links! This is something that needs addressing in the long run,
so far I still have "putting out a new release at all" on my TODO list ^^
I didn't use any of the mentioned tools myself yet.
Is this something you care about right now and want to work on?
Or should I just add it to the TODO list?
Regarding license compliance: I recently tried to get the linux kernel
source code for my Pocketbook ebook reader, it was a PITA.
You can sometimes be lucky if vendors release source code at all.
Cheers,
Tom
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
