On Mon, Nov 10, 2025 at 6:19 AM Richard W.M. Jones <[email protected]> wrote:
>
> On Mon, Nov 10, 2025 at 06:03:23AM -0500, Neal Gompa wrote:
> > On Mon, Nov 10, 2025 at 5:51 AM Richard W.M. Jones via legal
> > <[email protected]> wrote:
> > >
> > >
> > > We're thinking of using the DevCon tool inside virt-v2v:
> > >
> > > https://github.com/microsoft/Windows-driver-samples/tree/main/setup/devcon
> > >
> > > The license on the files looks like Microsoft proprietary ("All Rights
> > > Reserved", no other information).  However the license of the
> > > repository as a whole is MS-PL which is on the Allowed list:
> > >
> > > https://github.com/microsoft/Windows-driver-samples/blob/main/LICENSE
> > >
> > > So I'm really looking for an opinion on whether this is good enough
> > > for Fedora, or if we need to get some clarification (from Microsoft?)
> > >
> > > This was asked about before, and not really answered clearly:
> > >
> > > https://github.com/microsoft/Windows-driver-samples/issues/60
> > >
> >
> > Has anyone tried sending a pull request to add the licensing
> > information to the headers to all the files in the repository? If they
> > accept that, it could resolve the issue.
>
> I guess we could have something that would add an SPDX line, eg
> this sort of patch:
>
>  Copyright (c) Microsoft Corporation.  All rights reserved.
> +SPDX-License-Identifier: MS-PL
>
> For our purposes we'd only need it for files under devcon/
>

If you can easily do it for all files, that makes it considerably more
likely to get it merged.



-- 
真実はいつも一つ!/ Always, there's only one truth!
-- 
_______________________________________________
legal mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to