Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EAACE10654 for ; Sun, 22 Mar 2015 16:32:54 +0000 (UTC) Received: (qmail 71182 invoked by uid 500); 22 Mar 2015 16:32:54 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 70935 invoked by uid 500); 22 Mar 2015 16:32:54 -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 70924 invoked by uid 99); 22 Mar 2015 16:32:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Mar 2015 16:32:54 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [209.85.217.174] (HELO mail-lb0-f174.google.com) (209.85.217.174) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Mar 2015 16:32:47 +0000 Received: by lbbsy1 with SMTP id sy1so104159828lbb.1 for ; Sun, 22 Mar 2015 09:32:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=CYnHfz1mY7zBWP8kIfMYNESEZE/dNkV8ddsoKDleTFc=; b=JS/tsX6uLph9oqj4vHyhl1PQBtyWXP02jCQd7CuVq8i6LvcRQwxifWldfsa/8ybacc t5uzqo2ZaJKNg0rJ52GGujBgi0sa1xAA1wEcILneS/gujKgL4jPm17uMEE10ULb2ZNN4 88OlRORHcJT/SFYZPKGpeU9pSAFXckalUYlK2ag6tv7V6ppQ3UPgLoKEsWi5iVhN+dIh I9zvqSyL/NF5fXCVDnSpQH3VwiKf1OKf1XBZQKJTk6wBS9g4C9N1dnCoDoUQlTwSPLpN ash6fpu/0w9sicQK6dOaBXk78G5HL1FlAemk1qAfuV7bZKiWqZr9WkVHAz4CLxrqftCE 4+gg== X-Gm-Message-State: ALoCoQl/Af9g/PfVyAiBf32w7LsyyqQYIAq6WjMZ84B+LhSHbv7az9yzsgqwTeRiy+RDn18fyWBT MIME-Version: 1.0 X-Received: by 10.112.133.2 with SMTP id oy2mr28748766lbb.124.1427041925777; Sun, 22 Mar 2015 09:32:05 -0700 (PDT) Received: by 10.112.199.42 with HTTP; Sun, 22 Mar 2015 09:32:05 -0700 (PDT) X-Originating-IP: [72.214.60.130] In-Reply-To: References: Date: Sun, 22 Mar 2015 09:32:05 -0700 Message-ID: Subject: Re: [POLL] Using this list to discuss pTLP proposals, ok? From: Marvin Humphrey To: "general@incubator.apache.org" Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Sun, Mar 22, 2015 at 6:16 AM, Ross Gardler (MS OPEN TECH) wrote: > My only concern is confusion over pTLP and incubator. That's a manageable > concern but this lost is so large I fear it might keep recurring. > > Just a word of caution, not an objection. I agree that this is a concern. I also think it's important to give pTLP advocates enough space to pursue their inititative independently. However, I think that the recent practice of discussing project proposals on board@apache, a private list, is highly problematic and a disaster waiting to happen. While our nine Directors may ultimately make the decision whether or not to pass a specific resolution creating a pTLP, the establishment of an Apache project is an event with many stakeholders: * Existing developers and users for a project considering a move to Apache * Contributors to competing or related projects * Commercial interests * Press * Anyone who takes an interest in the direction of the Foundation Our Board operates with remarkable transparency to the Membership[1], but not to the wider world. Project proposal discussions need to be visible to the general public -- people need to have their say, and the discussions need to be made available in public archives where they may be perused later and linked, informing future conversations both inside and outside Apache. My preference would be to ask pTLP advocates "which public list" they want to use. Creating a new public mailing list is an option, though the low visibility of a new list makes such an option less than ideal and the usual arguments against Yet Another Mailing List apply. As far as I am concerned, they would be welcome to use general@incubator if that's their choice. Maybe dev@community would be OK though I would be surprised if the ComDev PMC were amenable. Marvin Humphrey [1] For those not familiar with the Foundation's structure: there are a few hundred Members who are effectively Apache's shareholders and who elect the Board annually: https://www.apache.org/foundation/how-it-works.html The Board conducts most of its business on board@apache, an internal list to which Members and Officers may subscribe. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org