Return-Path: X-Original-To: apmail-legal-discuss-archive@www.apache.org Delivered-To: apmail-legal-discuss-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9CB8D10048 for ; Wed, 28 May 2014 17:17:43 +0000 (UTC) Received: (qmail 56375 invoked by uid 500); 28 May 2014 17:17:43 -0000 Delivered-To: apmail-legal-discuss-archive@apache.org Received: (qmail 56216 invoked by uid 500); 28 May 2014 17:17:43 -0000 Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: Reply-To: legal-discuss@apache.org List-Id: Delivered-To: mailing list legal-discuss@apache.org Received: (qmail 56209 invoked by uid 99); 28 May 2014 17:17:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2014 17:17:43 +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: unknown (nike.apache.org: error in processing during lookup of aharui@adobe.com) Received: from [207.46.163.203] (HELO na01-bl2-obe.outbound.protection.outlook.com) (207.46.163.203) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2014 17:17:39 +0000 Received: from BL2PR02MB500.namprd02.prod.outlook.com (10.141.95.147) by BL2PR02MB353.namprd02.prod.outlook.com (10.141.91.12) with Microsoft SMTP Server (TLS) id 15.0.944.11; Wed, 28 May 2014 17:16:57 +0000 Received: from BL2PR02MB500.namprd02.prod.outlook.com (10.141.95.147) by BL2PR02MB500.namprd02.prod.outlook.com (10.141.95.147) with Microsoft SMTP Server (TLS) id 15.0.949.11; Wed, 28 May 2014 17:16:56 +0000 Received: from BL2PR02MB500.namprd02.prod.outlook.com ([10.141.95.147]) by BL2PR02MB500.namprd02.prod.outlook.com ([10.141.95.147]) with mapi id 15.00.0949.001; Wed, 28 May 2014 17:16:56 +0000 From: Alex Harui To: "legal-discuss@apache.org" Subject: Re: Continuous release review Thread-Topic: Continuous release review Thread-Index: AQHPeoo201zYX+uQ1Ei/wP6EAkedg5tWJdCAgAAQmgD//5BjgA== Date: Wed, 28 May 2014 17:16:55 +0000 Message-ID: References: <6F8EDB3F-12C5-4D0C-A379-E9AB4F99F391@jaguNET.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.1.140326 x-originating-ip: [63.229.18.221] x-forefront-prvs: 0225B0D5BC x-forefront-antispam-report: SFV:NSPM;SFS:(6009001)(428001)(199002)(189002)(24454002)(479174003)(377454003)(51704005)(99286001)(74662001)(87936001)(76176999)(54356999)(50986999)(77096999)(74502001)(19580405001)(4396001)(31966008)(99396002)(83072002)(83322001)(79102001)(66066001)(83506001)(101416001)(21056001)(36756003)(92726001)(77982001)(46102001)(64706001)(19580395003)(76482001)(92566001)(85852003)(2656002)(81542001)(20776003)(80022001)(86362001)(81342001);DIR:OUT;SFP:;SCL:1;SRVR:BL2PR02MB500;H:BL2PR02MB500.namprd02.prod.outlook.com;FPR:;MLV:sfv;PTR:InfoNoRecords;A:1;MX:1;LANG:en; received-spf: None (: adobe.com does not designate permitted sender hosts) authentication-results: spf=none (sender IP is ) smtp.mailfrom=aharui@adobe.com; Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: adobe.com X-Virus-Checked: Checked by ClamAV on apache.org On 5/28/14 9:56 AM, "Jim Jagielski" wrote: >Let's look at it this way... We need to recall that the ASF >is a legal entity, a Delaware corporation with 501(c)3 >classification. We are also a *significant* player, resource >and source in the IT eco-system. > >People want to play as if we were selling our >kitchen made cookies at a yard sale; we just bake 'em, >sell em, put the money in an old cigar box and >basically just take it all easy and relaxed. Instead, >we are more like Nabisco selling Nutter Butters >(ignore any implication of quality, etc in this >"analogy")... This is serious stuff we are doing, >stuff that people take seriously, stuff that >interests the IRS, the gov't, "partners", etc... I get that there is a difference between potlucks and manufactured food. What I think several of us want to explore is whether the current release policy/process can be automated in places and still be serious about it. For example, I bought some real estate last year, which I consider a serious process, and was pleasantly surprised to see that some of the paperwork could be digitally signed via web apps (but the final closing document required traditional signing). That was quite different that when I last bought real estate merely 5 years ago. Back then, it was all paper and faxing and couriers. And several of us are pushing on this topic because, I'm pretty sure that any bank that still requires all paper and faxing and couriers is finding itself at a competitive disadvantage against the banks that allow digital signing. So the question I have is: where can we use the differences in technology over the past five years to save us time in the release process without sacrificing being "serious". I would offer that at least a couple of things have changed: 1) smartphones make email available to many people virtually 24/7, eliminating some of the reason for waiting 72 hours to close votes 2) CI servers and automated testing frameworks and security software has evolved to the point where you can safely and securely create valid artifacts without human intervention. Thoughts? -Alex --------------------------------------------------------------------- To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org For additional commands, e-mail: legal-discuss-help@apache.org