NuGet: need to update AfterLutz package metadata

[Aaronontheweb]

There are a few areas of NuGet metadata that need to be updated so users of the .AL NuGet packages get the right information about the current status / home / maintainers of the project:

Akkatecture/Directory.Build.props

Lines 3 to 5 in b7c7fd0

	<Authors>Lutando Ngqakaza</Authors>
	<Company>Lutando Ngqakaza</Company>
	<Copyright>Copyright (c) Lutando Ngqakaza 2018 - 2020</Copyright>

Akkatecture/Directory.Build.props

Line 8 in b7c7fd0

<RepositoryUrl>https://github.com/Lutando/Akkatecture</RepositoryUrl>

[SeanFarrow]

Happy to do this, if it would help. One question, should we dynamically generate the end copyright year, so that we don't have to keep updating it when a new year roles around?

[malclear]

I think automating the adjustment of year would be great.
A question I have is regarding how we should maintain Lutando's copyright information. I know it's common to list previous authors in the individual code pages, but should we update his copyright dates there as well every year?
@Aaronontheweb, thoughts?

[Aaronontheweb]

I would add a copyright header that preserve's Lutando's copyright but adds a new one for "AfterLutz Contributors" or the "AfterLutz Project" - that's probably the best way to do it.

[SeanFarrow]

Yep, that’s what makes complete sense to me. From: Aaron Stannard ***@***.***> Sent: 09 January 2022 20:26 To: AfterLutz/Akkatecture ***@***.***> Cc: Sean Farrow ***@***.***>; Comment ***@***.***> Subject: Re: [AfterLutz/Akkatecture] NuGet: need to update AfterLutz package metadata (Issue #64) I would add a copyright header that preserve's Lutando's copyright but adds a new one for "AfterLutz Contributors" or the "AfterLutz Project" - that's probably the best way to do it. — Reply to this email directly, view it on GitHub<#64 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AALDK7TOZ5MK4HZLUAGIF53UVHVO3ANCNFSM5LOYJSTA>. You are receiving this because you commented.Message ID: ***@***.***>

[malclear]

I agree we should keep his name there. Should we increment the year on Lutando's copyright each year, or freeze it at 2021? *Malcolm Learner* ***@***.*** (214) 208-7005

…

On Sun, Jan 9, 2022 at 2:26 PM Aaron Stannard ***@***.***> wrote: I would add a copyright header that preserve's Lutando's copyright but adds a new one for "AfterLutz Contributors" or the "AfterLutz Project" - that's probably the best way to do it. — Reply to this email directly, view it on GitHub <#64 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACY3VUKYQK2RWVBR7BYJK3LUVHVO3ANCNFSM5LOYJSTA> . You are receiving this because you commented.Message ID: ***@***.***>

[Aaronontheweb]

Freeze it

[SeanFarrow]

Yep, definitely agree we should freeze it. Can you have two copyright tags in a nuspec file? I’ve never seen that done, so am thinking the answer is no. From: Aaron Stannard ***@***.***> Sent: 10 January 2022 14:52 To: AfterLutz/Akkatecture ***@***.***> Cc: Sean Farrow ***@***.***>; Comment ***@***.***> Subject: Re: [AfterLutz/Akkatecture] NuGet: need to update AfterLutz package metadata (Issue #64) Freeze it — Reply to this email directly, view it on GitHub<#64 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AALDK7RDZ7RILIM6Y63WCR3UVLXCRANCNFSM5LOYJSTA>. You are receiving this because you commented.Message ID: ***@***.***>

[Aaronontheweb]

Can you have two copyright tags in a nuspec file? I’ve never seen that done, so am thinking the answer is no.

No. I'd just delimit them via commas.