[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Clarifying blog post licensing
|
From: |
jbranso |
|
Subject: |
Re: Clarifying blog post licensing |
|
Date: |
Sun, 30 Jan 2022 04:21:08 +0000 |
January 27, 2022 12:59 AM, "Jan Nieuwenhuizen" <janneke@gnu.org> wrote:
> Ludovic Courtès writes:
>
>> With a few exceptions, our blog posts do not have a license, which is
>> not great
>
I agree.
Joshua Branson.
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
- Re: Clarifying blog post licensing, (continued)
- Re: Clarifying blog post licensing, Julien Lepiller, 2022/01/26
- Re: Clarifying blog post licensing, Ricardo Wurmus, 2022/01/26
- Re: Clarifying blog post licensing, Maxim Cournoyer, 2022/01/26
- Re: Clarifying blog post licensing, Tobias Geerinckx-Rice, 2022/01/26
- Re: Clarifying blog post licensing, Vagrant Cascadian, 2022/01/26
- Re: Clarifying blog post licensing, Jan Nieuwenhuizen, 2022/01/27
- Re: Clarifying blog post licensing, pelzflorian (Florian Pelz), 2022/01/27
- Re: Clarifying blog post licensing,
jbranso <=