X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail.cmpwn.com (mail.cmpwn.com [45.56.77.53]) by lists.alpinelinux.org (Postfix) with ESMTP id E222DF831FD for ; Mon, 15 Apr 2019 15:23:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cmpwn.com; s=cmpwn; t=1555341833; bh=eGay0TUVKkcLsYcgcy/oG8hGUHOzu/P3hHpyoL6T/nE=; h=Date:From:To:Cc:Subject; b=KPS187/gMdsyQ504wXxJx3uNQAXqeEtia0U06T6sov2EwJrJX5jn1qTsoWkzO9MzY PNzQvhqjjy8oN6xlmSJmePlYzEDmDyCEtGgJZAlo1tQvNtAUTKp8kIzJQVkCveusJ6 5mi5i7Q026DncKieoZiMjrW4woCnFM6Br3W828rU= Date: Mon, 15 Apr 2019 11:23:30 -0400 From: Drew DeVault To: alpine-devel@lists.alpinelinux.org Cc: Richard Mortier , Chloe Kudryavtsev Subject: [alpine-devel] Stripping down the governance model proposal Message-ID: <20190415152330.GG1179@homura.localdomain> X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GNU: Terry Pratchett There is a general sense of dissatisfaction with the governance proposal under discussion. It's too big and makes a lot of changes at once. Simplified governance model: 1. The core team is stripped down to 3 trusted people. 2. The core team is generalized to "responsible for everything". 3. The core team delegates their responsibilities at their discretion. Notes: - The new core team would immediately grant everyone already in core the necessary abilities to do the jobs they already do. - The core team can delegate delegation itself, for example to expand the leadership of aports. Based on this simplified model, informal teams will materialize as they're needed with minimal pomp & circumstance. The process for e.g. joining aports as a committer to community, becomes informally convincing the people who are responsible for giving people commit access to aports to add you. The person making that call might want to run it by the mailing list or the IRC channel for comments before pulling the trigger. The process for establishing a Python team is just getting a bunch of interested people together and doing the work. If it's necessary to connect an ad-hoc team like that with resources, just make the case to the person responsible for those resources. Official externally-facing roles can be established at the pleasure of the core team, as well. A security team, for example, can be established less informally and have membership written down somewhere, with a point-of-contact for the rest of the world. This may be simple enough for bootstrapping purposes and ought to solve the problems we set out to fix. As more complex procedures are shown to be necessary over time, they can be added. --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---