From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D29E5139694 for ; Thu, 27 Jul 2017 08:41:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 012F91FC114; Thu, 27 Jul 2017 08:40:53 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B3D2D1FC002 for ; Thu, 27 Jul 2017 08:40:52 +0000 (UTC) Received: from [192.168.0.10] (81.61.201.10.dyn.user.ono.com [81.61.201.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id 3DC6A3417DF for ; Thu, 27 Jul 2017 08:40:51 +0000 (UTC) Message-ID: <1501144847.4544.111.camel@gentoo.org> Subject: Re: [gentoo-dev] sys-boot/plymouth needs major fixes/maintainer From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Date: Thu, 27 Jul 2017 10:40:47 +0200 In-Reply-To: References: <1501062999.4544.105.camel@gentoo.org> <1501063423.3913.1.camel@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: a15a732f-9833-469e-8262-d4ab0f739bd7 X-Archives-Hash: 4eeed5cd50e5bc73a232f9e0bdfdadb2 El mié, 26-07-2017 a las 13:46 +0000, Lucas Ramage escribió: > I am not yet an official developer but I am interested in assisting in > maintaining this. > Then, please take a look on: https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers In summary, you will need to open a bug asking proxy-maint to set you as maintainer and, for fixing bugs, usually sending github PR is the preferred method Thanks