public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Yanestra <wysiwyg@seismic.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Becoming a Gentoo developer?
Date: Sun, 12 Apr 2015 14:17:33 +0200	[thread overview]
Message-ID: <552A625D.7030000@seismic.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]

Hi,

I am long time user of Gentoo and I tinker with the idea of becoming
Gentoo developer.

I am a software developer by profession, but I am not quite sure if I
should involve with Gentoo ebuild development.

To be honest, I have not the slightest imagination what becoming a
Gentoo developer might mean. Things seem to be abhorringly complicated.

As far as I understand, there are developers, proxy developers, then
there is something like Project Sunrise which I don't understand.

There are apparently several different portage source repositories,
basing on different software, and furthermore, there is layman. As far
as I remember, portage is stored in cvs, where there is also git, and
somewhere subversion seems to linger.

And there is lots of documentation that appears to be outdated or
strangely unattached to questions concerning organisation and overall
structure.

Can someone please tell me where to start becoming a developer? Do there
exist something like quality guidelines for ebuilds?

Why is there such a chaos?

Thanks!


[-- Attachment #2: Type: text/html, Size: 1679 bytes --]

             reply	other threads:[~2015-04-12 12:17 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12 12:17 Yanestra [this message]
2015-04-12 13:08 ` [gentoo-dev] Becoming a Gentoo developer? 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
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=552A625D.7030000@seismic.de \
    --to=wysiwyg@seismic.de \
    --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