Return-Path: X-Original-To: apmail-community-dev-archive@minotaur.apache.org Delivered-To: apmail-community-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1F08E176EE for ; Tue, 6 Jan 2015 20:26:50 +0000 (UTC) Received: (qmail 35283 invoked by uid 500); 6 Jan 2015 20:26:51 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 35008 invoked by uid 500); 6 Jan 2015 20:26:51 -0000 Mailing-List: contact dev-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list dev@community.apache.org Received: (qmail 34994 invoked by uid 99); 6 Jan 2015 20:26:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jan 2015 20:26:50 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mdrob@mdrob.com designates 209.85.214.174 as permitted sender) Received: from [209.85.214.174] (HELO mail-ob0-f174.google.com) (209.85.214.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jan 2015 20:26:45 +0000 Received: by mail-ob0-f174.google.com with SMTP id uz6so4518920obc.5 for ; Tue, 06 Jan 2015 12:26:25 -0800 (PST) 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=/3zPgbwh7mPp0ZL8Lkxtmwo5oOdX+OSahqXcSx7n/vM=; b=B/DoODUbcURTO/OrKhxl763SYIbePSdRcnrCtvQdiKF+FodyWI1mGBVsZONjfPRgML jVBcH+X6HEnvnjOdrjyeRZkXZP1ijoDTH01JFFEz/R3A3BGafpj92upfx7fFGviXQ3UK qAZI+RhulW66uUg0hLuZ7X2fFR9Yv8RhWvPyTBm6Vdbbkic7K7CEnDHAOuC3y6s1Ew+D bnz7qzf1e2We0lEILeeQmp9cOVNrj5Y1CS3rgJ4J/KbhX9YQ6kTajriVaxE9TvDNu/4i iEbV4C1jYOA6erP4hQJJGdZXf4pzB7eqHGMpIw4LW/Rnp1OY+SBe9Uzdb4uWgmDn9yGr SDTg== X-Gm-Message-State: ALoCoQnYhKXgtswGfyOdZgLekkCdoHH5vlPL8Uo3ZppqwlPfIurdoxxMJ/bMwU9cacGcjVtQ59Oi MIME-Version: 1.0 X-Received: by 10.60.92.40 with SMTP id cj8mr57632930oeb.43.1420575984898; Tue, 06 Jan 2015 12:26:24 -0800 (PST) Received: by 10.182.130.77 with HTTP; Tue, 6 Jan 2015 12:26:24 -0800 (PST) X-Originating-IP: [206.174.249.135] In-Reply-To: References: Date: Tue, 6 Jan 2015 14:26:24 -0600 Message-ID: Subject: Re: A maturity model for Apache projects From: Mike Drob To: dev@community.apache.org Content-Type: multipart/alternative; boundary=047d7b33d326f4f072050c019ea2 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b33d326f4f072050c019ea2 Content-Type: text/plain; charset=UTF-8 On Tue, Jan 6, 2015 at 2:12 PM, Marvin Humphrey wrote: > On Tue, Jan 6, 2015 at 11:16 AM, Mike Drob wrote: > > > How much of this is already covered by the Incubation process? Hopefully > > projects don't revert to improper licensing or closed development after > > they graduate. > > The absence of clear documentation harms projects both during and after > incubation. > Agreed. > > For example, when a project transgresses against some aspect of Apache > policy, > PMC members may not speak out because they don't feel confident that they > grok > our muddled rules well enough to argue the point -- even though they were > trained on them during incubation. > This is something I've personally experienced, but I hadn't realized that this is what it was until just now, when you explained it. > > Many people around the Foundation have unreasonable expectations about the > Incubator's ability to assure good behavior in perpetuity for its > graduates. > > Meanwhile, the abominable state of our policy documentation goes unnoticed. > I prefer to consider the expectations optimistic rather than unreasonable. Would it be easier to start from the Incubator checklist/guidelines and figure out how to expand that to the general populace rather than building a new model from scratch? Or is the idea that things are so bad that we need a drastic cut? I think the Incubator guidelines are reasonable, and have referred to them several times when discussing policy. I suppose that could be consequence of poorly maintained documents, though. Polishing those and hosting them somewhere on www.a.o (instead of incubator.a.o) would likely go a long way. > Marvin Humphrey > Mike --047d7b33d326f4f072050c019ea2--