From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2974 invoked by alias); 11 Jul 2012 21:34:58 -0000 Received: (qmail 2837 invoked by uid 22791); 11 Jul 2012 21:34:58 -0000 X-SWARE-Spam-Status: No, hits=-6.0 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 11 Jul 2012 21:34:35 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q6BLYYoC012383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 11 Jul 2012 17:34:34 -0400 Received: from fche.csb (vpn-11-235.rdu.redhat.com [10.11.11.235]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q6BLYXgW002314; Wed, 11 Jul 2012 17:34:33 -0400 Received: by fche.csb (Postfix, from userid 2569) id F381158182; Wed, 11 Jul 2012 17:34:32 -0400 (EDT) To: Joachim Protze Cc: gdb@sourceware.org Subject: Re: Licencing policy for gdb Python plugins References: <4FFC2F18.9000708@tu-dresden.de> From: fche@redhat.com (Frank Ch. Eigler) Date: Wed, 11 Jul 2012 21:34:00 -0000 In-Reply-To: <4FFC2F18.9000708@tu-dresden.de> (Joachim Protze's message of "Tue, 10 Jul 2012 15:33:12 +0200") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-07/txt/msg00028.txt.bz2 Joachim Protze writes: > [...] while the discussion in the last session of the GNU cauldron, > the question raised, whether there is a licencing policy for Python > plugins, [...] Unless one believes the gdb plugin api is copyrightable in its own right (and thus license compatibility comes up), perhaps discussion should be limited to how the gdb project would accept said plugins as a contribution. - FChE