Re: Move Licentia to KDEREVIEW

[Jonathan Riddell]

I opened an Issue in line with the new practice
https://invent.kde.org/sdk/licentia/-/issues/2


On Tue, 8 Nov 2022 at 02:14, Felipe Kinoshita  wrote:

> Yes, I'm still interested in working on them, just lost motivation because
> it was taking too long for someone to review it.
>
> On Thu, Nov 3, 2022, 09:44 Jonathan Riddell  wrote:
>
>> Same question on this one Felipe, are you still interested in working on
>> the app?  It seems stuck in kdereview with no recent development.
>>
>> Jonathan
>>
>>
>> On Fri, 8 Jul 2022 at 06:37, Felipe Kinoshita  wrote:
>>
>>> Hey, I'd like to move Licentia  to
>>> KDEREVIEW.
>>>
>>> Licentia is a simple app targeted at developers/creators who need to
>>> decide which license is suited to their projects, Licentia helps with that
>>> by listing a bunch of licenses, which with it's permissions, conditions and
>>> limitations, instructions about how to add a license to your project and a
>>> list of known projects that use said license.
>>>
>>> Thanks,
>>> Felipe.
>>>
>>

Re: Move Licentia to KDEREVIEW

[Felipe Kinoshita]

Yes, I'm still interested in working on them, just lost motivation because
it was taking too long for someone to review it.

On Thu, Nov 3, 2022, 09:44 Jonathan Riddell  wrote:

> Same question on this one Felipe, are you still interested in working on
> the app?  It seems stuck in kdereview with no recent development.
>
> Jonathan
>
>
> On Fri, 8 Jul 2022 at 06:37, Felipe Kinoshita  wrote:
>
>> Hey, I'd like to move Licentia  to
>> KDEREVIEW.
>>
>> Licentia is a simple app targeted at developers/creators who need to
>> decide which license is suited to their projects, Licentia helps with that
>> by listing a bunch of licenses, which with it's permissions, conditions and
>> limitations, instructions about how to add a license to your project and a
>> list of known projects that use said license.
>>
>> Thanks,
>> Felipe.
>>
>

Re: Move Licentia to KDEREVIEW

[Jonathan Riddell]

Same question on this one Felipe, are you still interested in working on
the app?  It seems stuck in kdereview with no recent development.

Jonathan


On Fri, 8 Jul 2022 at 06:37, Felipe Kinoshita  wrote:

> Hey, I'd like to move Licentia  to
> KDEREVIEW.
>
> Licentia is a simple app targeted at developers/creators who need to
> decide which license is suited to their projects, Licentia helps with that
> by listing a bunch of licenses, which with it's permissions, conditions and
> limitations, instructions about how to add a license to your project and a
> list of known projects that use said license.
>
> Thanks,
> Felipe.
>

Re: Move Licentia to KDEREVIEW

[Kevin Kofler]

Am Montag, 8. August 2022 21:05:44 CEST schrieb David Redondo:

Do the licenses really require these specially named files? Note that all
used licenses in the repo are all included in the repos in a 
LICENSES folder.
it would be a massive oversight and afaik there were never complains from 
fedora when this was started three years ago (https://phabricator.kde.org/

T11550)


The licenses do not require specific file names, so as long as *every* 
repository includes the licenses relevant for that repository in a 
LICENSES/ folder, and as long as these licenses are included in the 
tarball, you are good to go.


You just need to ensure that *every* tarball contains all licenses used by 
any code in the same tarball. (Then they should also end up in every source 
and binary RPM, but that is the distribution's job.) Where exactly does not 
matter. (But it is not enough to point to some dependency's copy of the 
license, the license really has to be included with every tarball.)


   Kevin Kofler

Re: Move Licentia to KDEREVIEW

[David Redondo]

Am Montag, 11. Juli 2022, 13:34:14 CEST schrieb Kevin Kofler:
> David Redondo wrote:
> > Am Montag, 11. Juli 2022, 12:37:09 CEST schrieben Sie:
> >> Please note that Gitlab and other places still do rely on LICENSE (or
> >> COPYING) files being present (and I guarantee there is distribution
> >> tooling out there that does the same too) so I wouldn't be too quick to
> >> shoot down LICENSE files in the root of repositories.
> >> 
> >> Cheers,
> >> Ben
> > 
> > That ship has long sailed.
> > At least for frameworks and most of plasma has been converted.
> 
> In the case of the GNU licenses, it is actually a violation of the license
> to not ship a LICENSE/COPYING file along with the project. (This matters as
> soon as you incorporate even a handful lines of third-party code under the
> same license.)
> 
> It is also Fedora policy that upstream SHOULD include a license file and
> that we will file bugs upstream to request them being added where they are
> missing. I believe that Fedora is not the only distribution with such a
> policy.
> 
> So any commits removing license files ought to be reverted ASAP. A pointer
> is not enough.
> 
> Kevin Kofler

Do the licenses really require these specially named files? Note that all
used licenses in the repo are all included in the repos in a LICENSES folder.
it would be a massive oversight and afaik there were never complains from 
fedora when this was started three years ago (https://phabricator.kde.org/
T11550)

David

Re: Move Licentia to KDEREVIEW

[Felipe Kinoshita]

ping!

On Tue, Jul 12, 2022, 13:40 Felipe Kinoshita  wrote:

> Just added SPDX instructions. Could you take a look?
>
> Thanks,
> Felipe.
>
> On Mon, Jul 11, 2022 at 2:47 AM David Redondo 
> wrote:
>
>> Am Freitag, 8. Juli 2022, 07:36:57 CEST schrieb Felipe Kinoshita:
>> > Hey, I'd like to move Licentia  to
>> > KDEREVIEW.
>> >
>> > Licentia is a simple app targeted at developers/creators who need to
>> decide
>> > which license is suited to their projects, Licentia helps with that by
>> > listing a bunch of licenses, which with it's permissions, conditions and
>> > limitations, instructions about how to add a license to your project
>> and a
>> > list of known projects that use said license.
>> >
>> > Thanks,
>> > Felipe.
>>
>> I am not entirely happy about the Instruction to use a license being 'put
>> a
>> LICENSE file in the root directory' when it's a pattern we are going away
>> from
>> and towards reuse compliance.
>> Maybe display the SPDX tag instead?
>>
>> David
>>
>>
>>
>>
>>

Re: Move Licentia to KDEREVIEW

[Felipe Kinoshita]

Just added SPDX instructions. Could you take a look?

Thanks,
Felipe.

On Mon, Jul 11, 2022 at 2:47 AM David Redondo  wrote:

> Am Freitag, 8. Juli 2022, 07:36:57 CEST schrieb Felipe Kinoshita:
> > Hey, I'd like to move Licentia  to
> > KDEREVIEW.
> >
> > Licentia is a simple app targeted at developers/creators who need to
> decide
> > which license is suited to their projects, Licentia helps with that by
> > listing a bunch of licenses, which with it's permissions, conditions and
> > limitations, instructions about how to add a license to your project and
> a
> > list of known projects that use said license.
> >
> > Thanks,
> > Felipe.
>
> I am not entirely happy about the Instruction to use a license being 'put
> a
> LICENSE file in the root directory' when it's a pattern we are going away
> from
> and towards reuse compliance.
> Maybe display the SPDX tag instead?
>
> David
>
>
>
>
>

Re: Move Licentia to KDEREVIEW

[Felipe Kinoshita]

I will work on adding REUSE instructions as well!

Thanks,
Felipe.

On Mon, Jul 11, 2022, 10:11 David Hurka  wrote:

> On Monday, July 11, 2022 7:47:36 AM CEST David Redondo wrote:
> > I am not entirely happy about the Instruction to use a license being
> 'put a
> > LICENSE file in the root directory' when it's a pattern we are going away
> > from and towards reuse compliance.
> > Maybe display the SPDX tag instead?
>
> Interestingly, the project Licentia itself uses the REUSE method, with
> named
> license files in the LICENSE/ directory.
>
> It seems to me that both LICENSE.txt and REUSE are valid methods, so
> Licentia’s instructions should support both.
>
> Personally, I prefer REUSE. :)
>
> David
>
>
>

Re: Move Licentia to KDEREVIEW

[David Hurka]

On Monday, July 11, 2022 7:47:36 AM CEST David Redondo wrote:
> I am not entirely happy about the Instruction to use a license being 'put a
> LICENSE file in the root directory' when it's a pattern we are going away
> from and towards reuse compliance.
> Maybe display the SPDX tag instead?

Interestingly, the project Licentia itself uses the REUSE method, with named 
license files in the LICENSE/ directory.

It seems to me that both LICENSE.txt and REUSE are valid methods, so 
Licentia’s instructions should support both.

Personally, I prefer REUSE. :)

David

Re: Move Licentia to KDEREVIEW

[David Redondo]

Am Montag, 11. Juli 2022, 12:37:09 CEST schrieben Sie:
>
> Please note that Gitlab and other places still do rely on LICENSE (or
> COPYING) files being present (and I guarantee there is distribution tooling
> out there that does the same too) so I wouldn't be too quick to shoot down
> LICENSE files in the root of repositories.
> 
> Cheers,
> Ben

That ship has long sailed. 
At least for frameworks and most of plasma has been converted.

David

Re: Move Licentia to KDEREVIEW

[Ben Cooksley]

On Mon, Jul 11, 2022 at 9:10 PM David Redondo  wrote:

> Am Freitag, 8. Juli 2022, 07:36:57 CEST schrieb Felipe Kinoshita:
> > Hey, I'd like to move Licentia  to
> > KDEREVIEW.
> >
> > Licentia is a simple app targeted at developers/creators who need to
> decide
> > which license is suited to their projects, Licentia helps with that by
> > listing a bunch of licenses, which with it's permissions, conditions and
> > limitations, instructions about how to add a license to your project and
> a
> > list of known projects that use said license.
> >
> > Thanks,
> > Felipe.
>
> I am not entirely happy about the Instruction to use a license being 'put
> a
> LICENSE file in the root directory' when it's a pattern we are going away
> from
> and towards reuse compliance.
> Maybe display the SPDX tag instead?
>

Please note that Gitlab and other places still do rely on LICENSE (or
COPYING) files being present (and I guarantee there is distribution tooling
out there that does the same too) so I wouldn't be too quick to shoot down
LICENSE files in the root of repositories.


>
> David
>
>
>
Cheers,
Ben

Re: Move Licentia to KDEREVIEW

[David Redondo]

Am Freitag, 8. Juli 2022, 07:36:57 CEST schrieb Felipe Kinoshita:
> Hey, I'd like to move Licentia  to
> KDEREVIEW.
> 
> Licentia is a simple app targeted at developers/creators who need to decide
> which license is suited to their projects, Licentia helps with that by
> listing a bunch of licenses, which with it's permissions, conditions and
> limitations, instructions about how to add a license to your project and a
> list of known projects that use said license.
> 
> Thanks,
> Felipe.

I am not entirely happy about the Instruction to use a license being 'put a 
LICENSE file in the root directory' when it's a pattern we are going away from 
and towards reuse compliance. 
Maybe display the SPDX tag instead?

David

Re: Move Licentia to KDEREVIEW

[Felipe Kinoshita]

I'm getting most of the data from the choosealicence project.

On Sun, Jul 10, 2022, 08:45 Adriaan de Groot  wrote:

> On Friday, 8 July 2022 07:36:57 CEST Felipe Kinoshita wrote:
> > Hey, I'd like to move Licentia  to
> > KDEREVIEW.
> >
> > Licentia is a simple app targeted at developers/creators who need to
> decide
> > which license is suited to their projects, Licentia helps with that by
> > listing a bunch of licenses, which with it's permissions, conditions and
> > limitations, instructions about how to add a license to your project and
> a
> > list of known projects that use said license.
>
> Where are you getting the data describing each license? In particular, the
> tags / metadata for them. There are plenty of online
> license-choice-helpers,
> although those generally have an agenda (e.g. GitHub's license chooser)
> and
> lots of ontologies for license description (e.g. one I made up in 2009 but
> lost the icons for).
>
> Asking for information, not for a hidden "why bother" agenda.
>
> [ade]

Re: Move Licentia to KDEREVIEW

[Adriaan de Groot]

On Friday, 8 July 2022 07:36:57 CEST Felipe Kinoshita wrote:
> Hey, I'd like to move Licentia  to
> KDEREVIEW.
> 
> Licentia is a simple app targeted at developers/creators who need to decide
> which license is suited to their projects, Licentia helps with that by
> listing a bunch of licenses, which with it's permissions, conditions and
> limitations, instructions about how to add a license to your project and a
> list of known projects that use said license.

Where are you getting the data describing each license? In particular, the 
tags / metadata for them. There are plenty of online license-choice-helpers, 
although those generally have an agenda (e.g. GitHub's license chooser) and 
lots of ontologies for license description (e.g. one I made up in 2009 but 
lost the icons for).

Asking for information, not for a hidden "why bother" agenda.

[ade]

signature.asc
Description: This is a digitally signed message part.

Move Licentia to KDEREVIEW

[Felipe Kinoshita]

Hey, I'd like to move Licentia  to
KDEREVIEW.

Licentia is a simple app targeted at developers/creators who need to decide
which license is suited to their projects, Licentia helps with that by
listing a bunch of licenses, which with it's permissions, conditions and
limitations, instructions about how to add a license to your project and a
list of known projects that use said license.

Thanks,
Felipe.