public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: gerrynjr <gerrynjr@emailgroups.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] the vision for Gentoo
Date: 28 Jun 2003 09:17:11 -0500	[thread overview]
Message-ID: <1056809831.1271.1.camel@screamer.nfn.net> (raw)
In-Reply-To: <20030628091853.GD11566@inventor.gentoo.org>

> 1) What engages and inspires us?
Well, I am similar to you in this respect, drobbins. I prefer to teach myself, 
to explore by myself, to break things, and then fix them.
Gentoo provides that environment to the greatest degree, and is thus why
I use it. I like working and engaging myself with people of many
different backgrounds and cultures, and Gentoo allows me to do this. 
However, I also feel that more user Input should be taken into
consideration when making critical decisions. (This email topic is a
great step toward this.) 

As I previously stated, I like breaking things. I used to be part of a
what Mandrake called "The Crash-testers."  It was a private list that
included people from around the world. Basically, we would test new
packages, new Ideas, as well as stress test existing ones. We became a
type of Quality Assurance Team, at least until our supervisor was let
off. 

I for one an interested in most alternative technical things. I'm
interested in security, PC architecture, alternative operating systems,
and new ideas. 

> 2) How do we formulate this "excitement/spirit" into a collective vision for
> Gentoo?

I feel it would be difficult to formulate a "collective" opinion until
we receive many more opinions on the matter, otherwise it isn't really a
collective spirit. I see Gentoo as quite possibly the future of Linux
meta-distributions, and the coming ability to choose a kernel, even if
it isn't Linux.. is a great thing. 

As for a straight out vision, it would be difficult to formulate one, as
gentoo's current one meets my expectation somewhat. 

> 3) How do we best implement this vision?

I can see how becoming a non-profit org may comfort many people, it
guarantees that their work (volunteer work, etc.) is preserved and 
not taken advantage of. It may provide some protections.  For the most
part, I could care less if it's a non-profit, but if becoming one makes
more people feel comfortable with helping out... that changes things. 

--Gerry Normandin


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-28 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-28  9:18 [gentoo-dev] the vision for Gentoo Daniel Robbins
2003-06-28 14:17 ` gerrynjr [this message]
2003-06-28 15:35   ` [gentoo-dev] private mailing lists? (was [Re: [gentoo-dev] the vision for Gentoo]) Todd Berman
2003-06-28 17:24 ` [gentoo-dev] the vision for Gentoo Michael Kohl
2003-06-28 21:31   ` [gentoo-dev] The problem of stable/current. Was: " James Yonan
2003-06-28 21:49     ` Martin Schlemmer
2003-06-28 22:59       ` James Yonan
2003-06-29 10:03         ` Martin Schlemmer
2003-06-29 11:13         ` Michael Cummings
2003-06-29  0:52   ` Jens Hoffrichter
2003-06-28 22:01 ` Svyatogor

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=1056809831.1271.1.camel@screamer.nfn.net \
    --to=gerrynjr@emailgroups.net \
    --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