From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Becoming a Gentoo developer?
Date: Fri, 17 Apr 2015 21:38:51 +0200 [thread overview]
Message-ID: <1429299531.875.8.camel@gentoo.org> (raw)
In-Reply-To: <552FF0F1.5080709@gentoo.org>
El jue, 16-04-2015 a las 19:27 +0200, hasufell escribió:
[...]
> To reply to the topic: If the only reason you want to become a gentoo
> developer is "contributing ebuilds", then you should reconsider that,
> because there are easier ways to do that.
> But if you are interested in politics, PMS, EAPI and other
> organizational stuff on top of contributing ebuilds, it might make sense.
>
I, as another Gentoo developer, encourage people willing to contribute
ebuilds to try to jump the gap if possible to allow to directly "do the
job" instead of depending on others (with commit access) to import the
ebuilds they put at some random overlays.
I am not mostly interested in "politics, PMS, EAPI and other
organizational stuff" and I still think it makes sense to become a
gentoo developer
next prev parent reply other threads:[~2015-04-17 19:39 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 12:17 [gentoo-dev] Becoming a Gentoo developer? Yanestra
2015-04-12 13:08 ` Pacho Ramos
2015-04-12 14:27 ` Yanestra
2015-04-12 14:44 ` Andrew Savchenko
2015-04-12 15:05 ` Andreas K. Huettel
2015-04-15 3:33 ` Yanestra
2015-04-15 6:40 ` Diamond
2015-04-15 13:02 ` Peter Stuge
2015-04-16 17:27 ` hasufell
2015-04-16 22:59 ` Kent Fredric
2015-04-17 19:38 ` Pacho Ramos [this message]
2015-04-17 21:09 ` Andreas K. Huettel
2015-04-18 9:45 ` hasufell
2015-04-17 10:33 ` Alexander Berntsen
2015-04-17 11:00 ` Andrew Savchenko
2015-04-17 11:12 ` Kristian Fiskerstrand
2015-04-17 11:14 ` hasufell
2015-04-17 12:26 ` Andrew Savchenko
2015-04-17 12:50 ` hasufell
2015-04-17 14:33 ` Andrew Savchenko
2015-04-17 14:41 ` Alexander Berntsen
2015-04-17 17:15 ` Rich Freeman
2015-04-18 9:15 ` hasufell
2015-04-18 9:26 ` Patrick Lauer
2015-04-18 12:35 ` Rich Freeman
2015-04-18 13:03 ` hasufell
2015-04-18 14:35 ` Rich Freeman
2015-04-17 21:12 ` Andreas K. Huettel
2015-04-17 23:16 ` Kent Fredric
2015-04-18 9:10 ` hasufell
2015-04-21 10:33 ` Sergey Popov
2015-04-17 19:14 ` [gentoo-dev] " Justin Bronder
2015-04-17 23:30 ` Kent Fredric
2015-04-18 4:07 ` Rich Freeman
2015-04-15 20:46 ` [gentoo-dev] " Pacho Ramos
2015-04-16 14:22 ` Bob Wya
2015-04-16 22:50 ` Kent Fredric
2015-04-17 11:13 ` Andrew Savchenko
2015-04-13 10:27 ` Daniel Campbell
2015-04-13 12:20 ` Patrice Clement
2015-04-13 12:37 ` Patrice Clement
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1429299531.875.8.camel@gentoo.org \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox