[PATCH RFC 1/4] LICENSES: Add SIL Open Font License 1.1

2023-11-02 Thread Bagas Sanjaya
Add the license text along with appropriate tags for reference and tooling. The text is taken from the text as distributed in Google Fonts's zip files. As the license itself may or may note be compatible with GPLv2, let's take on the err side and require combining it with GPL-compatible licenses w

[PATCH RFC RESEND 1/4] LICENSES: Add SIL Open Font License 1.1

2023-11-02 Thread Bagas Sanjaya
Add the license text along with appropriate tags for reference and tooling. The text is taken from the text as distributed in Google Fonts's zip files. As the license itself may or may note be compatible with GPLv2, let's take on the err side and require combining it with GPL-compatible licenses w

Re: [PATCH RFC RESEND 1/4] LICENSES: Add SIL Open Font License 1.1

2023-11-02 Thread Greg Kroah-Hartman
On Thu, Nov 02, 2023 at 07:32:19PM +0700, Bagas Sanjaya wrote: > Add the license text along with appropriate tags for reference and > tooling. The text is taken from the text as distributed in Google > Fonts's zip files. > > As the license itself may or may note be compatible with GPLv2, > let's t

Re: [PATCH RFC 1/4] LICENSES: Add SIL Open Font License 1.1

2023-11-02 Thread Richard Fontana
On Thu, Nov 2, 2023 at 8:01 AM Bagas Sanjaya wrote: > > Add the license text along with appropriate tags for reference and > tooling. The text is taken from the text as distributed in Google > Fonts's zip files. > > As the license itself may or may note be compatible with GPLv2, > let's take on th

Re: [PATCH RFC 1/4] LICENSES: Add SIL Open Font License 1.1

2023-11-02 Thread Greg Kroah-Hartman
On Thu, Nov 02, 2023 at 07:00:43PM +0700, Bagas Sanjaya wrote: > Add the license text along with appropriate tags for reference and > tooling. The text is taken from the text as distributed in Google > Fonts's zip files. > > As the license itself may or may note be compatible with GPLv2, > let's t