From: Nathan Zachary <kalos@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] Handbooks / Autobuilds: What needs to be done?
Date: Thu, 30 Apr 2009 10:29:44 -0500 [thread overview]
Message-ID: <49F9C3E8.1080007@gentoo.org> (raw)
In-Reply-To: <49F9BB35.1050001@gentoo.org>
Ben de Groot wrote:
> Josh Saddler wrote:
>
>> AllenJB wrote:
>>
>>> Is there a breakdown of tasks for updating the handbooks for autobuilds?
>>>
>> This is something that I've brought up on this list all the way back at
>> the beginning of March[1].
>>
>> As of right now, no one's bothered to reply on the list, nor respond
>> when I jump on to our IRC channel.
>>
>> But as I'm the only one doing any work these days, I have no idea when
>> the rest might be completed. As far as I know I'm the only one to even
>> start to consider all the things that need to be changed.
>>
>> [several points...] That's it for now, I guess.
>>
>
> To me this sounds like an issue that needs to be brought to the
> attention of the council. Having good documentation has always been one
> of the strengths of Gentoo. It would be sad to see that wither away
> because of lack of manpower or lack of interest. Maybe we need to do
> some targeted recruiting for the documentation team.
>
> Cheers,
>
I have contributed a document to the documentation team. While it is
unrelated to the autobuilds and the handbook, it shows interest in the
team. I know that Josh has been doing an immense amount of work for the
doc team, which is evidenced by his name showing up as "editor" on tons
of the existing documents. As Ben said, documentation is one of the
strongest points of Gentoo, so we cannot let it go by the wayside. I'm
willing to learn the ins and outs of editing existing documents, and the
other aspects of the doc team.
Two people actively working on documents is not enough either, but it
will hopefully offset some of the labour. I don't think that the team
would have any trouble finding volunteers to help out with editing, and
that an announcement should be made on the forum.
--Zach
next prev parent reply other threads:[~2009-04-30 15:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 10:22 [gentoo-doc] Handbooks / Autobuilds: What needs to be done? AllenJB
2009-04-30 1:14 ` Josh Saddler
2009-04-30 14:52 ` Ben de Groot
2009-04-30 15:29 ` Nathan Zachary [this message]
2009-04-30 20:29 ` Josh Saddler
2009-04-30 21:07 ` Nathan Zachary
2009-04-30 22:27 ` Josh Saddler
2009-04-30 23:21 ` Nathan Zachary
2009-05-01 0:41 ` wireless
2009-05-01 8:13 ` Ben de Groot
2009-05-01 11:30 ` [gentoo-doc] " Duncan
2009-05-01 11:44 ` AW: " KKH
2009-05-01 18:30 ` Марьясин Семён
2009-04-30 20:45 ` [gentoo-doc] " Joseph Jezak
2009-04-30 20:54 ` Josh Saddler
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=49F9C3E8.1080007@gentoo.org \
--to=kalos@gentoo.org \
--cc=gentoo-doc@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