[-- Attachment #1: Type: text/plain, Size: 409 bytes --] Hello Guix Development, Attached is my Guix package submission of Microsoft Cascadia Code fonts. This is my very first attempt to make a Guix package contribution and I did this in less than 30 minutes, copying the package descriptions of IBM Plex fonts and modifying a few things. I dont' know what protocols I may have missed 😅 Would you please let me know how to proceed from here? Regards, Yasu [-- Attachment #2: 0001-i.patch --] [-- Type: text/x-patch, Size: 1310 bytes --] From a86683caa6ee17e881c91cc103d30f844d6a6b34 Mon Sep 17 00:00:00 2001 From: Yasuaki Kudo <yasu@yasuaki.com> Date: Sun, 10 Jan 2021 16:11:26 +0900 Subject: [PATCH] i --- gnu/packages/fonts.scm | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/gnu/packages/fonts.scm b/gnu/packages/fonts.scm index 11a8e6261b..d080eb5567 100644 --- a/gnu/packages/fonts.scm +++ b/gnu/packages/fonts.scm @@ -78,6 +78,23 @@ #:use-module (gnu packages python-xyz) #:use-module (gnu packages xorg)) +(define-public font-cascadia-code + (package + (name "font-cascadia-code") + (version "2009.22") + (source (origin + (method url-fetch) + (uri (string-append "https://github.com/microsoft/cascadia-code/releases/download/" + "v" version "/CascadiaCode-" version ".zip")) + (sha256 + (base32 + "0ilqvy7hzw35w5mig6zp2lny30fm8kmpzh69fg2npr4snyacq6w0")))) + (build-system font-build-system) + (home-page "https://github.com/microsoft/cascadia-code/") + (synopsis "Microsoft Cascadia Code") + (description "This package provides Microsoft Cascadia Code fonts.") + (license license:silofl1.1))) + (define-public font-ibm-plex (package (name "font-ibm-plex") -- 2.30.0
[-- Attachment #1: Type: text/plain, Size: 841 bytes --] Hello, On Sun, Jan 10, 2021 at 9:04 AM yasu <yasu@yasuaki.com> wrote: > Attached is my Guix package submission of Microsoft Cascadia Code > fonts. > > This is my very first attempt to make a Guix package contribution and I > did this in less than 30 minutes, copying the package descriptions of > IBM Plex fonts and modifying a few things. I dont' know what > protocols I may have missed 😅 > > Would you please let me know how to proceed from here? > LGTM small nitpicks: * 80 columns (you can auto-format the code with etc/indent-code.el, this is documented here: https://guix.gnu.org/manual/en/html_node/Formatting-Code.html) * I've not checked the difference size (nor that it matters) between zip and tar.gz, you may want to use the smallest one to minimize download. Thanks -- Vincent Legoll [-- Attachment #2: Type: text/html, Size: 1458 bytes --]
[-- Attachment #1: Type: text/plain, Size: 300 bytes --] On Sun, Jan 10, 2021 at 9:46 AM Vincent Legoll <vincent.legoll@gmail.com> wrote: > * I've not checked the difference size (nor that it matters) between zip > and tar.gz, you may want to use the smallest one to minimize download. > I just did, and the tgz wins: 3.1 MB vs 5.7 MB -- Vincent Legoll [-- Attachment #2: Type: text/html, Size: 733 bytes --]
Hello Vincent, there is no .tar of the fonts however, that's a source tarball generated by github. To be fair, one should probably build this font (and other fonts) from source instead. In particular, we might want to package nerd-fonts[1] first, since Cascadia appears to be an iteration of it. Regards, Leo [1] https://github.com/ryanoasis/nerd-fonts
Hello,
On Sun, Jan 10, 2021 at 10:16 AM Leo Prikler
<leo.prikler@student.tugraz.at> wrote:
> there is no .tar of the fonts however, that's a source tarball
> generated by github. To be fair, one should probably build this font
> (and other fonts) from source instead. In particular, we might want to
> package nerd-fonts[1] first, since Cascadia appears to be an iteration
> of it.
Yes you're right, I did not look at the submitted scm hard enough to
see it.
Sorry for the noise.
--
Vincent Legoll
Thank you for your comments!
Because I don't have a lot of time, is it ok to just re-format the original submission, get it committed with the comment that the package needs to be compiled rather than copied, when someone (or I) wants to so properly?
Cheers,
Yasu
> On Jan 10, 2021, at 18:16, Leo Prikler <leo.prikler@student.tugraz.at> wrote:
>
> Hello Vincent,
>
> there is no .tar of the fonts however, that's a source tarball
> generated by github. To be fair, one should probably build this font
> (and other fonts) from source instead. In particular, we might want to
> package nerd-fonts[1] first, since Cascadia appears to be an iteration
> of it.
>
> Regards,
> Leo
>
> [1] https://github.com/ryanoasis/nerd-fonts
>
>
Hi Yasu, I don't think it'll be so simple. It appears, that nerd-fonts already includes – or at least has the potential to include – some non-free glyphs, which would in turn then be part of Cascadia. An instance would be pomicons [1], which are licensed as CC BY-NC-ND. A reviewer would first have to verify, that Cascadia is indeed wholly covered under the OFL or at least under a set of free licenses. Yes, it sucks having to put that much effort into packaging a font, but if you just want to have a workable font for programming, there are probably better solutions than Cascadia, some of which are already packaged in Guix – e.g. font-fira-code. Regards, Leo [1] https://github.com/gabrielelana/pomicons Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo: > Thank you for your comments! > > Because I don't have a lot of time, is it ok to just re-format the > original submission, get it committed with the comment that the > package needs to be compiled rather than copied, when someone (or I) > wants to so properly? > > Cheers, > Yasu > > > > On Jan 10, 2021, at 18:16, Leo Prikler < > > leo.prikler@student.tugraz.at> wrote: > > > > Hello Vincent, > > > > there is no .tar of the fonts however, that's a source tarball > > generated by github. To be fair, one should probably build this > > font > > (and other fonts) from source instead. In particular, we might > > want to > > package nerd-fonts[1] first, since Cascadia appears to be an > > iteration > > of it. > > > > Regards, > > Leo > > > > [1] https://github.com/ryanoasis/nerd-fonts > > > >
Hi Leo,
Understood, and this level of scrutiny is actually an encouraging sign that Guix has standards! 😄
I am happy enough to have it this way for my personal use for now. Later, when I have more time, let me revisit.
I have not experimented with this yet but I also understand I can create a separate repository as well. Maybe that will also do😄
Regards,
Yasu
> On Jan 10, 2021, at 19:38, Leo Prikler <leo.prikler@student.tugraz.at> wrote:
>
> Hi Yasu,
>
> I don't think it'll be so simple. It appears, that nerd-fonts already
> includes – or at least has the potential to include – some non-free
> glyphs, which would in turn then be part of Cascadia. An instance
> would be pomicons [1], which are licensed as CC BY-NC-ND. A reviewer
> would first have to verify, that Cascadia is indeed wholly covered
> under the OFL or at least under a set of free licenses.
>
> Yes, it sucks having to put that much effort into packaging a font, but
> if you just want to have a workable font for programming, there are
> probably better solutions than Cascadia, some of which are already
> packaged in Guix – e.g. font-fira-code.
>
> Regards,
> Leo
>
> [1] https://github.com/gabrielelana/pomicons
>
> Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo:
>> Thank you for your comments!
>>
>> Because I don't have a lot of time, is it ok to just re-format the
>> original submission, get it committed with the comment that the
>> package needs to be compiled rather than copied, when someone (or I)
>> wants to so properly?
>>
>> Cheers,
>> Yasu
>>
>>
>>> On Jan 10, 2021, at 18:16, Leo Prikler <
>>> leo.prikler@student.tugraz.at> wrote:
>>>
>>> Hello Vincent,
>>>
>>> there is no .tar of the fonts however, that's a source tarball
>>> generated by github. To be fair, one should probably build this
>>> font
>>> (and other fonts) from source instead. In particular, we might
>>> want to
>>> package nerd-fonts[1] first, since Cascadia appears to be an
>>> iteration
>>> of it.
>>>
>>> Regards,
>>> Leo
>>>
>>> [1] https://github.com/ryanoasis/nerd-fonts
>>>
>>>
>
I created a 'low-standard-guix' repository and moved the submitted package there, for now :-) https://github.com/yugawara/low-standard-guix/blob/master/README.md Again, when I get time, let me see if I can properly package Cascadia Code fonts! Cheers, Yasu On Sun, 2021-01-10 at 19:56 +0900, Yasuaki Kudo wrote: > Hi Leo, > > Understood, and this level of scrutiny is actually an encouraging > sign that Guix has standards! 😄 > > I am happy enough to have it this way for my personal use for > now. Later, when I have more time, let me revisit. > > I have not experimented with this yet but I also understand I can > create a separate repository as well. Maybe that will also do😄 > > Regards, > Yasu > > > On Jan 10, 2021, at 19:38, Leo Prikler < > > leo.prikler@student.tugraz.at> wrote: > > > > Hi Yasu, > > > > I don't think it'll be so simple. It appears, that nerd-fonts > > already > > includes – or at least has the potential to include – some non-free > > glyphs, which would in turn then be part of Cascadia. An instance > > would be pomicons [1], which are licensed as CC BY-NC-ND. A > > reviewer > > would first have to verify, that Cascadia is indeed wholly covered > > under the OFL or at least under a set of free licenses. > > > > Yes, it sucks having to put that much effort into packaging a font, > > but > > if you just want to have a workable font for programming, there are > > probably better solutions than Cascadia, some of which are already > > packaged in Guix – e.g. font-fira-code. > > > > Regards, > > Leo > > > > [1] https://github.com/gabrielelana/pomicons > > > > Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo: > > > Thank you for your comments! > > > > > > Because I don't have a lot of time, is it ok to just re-format > > > the > > > original submission, get it committed with the comment that the > > > package needs to be compiled rather than copied, when someone (or > > > I) > > > wants to so properly? > > > > > > Cheers, > > > Yasu > > > > > > > > > > On Jan 10, 2021, at 18:16, Leo Prikler < > > > > leo.prikler@student.tugraz.at> wrote: > > > > > > > > Hello Vincent, > > > > > > > > there is no .tar of the fonts however, that's a source tarball > > > > generated by github. To be fair, one should probably build > > > > this > > > > font > > > > (and other fonts) from source instead. In particular, we might > > > > want to > > > > package nerd-fonts[1] first, since Cascadia appears to be an > > > > iteration > > > > of it. > > > > > > > > Regards, > > > > Leo > > > > > > > > [1] https://github.com/ryanoasis/nerd-fonts > > > > > > > >
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --] I might be wrong, but I thought fonts were considered non-functional data. If that's the case, isn't cc-by-nc-nd acceptable? Le 10 janvier 2021 05:38:16 GMT-05:00, Leo Prikler <leo.prikler@student.tugraz.at> a écrit : >Hi Yasu, > >I don't think it'll be so simple. It appears, that nerd-fonts already >includes – or at least has the potential to include – some non-free >glyphs, which would in turn then be part of Cascadia. An instance >would be pomicons [1], which are licensed as CC BY-NC-ND. A reviewer >would first have to verify, that Cascadia is indeed wholly covered >under the OFL or at least under a set of free licenses. > >Yes, it sucks having to put that much effort into packaging a font, but >if you just want to have a workable font for programming, there are >probably better solutions than Cascadia, some of which are already >packaged in Guix – e.g. font-fira-code. > >Regards, >Leo > >[1] https://github.com/gabrielelana/pomicons > >Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo: >> Thank you for your comments! >> >> Because I don't have a lot of time, is it ok to just re-format the >> original submission, get it committed with the comment that the >> package needs to be compiled rather than copied, when someone (or I) >> wants to so properly? >> >> Cheers, >> Yasu >> >> >> > On Jan 10, 2021, at 18:16, Leo Prikler < >> > leo.prikler@student.tugraz.at> wrote: >> > >> > Hello Vincent, >> > >> > there is no .tar of the fonts however, that's a source tarball >> > generated by github. To be fair, one should probably build this >> > font >> > (and other fonts) from source instead. In particular, we might >> > want to >> > package nerd-fonts[1] first, since Cascadia appears to be an >> > iteration >> > of it. >> > >> > Regards, >> > Leo >> > >> > [1] https://github.com/ryanoasis/nerd-fonts >> > >> > [-- Attachment #2: Type: text/html, Size: 2506 bytes --]
[-- Attachment #1: Type: text/plain, Size: 2353 bytes --] Well, let me know if that's the case! After all, my submission is almost identical as the existing packages such as font-ibm-plex and font-inconsolata? I would prefer not to "fork" as another repository if I can avoid it! -Yasu On Sun, 2021-01-10 at 07:28 -0500, Julien Lepiller wrote: > I might be wrong, but I thought fonts were considered non-functional > data. If that's the case, isn't cc-by-nc-nd acceptable? > > Le 10 janvier 2021 05:38:16 GMT-05:00, Leo Prikler < > leo.prikler@student.tugraz.at> a écrit : > > Hi Yasu, > > > > I don't think it'll be so simple. It appears, that nerd-fonts > > already > > includes – or at least has the potential to include – some non-free > > glyphs, which would in turn then be part of Cascadia. An instance > > would be pomicons [1], which are licensed as CC BY-NC-ND. A > > reviewer > > would first have to verify, that Cascadia is indeed wholly covered > > under the OFL or at least under a set of free licenses. > > > > Yes, it sucks having to put that much effort into packaging a font, > > but > > if you just want to have a workable font for programming, there are > > probably better solutions than Cascadia, some of which are already > > packaged in Guix – e.g. font-fira-code. > > > > Regards, > > Leo > > > > [1] https://github.com/gabrielelana/pomicons > > > > Am Sonntag, den 10.01.2021, 19:11 +0900 schrieb Yasuaki Kudo: > > > Thank you for your comments! > > > > > > Because I don't have a lot of time, is it ok to just re-format > > > the > > > original submission, get it committed with the comment that the > > > package needs to be compiled rather than copied, when someone (or > > > I) > > > wants to so properly? > > > > > > Cheers, > > > Yasu > > > > > > > > > > On Jan 10, 2021, at 18:16, Leo Prikler < > > > > leo.prikler@student.tugraz.at> wrote: > > > > > > > > Hello Vincent, > > > > > > > > there is no .tar of the fonts however, that's a source tarball > > > > generated by github. To be fair, one should probably build > > > > this > > > > font > > > > (and other fonts) from source instead. In particular, we might > > > > want to > > > > package nerd-fonts[1] first, since Cascadia appears to be an > > > > iteration > > > > of it. > > > > > > > > Regards, > > > > Leo > > > > > > > > [1] https://github.com/ryanoasis/nerd-fonts > > > > > > > > [-- Attachment #2: Type: text/html, Size: 3373 bytes --]
Hi Julien, Am Sonntag, den 10.01.2021, 07:28 -0500 schrieb Julien Lepiller: > I might be wrong, but I thought fonts were considered non-functional > data. If that's the case, isn't cc-by-nc-nd acceptable? Not according to the FSDG: > [Non-functional data] can be included in a free system distribution > as long as its license gives you permission to copy and redistribute, > both for commercial and non-commercial purposes. IIUC CC BY-ND would be covered if we indeed consider fonts to be non- functional data, but not CC BY-NC and certainly not CC BY-NC-ND. It goes on to list a hypothetical example of a game map, which is somewhat ironic, considering that games more often disqualify themselves for the FSDG through the use of entirely non-free assets or assets rather than being GPL-incompatible through the use of assets, that don't allow derivative work. Of course, the former is a subset of the latter, but the point I'm trying to make here, is that the latter is sadly not even a concern for many (aspiring) game devs out there. It also reminds me, that I have yet to code up a fully GPL/FSDG- compatible game myself – I'll get there some day, I promise. TL;DR: Non-functional data is fine if it is commercially verbatim- copyable. Regards, Leo
Le 10 janvier 2021 08:09:03 GMT-05:00, Leo Prikler <leo.prikler@student.tugraz.at> a écrit :
>Hi Julien,
>
>Am Sonntag, den 10.01.2021, 07:28 -0500 schrieb Julien Lepiller:
>> I might be wrong, but I thought fonts were considered non-functional
>> data. If that's the case, isn't cc-by-nc-nd acceptable?
>
>Not according to the FSDG:
>> [Non-functional data] can be included in a free system distribution
>> as long as its license gives you permission to copy and redistribute,
>> both for commercial and non-commercial purposes.
>IIUC CC BY-ND would be covered if we indeed consider fonts to be non-
>functional data, but not CC BY-NC and certainly not CC BY-NC-ND.
>
I see, thanks for correcting me!
Hi, Leo Prikler <leo.prikler@student.tugraz.at> writes: > Am Sonntag, den 10.01.2021, 07:28 -0500 schrieb Julien Lepiller: >> I might be wrong, but I thought fonts were considered non-functional >> data. If that's the case, isn't cc-by-nc-nd acceptable? > > Not according to the FSDG: >> [Non-functional data] can be included in a free system distribution >> as long as its license gives you permission to copy and redistribute, >> both for commercial and non-commercial purposes. > IIUC CC BY-ND would be covered if we indeed consider fonts to be non- > functional data, but not CC BY-NC and certainly not CC BY-NC-ND. Also, fonts are specifically listed as an example of functional data according to the FSDG: >>> License Rules >>> >>> “Information for practical use” includes software, documentation, fonts, >>> and other data that has direct functional applications. It does not >>> include artistic works that have an aesthetic (rather than functional) >>> purpose, or statements of opinion or judgment. >>> >>> All information for practical use in a free distribution must be >>> available in source form. (“Source” means the form of the information >>> that is preferred for making changes to it.) >>> >>> The information, and the source, must be provided under an >>> appropriate free license. [...] <https://www.gnu.org/distros/free-system-distribution-guidelines.html> Regards, Mark