From general-return-69603-archive-asf-public=cust-asf.ponee.io@incubator.apache.org Fri Jun 7 18:46:46 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 6573518067E for ; Fri, 7 Jun 2019 20:46:46 +0200 (CEST) Received: (qmail 81066 invoked by uid 500); 7 Jun 2019 18:46:44 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 81050 invoked by uid 99); 7 Jun 2019 18:46:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jun 2019 18:46:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 8C0AD1A32BD for ; Fri, 7 Jun 2019 18:46:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.802 X-Spam-Level: X-Spam-Status: No, score=0.802 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id ehJ6dhnYOZ3T for ; Fri, 7 Jun 2019 18:46:42 +0000 (UTC) Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id A47915F180 for ; Fri, 7 Jun 2019 18:46:41 +0000 (UTC) Received: by mail-ed1-f49.google.com with SMTP id c26so4392448edt.1 for ; Fri, 07 Jun 2019 11:46:41 -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:content-transfer-encoding; bh=3NASFU+n9DlvKQVomiYYYBKVhII8pjNKXF1PkpYP5Zg=; b=mO5PARdB1LZgSBcZth8USTdusmUg5q29+9T4VRUXQNTOrRzTNMzx63o3olkXT/ySeI 0vqVE+o2dsS1m4vY82LGGcN38fvXsXdogxnfyc+VHA0j03ZFDLRPU6aqCngZPcS7rrXH VN/GYyYJdhksY2x4748ymX1j97VPEtYAe/ooYkWZMKBp+mvDJiyP8bM8DdZ+7hgaulus JH0Msb3KxOfbUvFA58TQWhew3KcNUmhUImZHkwbNT08+r2PJaZnKqiV4GcnLzkFORrHG dIVK7gORLH2ySvwAwJdaZpR6xC70epqAbOgJlBbzaqzies+JpUw+rZ9BhAJ+rVpIVhvR qnVQ== X-Gm-Message-State: APjAAAUtWFj1iGPU0hAqdeQ3gJBACnzj1OsFyiZFnU1AtzT9BAcP2LXP xs0Xum/N9ZqdN4Fzj8Nirkg3hP4KNjnJFFUaxVWmEkC4 X-Google-Smtp-Source: APXvYqzJC5z/go8ENQeW6uCxepN0N5uHKb8EIju2d4J6Lh3iyF91Mh7huusJVzQNmdO8vMqYTBe66ohm/f/ETw5YiIg= X-Received: by 2002:a05:6402:28e:: with SMTP id l14mr8827426edv.11.1559933193960; Fri, 07 Jun 2019 11:46:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sam Ruby Date: Fri, 7 Jun 2019 14:46:20 -0400 Message-ID: Subject: Re: [IMPORTANT] Board proposal on podling releases To: general@incubator.apache.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jun 7, 2019 at 2:00 PM Craig Russell wrote: > > Hi Justin, > > As a board member, I'm not comfortable with granting a blanket exception = to policy that might put us at legal risk. > > As an IPMC member, I think that we do not want to allow podlings to relea= se material that might put us at legal risk. I do think that the IPMC under= today's policy has the ability to decide whether a podling release puts us= at risk and therefore should be blocked. So I am not convinced that the IP= MC needs to ask for this waiver from the board. > > My understanding as an IPMC member is that there are some items in a rele= ase that can be allowed where they would not be in a TLP release. These th= ings have historically drawn -1 votes from IPMC members. > > I think there is consensus that a podling release does not have to confor= m in every respect to what we expect from a TLP release. > > I think that the incubator IPMC should first flesh out (on the general@ l= ist) which materials in a podling release are > a) fine; > b) minor issue (file a JIRA and fix before graduation); or > c) blocker (puts the foundation at risk). > > The detail of what is minor versus what it a blocker is the most importan= t thing that needs clarity. As of now, I don't see consensus although I see= movement. Drilling down by taking the contents of the draft incubator report: "Serious problems, such as; including GPL licensed software, including compiled code, or copyright violations, in a release is currently seen as a reason to vote -1 on a release." Picking them off one by one: 1) Is it legal to include GPL licensed software in releases? The answer is yes... as long as we comply with the terms of that license. In the case of strong copyleft licenses, that could mean that the podling release itself may need also be GPL licensed. 2) Is it legal to include compiled code in releases? Yes. 3) Is it legal to include copyright violations in releases? No. > Craig - Sam Ruby > > On Jun 6, 2019, at 11:45 PM, Justin Mclean w= rote: > > > > Hi, > > > > As suggested I=E2=80=99ve collated information from several threads and= turned it into a proposal for the board. Any edits, feedback, agreement, d= isagreement etc etc is welcome. In particular it would be nice to hear som= e feedback from people who are in favour of this. > > > > Note that this is important as it probably changes the advice mentors w= ill give their podlings on releases and change in a positive way how we vot= e on releases with serious issues in them. If you are a mentor or vote on r= eleases please read it. Again feedback welcome. > > > > If the board agrees with the proposal I think we'll need to update the = incubator DISCLAIMER. I=E2=80=99ve suggested what we might add in the propo= sal but the exact changes can to be discussed here. If the board disagrees = with the proposal I suggest we discuss and come up with a list of serious i= ssues that the IPMC recommends voting -1 vote on a release. This is just gu= idance, not rules, and there may of course be exceptions. (For instance you= could ask VP legal for an exception as has been done in the past.) That w= ay mentors and podlings have clear expectations on releases must contain. > > > > The proposal can be found in the draft board report. [1] > > > > Thanks, > > Justin > > > > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/June2019 > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org > > For additional commands, e-mail: general-help@incubator.apache.org > > > > Craig L Russell > clr@apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org > For additional commands, e-mail: general-help@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org