From dev-return-20779-archive-asf-public=cust-asf.ponee.io@arrow.apache.org Tue Sep 29 18:39:01 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mxout1-ec2-va.apache.org (mxout1-ec2-va.apache.org [3.227.148.255]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id 876D418063B for ; Tue, 29 Sep 2020 20:39:01 +0200 (CEST) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-ec2-va.apache.org (ASF Mail Server at mxout1-ec2-va.apache.org) with SMTP id A2A1C44467 for ; Tue, 29 Sep 2020 18:39:00 +0000 (UTC) Received: (qmail 34000 invoked by uid 500); 29 Sep 2020 18:38:59 -0000 Mailing-List: contact dev-help@arrow.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@arrow.apache.org Delivered-To: mailing list dev@arrow.apache.org Received: (qmail 33970 invoked by uid 99); 29 Sep 2020 18:38:59 -0000 Received: from spamproc1-he-de.apache.org (HELO spamproc1-he-de.apache.org) (116.203.196.100) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2020 18:38:59 +0000 Received: from localhost (localhost [127.0.0.1]) by spamproc1-he-de.apache.org (ASF Mail Server at spamproc1-he-de.apache.org) with ESMTP id 7D78D1FF39B for ; Tue, 29 Sep 2020 18:38:58 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamproc1-he-de.apache.org X-Spam-Flag: NO X-Spam-Score: -0.198 X-Spam-Level: X-Spam-Status: No, score=-0.198 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamproc1-he-de.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-ec2-va.apache.org ([116.203.227.195]) by localhost (spamproc1-he-de.apache.org [116.203.196.100]) (amavisd-new, port 10024) with ESMTP id bYJrJVM0xQ9u for ; Tue, 29 Sep 2020 18:38:57 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.215.174; helo=mail-pg1-f174.google.com; envelope-from=jhyde.apache@gmail.com; receiver= Received: from mail-pg1-f174.google.com (mail-pg1-f174.google.com [209.85.215.174]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id 6C73BBC306 for ; Tue, 29 Sep 2020 18:38:57 +0000 (UTC) Received: by mail-pg1-f174.google.com with SMTP id 34so4543138pgo.13 for ; Tue, 29 Sep 2020 11:38:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=/wbF2RgT0y2bHhEERxSbT+8oTPdMaobes+CObbsozvQ=; b=nALVQIBtWUdKOulQXcH4epSyBcAS+IcyNbBzJf51fkMx22khlYP7msmvYnJ2AyZsDg SA4WxuxEgJbpyBm77+kHDDnm/1dUG7hzq7fRPzxcXERSmNixOcGqNMzdMTtU5mNhbGF6 bofgkXeAcZd6cXU0U6DborneQ+Lo/1yz10HFAiPRBzOhpAs5V2tJqEaovCh2FuunhNJA PWe7fw+udpeGLHW8X8QAJxBm88QYsQ0DSEbMoykQ3xftGPAF7QhEsyKpCRk19lkQXzy0 F7rB/I9BCJ7ooxoXr3SsIEQHvSQTlIxvB487H7IVieodzi7iD4sBgQGQHH2Abvpei5lF TUYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=/wbF2RgT0y2bHhEERxSbT+8oTPdMaobes+CObbsozvQ=; b=nsOikq0I3BZLRHtnFGsPpwdVIzReooy1rjtBWwPPcsxX2Ki6x8Q5cM9ljm2XcFgufB 9hyTHemxC3skMvLtxCtUXpJsy2wI78jRKvZCBwy33nf3634n7O9loQ3lxZ9v9sDhyIaJ 8/0b76Agr1Ckz7oTKvROmxaxFvWVtsfI1KlrnYE3e/c50hkmeK+jz+Eac51ogEI8/nuL K5TAbx0248Jl+u0VidpX6xly/Zh9ZdqkcLSWQKN0jBY+ht4umd9GC37aBt5KtPCP5an4 x/w5onKxOhIvdDeSTyRlf7TPhZj4Cp2RUzOCvvZqN0RkAJ1cCuWQjPg1oMeoQc7229Ze M+XA== X-Gm-Message-State: AOAM5310jJZzDVWVAvQyYTvFolcp8ldEsN0oRfmBwZ7d6iaT5Be03T9/ RaF/qGRqhHnMvLjhx3aT778jNEFneug= X-Google-Smtp-Source: ABdhPJzBIm+olUsdhi1kiFVcUVl/AP9CRyMUnQcpky2tEiP0vYwlwJDE5DaRPNYHMfdBaKipPM4Lzg== X-Received: by 2002:a17:902:a40b:b029:d2:1e66:9c with SMTP id p11-20020a170902a40bb02900d21e66009cmr6022770plq.52.1601404736206; Tue, 29 Sep 2020 11:38:56 -0700 (PDT) Received: from [192.168.1.107] (107-182-36-90.volcanocom.com. [107.182.36.90]) by smtp.gmail.com with ESMTPSA id i17sm6237864pfa.29.2020.09.29.11.38.55 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Sep 2020 11:38:55 -0700 (PDT) From: Julian Hyde Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: [DISCUSS] Rotating the PMC Chair Date: Tue, 29 Sep 2020 11:38:54 -0700 References: To: dev@arrow.apache.org In-Reply-To: Message-Id: <044C487F-3E3C-4E99-B4F7-55BF8DEA8B32@gmail.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) Feb 17 as a term end date sounds good. We don=E2=80=99t necessarily have to wait until Feb 17. If we want to = move on this sooner, the next Chair could serve a slightly longer term, = ending on Feb 17 2022. > On Sep 29, 2020, at 11:25 AM, Wes McKinney = wrote: >=20 > This sounds reasonable to me. We are approaching our 5 year > anniversary as an Apache project (on February 17, 2021) and I have > thought that it would make sense to rotate PMC chairs at some point, > but making it an annual thing makes things even simpler. >=20 > For what it's worth, in this project the PMC chair (Jacques) has > mainly only had to exercise the unique responsibilities of the role in > the submission of board reports and in giving PMC karma to new PMC > members. There have been a handful of instances where the PMC has > engaged with the board beyond our routine reports over certain > matters, but overall IMHO we've had a generally healthy dynamic in our > governance. >=20 > On Tue, Sep 29, 2020 at 2:12 AM Julian Hyde wrote: >>=20 >> There has been some discussion in the Arrow PMC about rotating the = PMC >> Chair (also known as the project VP) every year. I wanted to raise = the >> topic here for discussion among Arrow committers and within the >> broader Arrow community. >>=20 >> Quite a few Apache projects have adopted a policy where they choose a >> new Chair on a regular basis. This has several advantages. First, it >> helps avoid the perception that the project has a BDFL [1]. Second, = it >> broadens the skills of the people in the project, exposing them to = the >> workings of the Apache Board. Third, it can drive cultural change in >> the project, because different leaders have different styles. >>=20 >> To be clear, a PMC Chair has very little actual power. Their main = role >> is to keep the Board informed, by submitting quarterly reports. >> Decisions are made by the PMC, and the Chair's vote has no more power >> than any other vote. But the perception is that the Chair speaks with >> authority and sets the agenda, and perception tends to become = reality. >>=20 >> In Calcite, for example, we have adopted a policy (without writing it >> down as bylaws) where we choose a new Chair around the project's >> anniversary, in October every year. Around the same time, the Chair >> starts a =E2=80=9CState of the Project" discussion thread where we = discuss the >> challenges and opportunities for the project. It has worked extremely >> well. We now have 5 current and former chairs, all of whom are active >> in the project, and all of whom can speak authoritatively for the >> project as "Former PMC chair, Apache Calcite=E2=80=9D. >>=20 >> I think such a scheme would be of benefit to Arrow. What do you all = think? >>=20 >> Julian >>=20 >> [1] https://en.wikipedia.org/wiki/Benevolent_dictator_for_life