From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) by sourceware.org (Postfix) with ESMTPS id 2E02E396E877 for ; Mon, 14 Jun 2021 20:19:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2E02E396E877 Received: by mail-ej1-x62c.google.com with SMTP id my49so18678712ejc.7 for ; Mon, 14 Jun 2021 13:19:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zT1BIczSnqkOfzl58wtWFtLnAN6M4Kz3THlrXu+s7es=; b=eyNyh1LJtR71bldfqDLwNHHXiZfHbs3geKAwVXvssLuJOS9zurVlwnbjoPk8LhYfrU fXNQ1fh+gDXZYuAmwkSDnPQFovDs8COOjFuhc32IrZg951BhSEGryndXyTWc2M+o339+ 1SusRXCLFwrYPQV1i4bAzb+8XFgmMOYWJih+aicLEsGBKEySI8NsY9S4aBoqvcHtZRyW NWk/a1U1PSEfkv0EFi90UPdDuLFsTSCGLv2MeH3SCDmdZKkq2KMvDBWx6er3JnEvl43g SmPUYZMj5V2BTzxTR0FKXqOSrKZk8E5oUvDD02zinCQ5y9oFN9MUgKFw1/KrfNo209pu 8Ckw== X-Gm-Message-State: AOAM531Rb7PyfBFXdbHigDeQQJ1iOmBUOEg2yzjL1rFpvQKDEvmozyHo eH4GDSsdOshz1xQfnL5htk2ej8JnfYCWXo8Voeo= X-Google-Smtp-Source: ABdhPJwWfVnQgaLG9JoGkMAQMBJtJtEKzWLZqe2mb/scdnixcUjqiOy4TupKNchO2PgzscQcbOGOO7e7NOga6m/E73I= X-Received: by 2002:a17:907:1de6:: with SMTP id og38mr17142735ejc.471.1623701948267; Mon, 14 Jun 2021 13:19:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Matt Turner Date: Mon, 14 Jun 2021 13:18:56 -0700 Message-ID: Subject: Re: Seeking input from developers: glibc copyright assignment policy. To: "Carlos O'Donell" Cc: libc-alpha , Jakub Jelinek , "Joseph S. Myers" , Maxim Kuvyrkov Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2021 20:19:10 -0000 On Mon, Jun 14, 2021 at 11:53 AM Carlos O'Donell via Libc-alpha wrote: > > Community, > > glibc was created as part of the GNU Project but has grown to operate as > an autonomous project. As part of the GNU Toolchain the glibc stewards > support the gcc project policy changes presented here: > https://gcc.gnu.org/pipermail/gcc/2021-June/236182.html > > The glibc stewards are seeking input from developers to decide if the project > should relax the requirement to assign copyright for all changes to the > Free Software Foundation as follows: > > Contributors who have an FSF Copyright Assignment wouldn't need to > change anything. Contributors who wish to utilize the Developer Certificate > of Origin[1] would add a Signed-off-by message to their commit messages. > > The changes to accept patches with or without FSF copyright assignment > would be effective on August 2nd, and would apply to all open branches. Yes, please! To give a concrete example of what a barrier this can be to contributors: When I was in graduate school and contracting for OLPC, I wanted to contribute a fix to GCC [1]. I was asked to complete the copyright assignment paperwork and disclosed that I was a student in university. That necessitated the FSF paperwork being approved by my university... Research universities often have technology-transfer rules, designed around handling inventions created by professors and research assistants. Despite not doing research for the university, not working on GCC for the university, not doing the work with anyone from the university, and not doing the work with any property from the university, the university required me to fill out paperwork describing the "invention" and provide information on how they might "market it". A process which began in October finally concluded in April, the month before I graduated. Not coincidentally, someone in the tech-transfer office asked me if I could simply wait until after I graduated to contribute... I can imagine most people would simply not contribute if they knew they'd have to go through this (or neglect to mention to the FSF that they're a university student, as I would do if I had known). None of this is the fault of the copyright assignment policy per se, but it does demonstrate how it's not as simple as signing a piece of paper. [1] I believe it was https://patchwork.ozlabs.org/project/gcc/patch/CAEdQ38ECXJahf8sp8b7Yq5NgOQBh9MQ7s3LxfSmZJhJva-UfDg@mail.gmail.com/