public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Caleb Cushing" <xenoterracide@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Wiki document
Date: Tue, 8 Aug 2006 12:01:19 -0400	[thread overview]
Message-ID: <81bfc67a0608080901q4f2e2ee2vd05294a0bdd01e38@mail.gmail.com> (raw)
In-Reply-To: <1155050965.11843.24.camel@inertia.twi-31o2.org>

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

you mean besides starting the portage 2.1 thread trying to sort out the new
features? and considering updating the wiki for catalyst? volunteering for
user representative at gentoo, and giving presentations frequently at my
local lug? studying school doing my 40 hour a week internship, and I
somewhat aided with other docs in the past, filing bugs to add, update, or
remove sections. So I suppose I've done nothing to help gentoo or the linux
community? no need to get so offended... I applaud the fact that catalyst2
won't be made stable without proper documentation, and a how to is planned.
believe it or not I'm willing to help. but I can't help a project I don't
understand. but I don't like it when software is rolled out as STABLE
without proper documentation and months later it still doesn't have it. I
guess I will have to write it myself question is will it make it into the
tree? I'll see what I can do in the next few weeks to get the portage
utilities man pages in the next few weeks and make an update to the portage
manpage. I'm not coming down on you, and gentoo generally has the best
documentation around, however I notice many new tools (gentoo specific) are
lacking it.

On 8/8/06, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
>
> On Tue, 2006-08-08 at 10:55 -0400, Caleb Cushing wrote:
> > finally someone is writing documentation? for something this year?
> > <sarcasm>I thought docs were on hold for 06?</sarcasm> know if portage
> > docs will be updated too? sorry for the sarcasm... I just think some
> > things that should have been documented weren't. catalyst not
> > necessarily one of those things although a bit more would have been
> > nice...
>
> You know, was there really a point in this?
>
> I'm a volunteer.  I spend about 40 hours a week working on Gentoo stuff,
> besides my normal 40 hour a week job.  You're complaining because what I
> volunteer on wasn't done to your satisfaction?  Seriously, keep this
> kind of opinion to yourself.  I don't care to hear it, and it doesn't
> contribute anything to the conversation.
>
> What did *you* do to help get documentation done?
>
> --
> Chris Gianelloni
> Release Engineering - Strategic Lead
> x86 Architecture Team
> Games - Developer
> Gentoo Linux
>
>
>

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

  reply	other threads:[~2006-08-08 16:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08  9:49 [gentoo-catalyst] catalyst_lock Caleb Cushing
2006-08-08 12:16 ` Andrew Gaffney
2006-08-08 12:26   ` [gentoo-catalyst] Wiki document Luca Casagrande
2006-08-08 14:16     ` Caleb Cushing
2006-08-08 14:42     ` Chris Gianelloni
2006-08-08 14:55       ` Caleb Cushing
2006-08-08 15:29         ` Andrew Gaffney
2006-08-08 15:29         ` Chris Gianelloni
2006-08-08 16:01           ` Caleb Cushing [this message]
2006-08-08 16:18             ` Kessler, Paul
2006-08-08 16:52               ` Caleb Cushing
2006-08-08 16:32             ` Chris Gianelloni
2006-08-10 13:14       ` Luca Casagrande
2006-08-10 15:01         ` Andrew Gaffney
2006-08-10 15:11           ` Luca Casagrande
2006-08-10 15:18             ` Andrew Gaffney
2006-08-08 18:12     ` Andreas Rueckert

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=81bfc67a0608080901q4f2e2ee2vd05294a0bdd01e38@mail.gmail.com \
    --to=xenoterracide@gmail.com \
    --cc=gentoo-catalyst@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