Received: from mx1.mailbun.net (mx1.mailbun.net [170.39.20.100]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id C423B7810DB for <~alpine/devel@lists.alpinelinux.org>; Thu, 20 Jan 2022 21:22:11 +0000 (UTC) Received: from [2607:fb90:d983:1d8:e070:381b:a0bf:3b01] (unknown [172.58.104.36]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: ariadne@dereferenced.org) by mx1.mailbun.net (Postfix) with ESMTPSA id 6A54111AF82; Thu, 20 Jan 2022 21:22:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dereferenced.org; s=mailbun; t=1642713730; bh=nbA+p6myC3a+JV20CHXvE81nZfqWOyb2gPB2smT1tZ8=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=R7TJZGbY3ThC3IJ6Weyk+juoC+zKVPfa40ojcoLhW60BhwukYK0Fmu2EWjtHeQM33 Uj+3PWdRIemNDCNjLE61/3Gb0BOOQkRxKwgckE6tBFb7Qp1zlViQvGMBpLS4xegB+p 753S1rtexdxmScMKlSQVCyUAJ6aPJlUz02/GbAc1F3P3MQvsQWRmFHboNYSxXV2x4N lTwCx9Lj+o760Ji5frwBojY374aiI3FoILaoHjpT0hiX1p6cZ34qH3t34lk74AN659 9p3OOgbrIIhikTul/zZY+0IH3DXPa8I9YL+5xyFYMpaKLpETzF65DVVL7XLeqONxQ+ tOeCd8nU/U4jw== Date: Thu, 20 Jan 2022 15:22:05 -0600 (CST) From: Ariadne Conill To: Drew DeVault cc: Ariadne Conill , Nulo , ~alpine/devel@lists.alpinelinux.org Subject: Re: Experiencing harmful behavior in Alpine In-Reply-To: Message-ID: References: <20220120180617.rvboyscx2oz5r3wu@x69> <1ea6351e-e958-78d6-9b92-fcde35a52d@dereferenced.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Hi, On Thu, 20 Jan 2022, Drew DeVault wrote: > On Thu Jan 20, 2022 at 10:07 PM CET, Ariadne Conill wrote: >> Unfortunately, the TSC does not have the authority to enforce the Code of >> Conduct, this is retained by the Alpine Council, for good reason. When >> developing the new governance structure, it was our intent that there be >> an ability to validate that TSC members are also following the Code of >> Conduct, which requires a separate team without conflicts of interest. > > I was not aware that the council existed until now, and indeed it seems > like a more appropriate venue. The new governance structure was launched at AlpineConf 2021, but admittedly there has not been much of an announcement since then. I think this is because the Council has been busy dealing with more urgent governance issues and wanted to wait on an announcement until everything was polished. > I'm also going to ask that the following tickets are prioritized: > https://gitlab.alpinelinux.org/alpine/council/-/issues/3 > https://gitlab.alpinelinux.org/alpine/council/-/issues/8 > https://gitlab.alpinelinux.org/alpine/council/-/issues/9 > > There is not really sufficient communication around what's going on with > Alpine governance as of late. > >> But, admittedly, I am not happy with this either, both because Nulo's >> concern has not been addressed by our current workflows, and because there >> is no actual way to request a CoC inquiry. Both of these things should be >> addressed. > > Can you open another ticket for the Council to amend the CoC to define > the redress procedures? This seems reasonable. I have opened a work item to update the CoC, including redress procedures: https://gitlab.alpinelinux.org/alpine/council/-/issues/12 Ariadne