Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch [185.70.40.132]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 013597819EA for <~alpine/devel@lists.alpinelinux.org>; Sun, 27 Oct 2019 13:42:28 +0000 (UTC) Date: Sun, 27 Oct 2019 13:42:20 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cogitri.dev; s=protonmail; t=1572183747; bh=55wNRnjMspCBwDitnt1Dw9kelvdOf5w3ldHhfTQtwYs=; h=Date:To:From:Reply-To:Subject:In-Reply-To:References:Feedback-ID: From; b=rWP0/3pzorWG8kXY1ffpsoOkSaZurMNV1tAzaBBVxhMyJiZRb3Qea/MK5zRu9YtYR O/APOtFPbzIPvalaADhIeWoGiE8UpKXebddWm8QG/s0CjFky0c5dHeR7NqQYo0VJF3 oTmLL0XxPD5jZA4CeJLDbljcinrJa5f6Da2qPXss= To: ~alpine/devel@lists.alpinelinux.org From: Rasmus Thomsen Reply-To: Rasmus Thomsen Subject: Re: Alpine community governance Message-ID: <5152c7bd5e788aadfb987281a47107a4f3959860.camel@cogitri.dev> In-Reply-To: References: Feedback-ID: LZW2MXNaH7NSG88i8lGpebeqB0wmcl0-3TbzkSuzsmAwEQspn4GI-WRe8j3PhRL4SBmua4rQWq6fadPcLS5uxQ==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_6e9557ce0c6251d1ec6462ace09eaa6c" X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.protonmail.ch This is a multi-part message in MIME format. --b1_6e9557ce0c6251d1ec6462ace09eaa6c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Moving a discussion from IRC to the ML: >=20 > One easy way to improve the core team's bandwidth would be a simple > git > hook which allowed anyone to push changes to packages for which > they're > listed as the maintainer. Hm, although that does sound like it'd significantly lessen the workload on core member I dislike this approach, at least with how we currently handle maintainership of packages. About everyone can become a maintainer (which is a good thing IMHO since this allows people knowing the package well but not Alpine's packaging process to be a maintainer) as of now and I feel like it'd be best to have someone look over the changes of maintainers which aren't that experienced with Alpine's packaging process yet. Maybe just having somewhat strict CI rules and only allowing a merge if CI passes would do the trick to ensure QA is done though. > This reduces the core team's workload to > dealing with new packages, new maintainers, etc; but removes the > burden > of dealing with every change to aports. --b1_6e9557ce0c6251d1ec6462ace09eaa6c Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=signature.asc LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ2dBZEZpRUV1WEFWYTVoYXNT Y08yaFp3WmJ6UURYYkkrSWdGQWwyMW5yb0FDZ2tRWmJ6UURYYkkKK0lqOS9nLytMMUozQWp0Rlk1 dW8vSXY2b2JaS04rTEpFNDF0U1BYUnZVUjdKTWJ4dU5CZFBLdUZTZ0lyNkxCQQpFelQ2M0xlekM3 MFNlOURjb0xEblNGaTJtMGtDR0x1ejV4c1UzaWx1NFc5RzVGNGEwMGRjZ05pRHhzMHZaUzg1CnhK K0NZOXlELzJUSG15VEJQd2VWeHNFSEpqZmxTcXozWTRPcUlUY2Fyd09XVkc2ckl4cVN1djBqem1l SmpkWGgKTHdyQ3J3UzZuVmhSNDk0R0k5dzNKd29YNytmSTE4MmtkblRJU3lWUmFtcEY5Ri9HV1hx TFk0UlA4TzhYeFpRWQpDRFFEZk0xTFgvWDRDVm5HQzhiNk4vbHFxRnRFUnVGbkV0RmxKQjRRR0tV WGc5dGZmeEo3Wk5NcTlwMmZhQ1YvCmsxRHpXOHNsYzk5am1qWFpsTnZ0T2NYNGk3dHZPRjdJQStq bWZPM3lDRUdjcFBsOGZPSWpZMVpqblBON0hibTYKYUZMeGZyY0RQU1NkK1crQmhxU2prSUplUlAy dXE0ZWlUTk0wVUNPYlBJTFgxRUppc2krWFpSeVl5WlFFT3lubgpKZDhGaER5aktNNTQ1c0tIUGhI RVlzMHdDTmt4ZFFxQURaSGR0RFJ6Q1ArVFBzMjY4S2NIbFVCa01DV05LaXlyClZsYXhrY1MzUC9R SU1adnBsNE54eDVwY0UvMU8vbEpCcStNNUdpSHl3UWRXekFiamhnQlNXa3NudmlQQXNXQVoKMU13 alhmdmM2RGJMamsxWEMyVzN6SlJIcmJWb3JTYUU2dklyVE1CdzJ0WVhXb1hyRm9VSUMwMEhNdDVG NFdIcgord28yblVnd0IrN1pCaUlzaVB4N25OVHVnUXpWVlJuNVJ1cERFYTkrT0NXbHI1cjZzcG89 Cj1KR0t1Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --b1_6e9557ce0c6251d1ec6462ace09eaa6c--