From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 0B3E6385C418 for ; Sun, 17 Jul 2022 22:59:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0B3E6385C418 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (213-10-231-91.fixed.kpn.net [213.10.231.91]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 98D76300047C; Mon, 18 Jul 2022 00:59:54 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 4B9CE2E801D7; Mon, 18 Jul 2022 00:59:54 +0200 (CEST) Date: Mon, 18 Jul 2022 00:59:54 +0200 From: Mark Wielaard To: lkcl Cc: GCC developers Subject: Re: rust non-free-compatible trademark Message-ID: References: <20220717163100.GA1558@gnu.wildebeest.org> <20220717174101.GA4487@gnu.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2022 22:59:57 -0000 Hi Luke, On Sun, Jul 17, 2022 at 07:29:22PM +0100, lkcl wrote: > whilst you *as developers* have been in contact with the Rust Foundation > and presumably have private assurances that your use of the Trademarked > word "rust" is Authorised under License (through either implication or by > actual explicit approval) absolutely nobody else does. As far as I know all discussions have been in public. The Rust Foundation is aware of the gccrs frontend and other "unofficial" implementations. Using the word "rust" in the implementation of the gccrs frontend doesn't need any "Authorization under License". Normal use of a word isn't something that Trademarks prevent. > i appreciate that this is a bloody nuisance. i do however expect the > Rust Foundation to get their act together and act Reasonably and > Fairly to sort out the mess they've accidentally created. I believe the Rust Foundation is reasonable. We aren't using the word mark "Rust" in a way that needs any trademark license. And even if we did the Rust Foundation allows all usage of the word mark as long as you don't deliberately try to confuse about (commercially) shipping a product called "Rust" that is officially endorsed by the Rust Foundation. If the Rust Foundation really believed that some of the marketing we do around the gccrs frontend is confusing they would contact us and if they are reasonable we can adjust the messaging (we can be reasonable too). The best advice I can give you is to listen to what the Rust Foundation itself says about their trademark: Please do not approach users of the trademarks with a complaint. That should be left to the Rust Foundation and its representatives. Thanks! If you have a specific question or concern about promoting Rust or using its trademarks, please contact the Rust Foundation: contact@rustfoundation.org. Cheers, Mark