unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bone Baboon <bone.baboon@disroot.org>
To: guix-devel@gnu.org
Subject: Rust freedom issue claim
Date: Sun, 23 May 2021 23:24:24 -0400	[thread overview]
Message-ID: <87bl90byqf.fsf@disroot.org> (raw)

This is an article from Hyperbola about the Rust trademark. It claims
that Rust has a freedom issue.
<https://wiki.hyperbola.info/doku.php?id=en:main:rusts_freedom_flaws>

I searched for this in the Guix bug and devel mailing list archive but
did not see it.

I would like to know how others interpret this claim of Rust having a
freedom issue.

# Linux-libre

If Rust does have a freedom issue then there is potential that it could
have an impact on Linux-libre.  Recently there was a RFC for adding
support for Rust to the Linux kernel
<https://lkml.org/lkml/2021/4/14/1023>.  Linus Torvalds's response is
here <https://lkml.org/lkml/2021/4/14/1099>.

# Responses on Freenode

I asked about Hyperbola's claim of a Rust freedom issue on
##rust@ire.freenode.net and these were some of the responses I
received.  However it appears that the core of Hyperbola's claim
remains unaddressed by these responses.

"<SpaceManiac> the trademarks are now owned by the Rust Foundation
rather than Mozilla, but the Rust Media Guide has not been updated to
reflect this"

"<lifeless> bone-baboon: https://github.com/rust-lang/rust/issues/53287
is closed by https://github.com/rust-lang/rust/pull/59748"

"<lifeless> bone-baboon: whether you consider is a freedom issue or not
is a matter of viewpoint - debian doesn't seem to care at this point,
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=cargo
shows no bugs open related to trademarks"


             reply	other threads:[~2021-05-24 17:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24  3:24 Bone Baboon [this message]
2021-05-25  2:01 ` Rust freedom issue claim 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
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=87bl90byqf.fsf@disroot.org \
    --to=bone.baboon@disroot.org \
    --cc=guix-devel@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).