public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Why no updates on delay of 2008.0 release
Date: Sun, 23 Mar 2008 08:17:45 -0400	[thread overview]
Message-ID: <47E64A69.7090203@gentoo.org> (raw)
In-Reply-To: <000701c88c89$db499560$91dcc020$@org>

Chrissy Fullam wrote:
 > Somebody else wrote:
>> ... I don't think there is any excuse not to update the published
>> release schedule,...

<snip>

> the update is simple: the untimely and quite unexpected surgical 
> "complication" resulting in the death of my mother has set back a 
> number of schedules,

Lesson:  Ask nicely before going into attack mode.  Don't assume the 
worst.  Consequently, avoid putting foot in mouth...

Try to remember that this is a volunteer-driven effort.  If you want it 
to stay vibrant we need to try to be nice to each other.  There have 
been many occasions where I've needed something from a gentoo dev - if 
you ask nicely there is a good chance you'll get it, and if you 
volunteer to help out in some way there is an even better chance.

I was just browsing the net today looking for some options for a 
bootable linux CD that would turn a workstation into a dvdrip cluster 
node.  Sadly I ran into several projects that would be almost exactly 
what I need, and most are dead for various reasons.  Open source is 
something that needs to be nurtured, and if we don't want to write code 
the least we can do is offer a little help of some sort to somebody who 
does.

No, that doesn't justify some of the more antisocial behavior some 
developers dump on users, but I think that Gentoo has managed to put 
some of that in the past (I've been impressed about how cordially some 
devs have been getting along in recent months).

Sure, maybe some things could be improved. But, new blood is always 
welcome, and there are signs of new life springing up (recent talk about 
PMS progressing, innovations in the kde overlay, talk of openrc going 
mainstream, activity on the -nfp front, etc).  Not that it ever really 
died in the first place, but I think that the future looks good for Gentoo.

Let's just try not to stamp out the enthusiasm before it spreads a 
little more...  :)
-- 
gentoo-dev@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-03-23 12:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 10:20 [gentoo-dev] Testing to see if services have crashed on hardened Roy Marples
2008-03-21 10:37 ` Fabian Groffen
2008-03-21 12:07   ` Roy Marples
2008-03-22 10:27     ` [gentoo-dev] Why no updates on delay of 2008.0 release Ben de Groot
2008-03-22 15:39       ` Sylvain Alain
2008-03-22 21:34         ` [gentoo-dev] " Duncan
2008-03-22 18:54       ` Christian Faulhammer
2008-03-23  2:01       ` [gentoo-dev] " Chrissy Fullam
2008-03-23  5:54         ` [gentoo-dev] " Duncan
2008-03-23 12:17         ` Richard Freeman [this message]
2008-03-23 12:26           ` [gentoo-dev] " Ciaran McCreesh
2008-03-23 13:00           ` Ben de Groot
2008-03-25 19:45     ` [gentoo-dev] Testing to see if services have crashed on hardened Fabian Groffen
2008-03-21 10:44 ` Natanael Copa
2008-03-21 12:08   ` Roy Marples
2008-03-21 12:39     ` Natanael Copa
2008-03-21 13:08       ` Roy Marples

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=47E64A69.7090203@gentoo.org \
    --to=rich0@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