From: Bone Baboon <bone.baboon@disroot.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Rust freedom issue claim
Date: Thu, 03 Jun 2021 14:38:18 -0400 [thread overview]
Message-ID: <87sg1y94kl.fsf@disroot.org> (raw)
In-Reply-To: <87k0nlsh0c.fsf@gnu.org>
Ludovic Courtès writes:
> Before triggering an alarm, I would check what major distros, and Debian
> in particular, are doing about Rust; I have not heard of any concerns so
> far. If the Rust trademark turns out to be a concern, distros should
> try hard, collectively, to resolve it through dialog with Rust
> Foundation people.
I started a thread about the Rust trademark policy on the debian-legal
mailing list.
<https://lists.debian.org/debian-legal/2021/06/msg00003.html>
I participated in the Free Software Foundation's most recent Free
Software Directory meeting. Several participants in the meeting where
interested in the Rust trademark policy. I started a thread on the
directory-discuss mailing list as was suggested in the meeting.
<https://lists.gnu.org/archive/html/directory-discuss/2021-06/msg00000.html>
The Free Software Foundation's licensing team will be taking a serious
look at the Rust trademark policy issue (no time frame was given).
<https://lists.gnu.org/archive/html/directory-discuss/2021-06/msg00001.html>
After reading further on the topic and receiving feedback I have written
an update to my understanding of the Rust trademark policy.
<https://lists.gnu.org/archive/html/directory-discuss/2021-06/msg00000.html>
next prev parent reply other threads:[~2021-06-03 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 3:24 Rust freedom issue claim Bone Baboon
2021-05-25 2:01 ` Bone Baboon
2021-05-26 14:32 ` Ludovic Courtès
2021-05-26 15:14 ` Pjotr Prins
2021-05-27 14:47 ` Joshua Branson
2021-05-27 16:28 ` Pjotr Prins
2021-05-27 20:23 ` Jack Hill
2021-06-03 18:38 ` Bone Baboon [this message]
2021-06-08 13:00 ` Ludovic Courtès
2021-06-12 18:49 ` Bone Baboon
2021-06-12 21:31 ` Vagrant Cascadian
2021-06-13 18:20 ` Leo Famulari
2021-06-15 12:38 ` Bone Baboon
2021-06-19 3:21 ` Bone Baboon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg1y94kl.fsf@disroot.org \
--to=bone.baboon@disroot.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).