X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-qt0-f173.google.com (mail-qt0-f173.google.com [209.85.216.173]) by lists.alpinelinux.org (Postfix) with ESMTP id CA4CD5C4CF9 for ; Fri, 19 Jan 2018 20:18:49 +0000 (GMT) Received: by mail-qt0-f173.google.com with SMTP id u10so6850793qtg.2 for ; Fri, 19 Jan 2018 12:18:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dereferenced-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=19TuxUYNMVLZKU9/F/ax1mhdC38KkZemtA0nku60D1I=; b=YzcecUNP1QsES23Ge748Ca/quMecfqGA3rLRX4TX6SHP+yKfC7IESDOcjIlByPD+dd kWhB+bs1j9PthKA3war/Jll9d4dogNGumxaNxj2wIOvKfzrNbcSF6CmrOalEnZ8Wc/cs DmmUpNYod2Fcx6BgTVcEu7nZkhxblgdkRqmuI8Gowr4O/pnjUmSUkS4K5ERYJ/kvdnwk ExypWHcz1mYMahQ1YBahiqGN2IEZ3fDyTn0HZhOXCZd/TtM1F3OU+a5NI2QHjfbjioCs No4O9UdOzz9Ca3d9PKym/dquvLKYwWISYtEUhAJ/1GCKrUP40lQgcQBO0vUkhP3eQ0R0 QOSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=19TuxUYNMVLZKU9/F/ax1mhdC38KkZemtA0nku60D1I=; b=SP1kdUZhWrWUrwug+RAS6a9tidICmCoC++b/8KbUE/ceusjt1Dky7Z/yqrpR1v7OEv vaQCjDLFVIDKG4p7CYuAjU55QEIp5h0KwpQ9F3JEHmGcgBlJp2daj4ADh+8cuNdnw4Tg 0vt2yQkMDexkW449PmDXGvVVi74O+L1Yv7F3xUiiZCAIbIIi3iam0XLdjFeJLE9gyFF/ Zeu3pbwvF/ODr2HwjSkSAD4VpTD4cwqmaWlV0Y7LjULXEmhjhy5rsSchMorJrfpuhnM6 HvJj8UElCsnuhFzXDpV/CtZjaipOHYMWbpBDFuxOOrN0C1KyLUULqod6X1tke3zVIeQM J61Q== X-Gm-Message-State: AKwxytcda1SpfCh+4748olCEdN4Jn0gbsec5jQOE5cm9/KRi9Xz89o+I QnpF7/14DtZdKA9RvetWr7F8uiMUA+8enAR/EojbZCLq X-Google-Smtp-Source: ACJfBosUvChj0p11Czdl2AK+v/aXlUT9G63OG/q6h8ZrfkfULZ8W3Q2+tdHR4QE0JaeGdq6RgFjCFDDcGbidKtryYEw= X-Received: by 10.55.71.195 with SMTP id u186mr37542188qka.255.1516393128812; Fri, 19 Jan 2018 12:18:48 -0800 (PST) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.200.39.100 with HTTP; Fri, 19 Jan 2018 12:18:48 -0800 (PST) From: William Pitcock Date: Fri, 19 Jan 2018 14:18:48 -0600 Message-ID: Subject: [alpine-devel] Announcement: Non-technical member status To: alpine-dev Content-Type: text/plain; charset="UTF-8" Hello, As is already known, the core team holds final responsibility for all decisions made on behalf of the project. This includes defining what a Developer actually is. The core team has not at this time delegated that responsibility. Therefore, this email serves to document a modification to what is meant by Developer status, as well as creating a track for non-technical contributors to earn Developer status (as a non-technical member). Member status =========== A Member is any participant in the project who has been granted full rights to the project. These rights include: * the ability to nominate others for membership rights in the project * the ability to nominate others for expulsion from the project (as a last resort) * the ability to bring proposals up for a vote by the whole project * the ability to vote on proposals * an alpinelinux.org email account A contributor may become a Member by either a technical track in which case they become a Developer or Sysadmin, or a non-technical track in which case they are just a Member. A Maintainer is not a Member of the project unless they gain Developer status or are separately nominated under the non-technical Member procedure. Developer status ============= Developer status remains largely unchanged, except that the rights exclusive to Developers and Sysadmins now belong to any Member. In other words, a Developer is now a Member who has full push rights and nothing else. Sysadmin status ============= Sysadmin status remains largely unchanged, except that they are now just a Member who has special access to Alpine systems. Non-technical contributor track ======================= A non-technical contributor may be nominated for Member status by any other Member. As part of their nomination, they should highlight notable contributions made by the nominee. A nomination will have a period of a week, starting from the moment a core team member acknowledges the nomination. At this point, admission is decided using lazy consensus: if 2 or more core team members approve of the nomination and there are no objections, the nomination will be accepted. Otherwise the core team will discuss and come to a conclusion after the deadline is hit. If the nomination is accepted, then the infrastructure team will be directed to create the account, collecting an SSH key and any other pertinent data they need to process the account creation request. A non-technical Member may apply for Maintainer or Developer privileges later, but they will have to complete the full technical track before getting Developer privileges. William --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---