PLEASE REMOVE ME FROM ALL LISTS!
I tried to remove myself. It didn't work.
I tried to contact the list admin. I did not get an answer.
I'M GONNA SPAM YOUR LISTS UNTIL YOU REMOVE ME!
On 05.03.24 22:15, Alan M Varghese wrote:
Soren,
... but it is also perfectly fine to ship them in the same
Soren,
... but it is also perfectly fine to ship them in the same file.
I think what Wookey is referring to is that GPL and LGPL licenses contain
a line that says something like:
'Copyright (C) 1991, 1999 Free Software Foundation, Inc.'
I believe this copyright refers to the text of the licens
Wookey,
On Tuesday, March 5, 2024 2:51:10 AM MST Wookey wrote:
> On 2024-03-04 11:19 -0700, Soren Stoutner wrote:
> > Alan,
> >
> > These are good questions.
> >
> > 1. Yes, there must be a copyright statement. Only the person, people,
> > group, or organization that holds the copyright can is
On 2024-03-04 11:19 -0700, Soren Stoutner wrote:
> Alan,
>
> These are good questions.
>
> 1. Yes, there must be a copyright statement. Only the person, people,
> group,
> or organization that holds the copyright can issue a license for other people
> to use the work. So, you must have some
Thanks you for the confirmation. Really appreciate it!
They have added a copyright file; so it should be all good. I was likely being
overly cautious and they might have been too. It tripped me up when they
indicated
(L)GPL might have to be treated differently, and when I looked up projects that
On Tue, Mar 05, 2024 at 03:50:27AM +0530, 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?
There are no
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
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
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
Alan,
These are good questions.
1. Yes, there must be a copyright statement. Only the person, people, group,
or organization that holds the copyright can issue a license for other people
to use the work. So, you must have someone claiming a copyright or they do
not have the legal ability to
Sent message incorrectly to debian-mentors-request instead of debian-mentors.
Correcting.
Forwarded Message
Subject: Copyright in LGPL projects
Date: Mon, 4 Mar 2024 11:10:58 +0530
From: Alan M Varghese
To: 1065...@bugs.debian.org
CC: Matthias Geiger , SmartList
Hello Ment
11 matches
Mail list logo