From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1M1PpH-0005Nn-Lo for garchives@archives.gentoo.org; Tue, 05 May 2009 18:57:11 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D5EACE04CB; Tue, 5 May 2009 18:57:09 +0000 (UTC) Received: from yw-out-1718.google.com (yw-out-1718.google.com [74.125.46.154]) by pigeon.gentoo.org (Postfix) with ESMTP id AEE9AE04CB for ; Tue, 5 May 2009 18:57:09 +0000 (UTC) Received: by yw-out-1718.google.com with SMTP id 5so6823925ywm.46 for ; Tue, 05 May 2009 11:57:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=a6SkgQeJ0zfGtawXPZeONX7s0py1SkTrcK094djnwUM=; b=aQIp2U38Ix9hf8KVILTRplT584VWKYgG7SUMUMkRvD/3wIVlP+taYHp5ORISimJBGd B4F4M38euVq9fbtvFsjzNchwsAc7k/RbkJGOJBR0C9/fFqQCU/56jt1sSTvO5Y1gA5ZX YYIuTknJxdILel0beGpKlXq1BWySKpIY+M85A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:reply-to:to:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=wICiAAxBvwyfTIYr8NHbZRRgd9MAJBlXOt5M7DJc6UElPKlI/mrUpexDWjikrCzr1e CDJmV5t5C+6No9M2I9TMmNzVKz7/djRhFj4dj5HTfANIlaS2EcAFgfInCPpYYFg3fSIo ZIA9yEkRd0tiy85Cvq/3rJOk+oO+W5SgdwYjI= Received: by 10.100.57.19 with SMTP id f19mr758113ana.72.1241549829447; Tue, 05 May 2009 11:57:09 -0700 (PDT) Received: from ?190.203.101.54? ([190.203.101.54]) by mx.google.com with ESMTPS id 10sm307942agb.76.2009.05.05.11.57.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 05 May 2009 11:57:08 -0700 (PDT) Subject: Re: [gentoo-dev] Re: Training points for users interested in helping out with ebuild development From: =?ISO-8859-1?Q?Sebasti=E1n_Ram=EDrez_?= =?ISO-8859-1?Q?Magr=ED?= To: gentoo-dev@lists.gentoo.org In-Reply-To: <4A007728.2050504@gmail.com> References: <200905042006.52646.mario.fetka@gmail.com> <49FF40FC.2090105@gentoo.org> <49FF544C.9060500@gmail.com> <4A0073B3.3000101@gentoo.org> <4A007728.2050504@gmail.com> Content-Type: text/plain; charset="UTF-8" Date: Tue, 05 May 2009 13:29:29 -0430 Message-Id: <1241546369.11404.18.camel@supertux.cantv.net> 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 X-Mailer: Evolution 2.24.5 (2.24.5-1.fc10) Content-Transfer-Encoding: quoted-printable X-Archives-Salt: dbf1decf-b8fa-4ca8-a065-f0c037845fb5 X-Archives-Hash: 524e845a980b2a3ee253b62399b5ccfc El mar, 05-05-2009 a las 18:28 +0100, George Prowse escribi=C3=B3: > Thomas Sachau wrote: > > George Prowse schrieb: > >> Thomas Sachau wrote: > >>> For those, who can work with IRC and are interested in working with > >>> ebuilds, there is already an option: > >>> > >>> Join #gentoo-dev-help or even better #gentoo-sunrise and read the > >>> documentation from the topic. The > >>> Sunrise Overlay (with the #gentoo-sunrise IRC channel) is open for > >>> everyone willing to learn and > >>> contribute to it. Even normal users can get access, learn how to > >>> create ebuilds, how to improve them > >>> and how to maintain them. > >>> As a starting point, this is a central overlay, where ebuilds are > >>> maintained, that dont get a > >>> developer as maintainer because of missing manpower. Additionally, = all > >>> contributors learn the ebuild > >>> development work themselves. > >>> > >>> And if you are willing to learn and do continuously good work, ther= e > >>> is a good chance that you may > >>> level up to a developer yourself someday. You want an example? This > >>> was my way to become a full > >>> Gentoo developer. ;-) > >>> > >>> So at least for ebuild maintainence, there are good starting points > >>> (probably other projects also > >>> have training grounds like the java or kde herds), the bigger probl= em > >>> may be the communication > >>> between potential new developers and the current developer base and > >>> our options to become a new > >>> developer. > >>> > >> I think you are missing the point. If you sit and wait for them to j= oin > >> you will always be understaffed. > >> > >> Go on a big dev drive! Announce it all over all the Gentoo's normal > >> communication channels and other generic linux places! Email some li= nux > >> magazines, talk to distrowatch, message some large LUGs. Get people > >> talking about it. Whatever happens, dont just sit on your hands. Tel= l > >> the users that Gentoo needs them and that they can make a difference= ! > >> > >> If you make it a big and special occasion which is planned correctly > >> with a sufficient number of current developers who are willing to wa= lk > >> people through how and what it means to be a Gentoo Developer then t= he > >> influx could create a new backbone of new developers who will hopefu= lly > >> be here for years to come. > >> > >> > >=20 > > Such a campaign would need quite some time and i dont have this free = time. So if anyone is willing > > to do the needed work, i can try to help a bit, but cannot take the w= ork and time myself. > >=20 > > The only thing i can do and currently do whenever possible is pointin= g people to the sunrise project > > and helping them there. And thats what i did with my mail. > >=20 > I also fear that any sustained campaign would be bogged down in Gentoo'= s=20 > red tape. >=20 I feel it's necessary to clear that it's not mandatory to be a full time developer to help improve Gentoo. Many users want to help but they don't feel ready for such a compromise. Then there is Sunrise, and the overlays from the herds, where the prospective users can learn first and take the following step when they feel they're ready. I think there are at least 2 recent new developers who made it this way. There are several (much?) understaffed projects in Gentoo, the developers who are responsible of this areas could take some time to write a guide for users on how to help, with steps to commit patches to the overlays, wishes and needs... and then publish it in the project web page. Also, there could be a page similar to the 'staffing-needs' one, but listing links to the 'Help Us' pages of the projects. Just my 2c... And sorry for any spell/grammar error...