No, there isn’t a specific format that is preferred or legally required. And, as Andrey wrote, there is no difference between how this would work for the LGPL as compared to any other license (copyright law has existed for hundreds of years before any open-source license and how you document copyright has not been changed just because open-source licenses came along).
Here is an example of how I do it for one of my projects that is GPL.
You can use the word copyright, the © symbol, or both combined. It doesn’t matter.
The only importance is that it communicates which person, people, or organization hold the copyright, the year or range of years during which the software was written (because that is important to know in relation to when the copyright expires), and then the license those copyright holders are releasing their code under.
Soren
On Monday, March 4, 2024 3:20:27 PM MST Alan M Varghese wrote:
> What I meant was that upstream does not know where to put the copyright
> information or how it should be formatted. Or, to rephrase, is there a
> preferred format for a COPYRIGHT file in a project that uses LGPL?
>
> This is the issue I opened upstream:
> https://github.com/hyprwm/hyprlang/issues/28
>
> On 3/5/24 01:38, Andrey Rahmatullin wrote:
> > On Tue, Mar 05, 2024 at 12:38:00AM +0530, Alan M Varghese wrote:
> >> Hello Soren,
> >>
> >> Thank you for answering my queries.
> >>
> >> I will share this with the upstream project. The project authors are unsure
> >> how to do this for an LGPL project. I will see tomorrow if I can find an
> >> example of an LGPL project that includes the copyright information in the
> >> root of the project. (I found a project that does this for GPL[1], but not
> >> for LGPL).
> >
> > Why would that make a difference?
--
Soren Stoutner
soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.