To be fair, it appears that many source files refer to a non-existent LICENSE file. Someone on the CrOS team should probably just add the LICENSE file for depthcharge and/or contact mal@ to see how the license info is being collected these days (e.g. for chrome://os-credits <https://www.chromium.org/chromium-os/licenses>).
On Tue, Dec 19, 2017 at 9:19 AM, ron minnich <rminn...@gmail.com> wrote: > Is there even a question? Looks like aaron just answered the original > question, which boils down to Read The Source? > > On Tue, Dec 19, 2017 at 7:58 AM Aaron Durbin via coreboot < > coreboot@coreboot.org> wrote: > >> On Tue, Dec 19, 2017 at 8:03 AM, <ttu...@codeaurora.org> wrote: >> >>> On 2017-12-15 13:39, ttu...@codeaurora.org wrote: >>> >>>> Preparing to mirror the coreboot.org requires us to vet the various >>>> licenses, etc. >>>> >>>> There doesn't appear to be a LICENSE or COPYING file in the Depthcharge >>>> tree. >>>> >>>> My understanding is that Depthcharge is licensed GPLv2 (or later). >>>> >>>> How would I confirm this with an online source? >>>> >>>> Cheers, >>>> T.mike >>>> >>> >>> Should this query be posted on Chromium list rather than Coreboot list? >>> >>> >> Probably. The files in the depthcharge repository have licenses at the >> top of each file. They are GPLv2. >> >> Cheers, >>> T.mike >>> >>> -- >>> coreboot mailing list: coreboot@coreboot.org >>> https://mail.coreboot.org/mailman/listinfo/coreboot >>> >> -- >> coreboot mailing list: coreboot@coreboot.org >> https://mail.coreboot.org/mailman/listinfo/coreboot > > > -- > coreboot mailing list: coreboot@coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot >
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
