public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michaela Susan Buesing <ela@elamaus.mausehaus.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Introduction to Gentoo Development Teams and Processes
Date: Wed, 3 Jul 2002 20:13:36 +0200	[thread overview]
Message-ID: <20020703181336.GA19787@elamaus.mausehaus.org> (raw)
In-Reply-To: <20020702210119.GA26675@barbrady.circlesoft.dyn.dhs.org>

Be greeted, "Sir" Perc!

Sorry, if I don't get into too much detail, concerning your ideas, but
don't you think, that your suggestions are completely missing the point
about having an OPEN (and volountary) development process?

How are people/users supposed to learn and eventually become fully-fledged
developers if they aren't to interact/learn from those who are already
there?

I for myself would have never taken the step to apply for some official
developer status. The open system of openly available developer
documentation, mailing lists and BugZilla helped me a whole lot with
overcoming my doubts...

I also think that input from "normal" users is the best way to learn, what
should be improved. - And after all, what is OpenSource/open development
all about in the end?

Bye, Ela.

P.S.: Sorry, if this was a bit sharp. It's only my opinion, after all. :-/


  reply	other threads:[~2002-07-03 18:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-02 21:01 [gentoo-dev] Introduction to Gentoo Development Teams and Processes sirperc
2002-07-03 18:13 ` Michaela Susan Buesing [this message]
2002-07-07 23:45   ` Sir Percival
2002-07-08 17:41     ` Wout Mertens
2002-07-08 18:12       ` Andy Arbon
2002-07-04  1:49 ` Karl Trygve Kalleberg

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=20020703181336.GA19787@elamaus.mausehaus.org \
    --to=ela@elamaus.mausehaus.org \
    --cc=gentoo-dev@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