Return-Path: X-Original-To: apmail-infrastructure-dev-archive@minotaur.apache.org Delivered-To: apmail-infrastructure-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 BAC85100D9 for ; Thu, 22 Jan 2015 18:16:20 +0000 (UTC) Received: (qmail 82480 invoked by uid 500); 22 Jan 2015 18:16:20 -0000 Delivered-To: apmail-infrastructure-dev-archive@apache.org Received: (qmail 82349 invoked by uid 500); 22 Jan 2015 18:16:20 -0000 Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: infrastructure-dev@apache.org Delivered-To: mailing list infrastructure-dev@apache.org Received: (qmail 82336 invoked by uid 99); 22 Jan 2015 18:16:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jan 2015 18:16:20 +0000 X-ASF-Spam-Status: No, hits=0.3 required=10 tests=RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of list@toolazydogs.com does not designate 209.85.220.44 as permitted sender) Received: from [209.85.220.44] (HELO mail-pa0-f44.google.com) (209.85.220.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jan 2015 18:16:15 +0000 Received: by mail-pa0-f44.google.com with SMTP id rd3so2341881pab.3 for ; Thu, 22 Jan 2015 10:15:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=JZWZuBdTG1FEqNqfbLPCXZaUj/sW/qYwmDJHWbGKeVI=; b=OnQi3hgZRn7aD29Thu4ovQAgBSeP8cfUCCQK0NZc6oMrDy9rb+SenpXn4I7J6a3dkB OXFoI+UAC23nfa5F6c3EP56DmaY6QvBE1YSrgOB0Lgc33ThuQkcL5L1WMvOYd1hVDaJh m8C0t7MyuQgC5t22x1Esuabpw6cO8WspOnVhhqhc8vBkTJDrbt8ByphtLXKcYs66bPGX TOQ08/nyW3ZCVhxvhgY2Q9kUZr4eh7Ztjyh/qfZKkxzem0x1vYQfSKbN0lUWG2Qwhras YfTJRuOPGaIP0R04/HltjGiEqtsE6T6tR2q0lq1S47HP40FoPbdI2DgJptsAEdlPGFxu iD5g== X-Gm-Message-State: ALoCoQkiqs6+YRyb1Ib7+ukKO7Zkp7ClusXZXL5Th37r/1tBLcDRcTBTdJUMz1NPagMvRIFSdxCt X-Received: by 10.66.139.129 with SMTP id qy1mr4248580pab.21.1421950554336; Thu, 22 Jan 2015 10:15:54 -0800 (PST) Received: from acabrera-mn.linkedin.biz (dagmar1.corp.linkedin.com. [69.28.149.129]) by mx.google.com with ESMTPSA id x10sm9937658pas.18.2015.01.22.10.15.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 22 Jan 2015 10:15:53 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: Brooklyn not in http://people.apache.org/committers-by-project.html From: "Alan D. Cabrera" In-Reply-To: Date: Thu, 22 Jan 2015 10:15:51 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <0796270C-2516-4944-AD90-96ED41500F7D@toolazydogs.com> References: <4E0AE711-6F64-434C-86C9-A9811FC729D6@toolazydogs.com> <45FDAEE3-8701-4BA3-B3C3-57A7A7DDE6E1@toolazydogs.com> <933D3493-8B77-44F3-A76F-C7C80328DFAB@toolazydogs.com> <07AECD11-CA8F-42AB-8D3D-70B0D6764720@toolazydogs.com> <54BF775B.4040305@apache.org> <89AE5C12-B40D-4CF3-9084-4E2CD170111F@toolazydogs.com> <7B9FC44C-EAE8-4C7B-BB3E-9DE8FC2A01DD@toolazydogs.com> To: infrastructure-dev@apache.org X-Mailer: Apple Mail (2.1993) X-Virus-Checked: Checked by ClamAV on apache.org > On Jan 22, 2015, at 10:05 AM, sebb wrote: >=20 > On 22 January 2015 at 17:54, Alan D. Cabrera = wrote: >>=20 >>> On Jan 22, 2015, at 9:36 AM, jan i wrote: >>>=20 >>> On 22 January 2015 at 18:04, Alan D. Cabrera > wrote: >>>=20 >>>>=20 >>>>> On Jan 22, 2015, at 8:14 AM, sebb wrote: >>>>>=20 >>>>> On 22 January 2015 at 15:52, Alan D. Cabrera >>>> wrote: >>>>>>=20 >>>>>>> On Jan 22, 2015, at 7:34 AM, sebb wrote: >>>>>>>=20 >>>>>>> AIUI PPMCs have no legal status within the ASF. >>>>>>>=20 >>>>>>> If LDAP committee entries are created for them, then the tooling = needs >>>>>>> to be adjusted to cater for this. >>>>>>> There is other data that really needs to go into LDAP as well. >>>>>>> AIUI changing LDAP structure is not trivial so ideally all the = changes >>>>>>> need to be done at once. >>>>>>=20 >>>>>> I am espousing for the creation of a new OU, i.e. Podlings. >>>>>=20 >>>>> It would still require changes to LDAP and Infra processes. >>>>=20 >>>> Changes in LDAP, of course, but these are new orthogonal changes. = Changes >>>> to Infra processes, yes, but we are cleaning technical debt here = and so >>>> that=E2=80=99s to be expected. The change is not burdensome. >>>>=20 >>>>>>> However if my suggestion of adding -ppmc entries to asf-auth is >>>>>>> acceptable to Infra, then this can be implemented very quickly. >>>>>>=20 >>>>>> What is this asf-auth file? Is it the subversion authorization = file? >>>>>=20 >>>>> Yes. >>>>>=20 >>>>> As noted else-thread that is how Corinthia committers are = documented. >>>>=20 >>>> Pointing to a prior use of a bad practice is not itself a = justification of >>>> the bad practice. >>>>=20 >>>=20 >>> Why not make a step by step approach, looking at the mail is is = obvious >>> that a LDAP change right now misses: >>> - backing from infra >>> - backing from the IPMC chair (who would need at least for a while = to do >>> the job) >>> - a discussion if a REST API is so secure that Infra will allow it = (to be >>> honest I would not) >>> - the tools that use the REST API. >>>=20 >>> It is a lot more than just collecting the data. >>>=20 >>> as Sebb suggested we can expand the svn-auth file, it is not perfect = but it >>> collects the information PPMC and committer in one place. Once that = is done >>> we could have a longer discussion on >>> - which information should in general be appended to LDAP (and do we = want >>> LDAP to be our central repository for committer data) >>> - if yes, can we allow a REST API that updates LDAP, and how to make = it >>> secure >>=20 >>=20 >> If you want to put PPMC and committer information in a Subversion = authorization file, I can=E2=80=99t stop you. What worries me, other = than it is a bad practice, is that we=E2=80=99re simply adding more = technical debt that needs to be undone; you guys are already using it as = an excuse to not move to LDAP. >=20 > It is not *adding* to the technical debt. >=20 > The asf-auth file is the correct place for defining SVN groups that > are not in LDAP. > The podlings that do use SVN *already* have the committer groups here. >=20 > It so happens that the ppmc groups won't have any SVN folders that = need auth. > Likewise the podlings that use Git don't *need* committer entries. If you don=E2=80=99t see how that is not a poor practice, then there=E2=80= =99s nothing else I can say. Let=E2=80=99s just drop it and agree to = disagree. >> But please, I am totally baffled by the pushback on putting this = information in LDAP. This is not rocket science and there=E2=80=99s not = a lot of refactoring that needs to be done to get us in a good place. >=20 > I'm equally baffled why you seem unwilling to try this simple = improvement. I apologize for my tone. Regards, Alan