On 6/26/24 5:24 AM, Florian Weimer wrote:
* Miroslav Suchý:
Dne 25. 06. 24 v 1:09 odp. Miro Hrončok napsal(a):
Could you make the comment something like this?
# Automatically converted from old format: GPLv2
# TODO check if there are other licenses to be listed
License: GPL-2.0-onl
On 6/26/24 8:41 AM, Richard Fontana wrote:
On Wed, Jun 26, 2024 at 10:24 AM Jerry James wrote:
On Wed, Jun 26, 2024 at 6:17 AM Miroslav Suchý wrote:
We will get valid SPDX formula.
Some legacy license names contain spaces. Simply slapping
"LicenseRef-Fedora-" on the front will only affect
On 6/19/24 6:07 PM, Richard Fontana wrote:
On Wed, Jun 19, 2024 at 11:58 AM Miro Hrončok wrote:
On 18. 06. 24 18:46, Miroslav Suchý wrote:
Hi.
I am going to do the mass change of the license from GPLv2 to GPL-2.0-only
Hi.
How do you know the License tag is not supposed to be e.g. "GPL-2.0
On 9/2/23 5:32 AM, Miroslav Suchý wrote:
Dne 02. 09. 23 v 13:07 Zbigniew Jędrzejewski-Szmek napsal(a):
"python-lit warning: valid as old and new and no changelong entry, please check"
The License string is valid as both the old-style Fedora license and a SPDX
expression, and the tooling did n
Top-posting a few comments related to this thread in total (instead of
multiple responses to separate posts) and in hopes that people will be
more likely to see/read :)
As to Rust saying MPL-2.0+ is invalid - this is likely because Rust
thinks of the SPDX License List as *only* what is this pa
In support of package maintainers still needing to update their license
info for their packages - how can we help keep the momentum going?
We have our next "office hours" on Tuesday, 27th of June at 10am US
eastern time - that is for anyone to get help, ask questions, etc.
We just had a hackf
Hi all,
Given we just had the hackfest last week, we are cancelling the standing
SPDX Office Hours for tomorrow, May 23rd.
The next SPDX Office Hours will be June 27th at 8am US eastern time at
https://meet.google.com/jbz-erzk-btc?authuser=0&hs=122
Thanks!
Jilayne___
On 5/19/23 4:03 AM, Miro Hrončok wrote:
On 19. 05. 23 4:28, Jilayne Lovejoy wrote:
Packages from this list
https://pagure.io/copr/license-validate/blob/main/f/eln-not-migrated.txt
that were worked on during or as a result of the hackfest are listed
below. If you are a package maintainer of a
Speaking of Wednesday's hackfest... thanks to all who attended. It was a
good session with worthwhile discussion and progress made on some ELN
packages - yeah!
It'd be great to get feedback from those who attended or wanted to but
couldn't on doing another one and timing (e.g., day of the week
Hi Richard, You should be looking at the new documentation at
https://docs.fedoraproject.org/en-US/legal/ for the list of approved
licenses. The old wiki page does have a note at the top to the new link,
but we should make it redirect automatically, so thanks for the
reminder! We do have a list
Hi all,
Just a reminder that the Fedora Legal -SPDX Hackfest is next week,
Wednesday, May 17th.
See details below!
Thanks,
Jilayne
Forwarded Message
Subject: [Fedora-legal-list] [Fedocal] Reminder meeting : Fedora Legal
- SPDX Hackfest
Date: Wed, 10 May 2023 10:00:03
Hi all,
We are going to reschedule the ELN Hackfest for Wednesday, May 17th.
Same time and meeting info as below. We'll send another reminder a few
days out.
Sorry for the last minute notice!
Cheers,
Jilayne
On 4/17/23 11:25 AM, David Cantrell wrote:
Time corrections from the original ann
On 3/27/23 1:19 AM, Andreas Schneider wrote:
On Sunday, 26 March 2023 01:56:32 CEST Miroslav Suchý wrote:
Two weeks ago we had:
* 23107 spec files in Fedora
* 29503license tags in all spec files
* 20302 tags have not been converted to SPDX yet
* 8096 tags can be trivially converted using `
Thanks to all the package maintainers who have been diligently updating
their packages to SPDX identifiers! Here are a few interesting stats:
- 160 issues in the Fedora-license-data, which has resulted in 34 new
license/TOML files being added to the data, and 18 more ready to be
added
https:/
every two weeks was my understanding too, although I don't think Miro
set up a recurring invite b/c we were also going to try to alternate the
time of day to accommodate various time zones.
Bi-weekly is ambiguous in English, I've had this challenge before!
Jilayne
On 1/12/23 10:14 AM, Richard
> On Tue, Nov 15, 2022, 12:24 Miro Hrončok
>
>
>
> I package askalono-cli which can detect license texts and outputs an SPDX
> identifier: https://github.com/jpeddicord/askalono
>
> We use it in go2rpm.
>
Looking through this thread, it seems there are a range of tools that package
maintai
> Dne 10. 11. 22 v 12:04 Remi Collet napsal(a):
>
>
> Open an issue for
>
> https://gitlab.com/fedora/legal/fedora-license-data
>
> if there is need for new SPDX id then Jilayne will request it for you and add
> it to
> fedora-license-data.
>
Just a quick process clarification here!
General
Hi all,
Sorry for joining the thread late, but a few thoughts below!
> Tl;dr Please start migrating your license tag to SPDX now. Tool
> `license-fedora2spdx` is
> your friend. The JSON format
> changed - but is backwards compatible.
>
>
> Hi.
>
> I want to update you on where we are with SP
On 8/24/22 8:56 AM, Richard Fontana wrote:
Cross-posting this to the devel list.
On Tue, Aug 23, 2022 at 11:41 PM Maxwell G wrote:
Hi Legal folks,
Can you please consider removing the following rule?
Fedora package maintainers are expected to announce upstream license
changes that they be
That would be a bit hard since a large number of the SPDX ids are the same as
the Fedora short names. That being said, some of the more commonly found
licenses are not the same.
It might be interesting to see how many packages have had a license update
since this change, which could indicate u
looks good!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedorap
Thanks!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproje
Hi,
Did you or could you also update the License: field to "EPL-2.0" as per the
change to using SPDX identifiers. :)
Thanks!
Jilayne
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject
23 matches
Mail list logo
