Missing guidance on adding contributors to licensing headers about msix-packagesupportframework HOT 8 CLOSED

Thanks for bringing it up Rafael. Lets go with the same approach as the .Net Foundation team and add "contributors" where appropriate. I will update our guidance.

from msix-packagesupportframework.

If I add a completely new translation unit, adding Copyright (c) Microsoft Corporation would be incorrect as no copyright was transferred. I suspect this is one reason why the .NET Foundation uses different language:

// Licensed to the .NET Foundation under one or more agreements.
// The .NET Foundation licenses this file to you under the MIT license.
// See the LICENSE file in the project root for more information.

from msix-packagesupportframework.

Looking into few .NET repositories I don't see one standard way.
dotnet/cli uses the format you suggested above;
// Copyright (c) .NET Foundation and contributors. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
and dotnet/coreclr uses various formats dependents on the library they use.
Or are you saying we can't use both: "Copyright (c) Microsoft Corporation" and "Copyright (C) Microsoft Corporation and contributors"?

from msix-packagesupportframework.

If I create foo.cpp, I implicity own it so I'd be inclined to put only Copyright (c) Rafael Rivera. Just something to be aware of!

Does LCA have recommendations we can apply here?

from msix-packagesupportframework.

Let me check with CLA and get back to you.

from msix-packagesupportframework.

Checked with legal, we can use this format; in fact it is their guidance.
It also reinforces why we typically need to go through the OSS process when we take back in our own project code (with external modifications) into our own proprietary projects.
//-------------------------------------------------------------------------------------------------------
Copyright (c) Rafael Rivera. All rights reserved.
Licensed under the MIT license. See LICENSE file in the project root for full license information.
//-------------------------------------------------------------------------------------------------------

from msix-packagesupportframework.

@vladimp LCA has spoken! Thanks for the quick follow up.

from msix-packagesupportframework.

No Problem

from msix-packagesupportframework.