From: Torsten Veller <tove@gentoo.org>
To: gentoo-qa@lists.gentoo.org
Subject: [gentoo-qa] Devmanual status
Date: Sat, 2 Dec 2006 14:11:46 +0100 [thread overview]
Message-ID: <20061202133803.TAb6a5a.tv@veller.net> (raw)
Hello,
so what's going on with the devmanual?
Current situation AFAIK:
After the repo has been moved to Gentoo hardware,
Stephen Bennett (spb) and Christel Dahlskjaer (christel) and the Council
members have write permission and every dev can check it out with:
`svn co svn+ssh://devname@svn.gentoo.org/var/svnroot/devmanual`
With the new bugzilla we will also get a devmanual component in the
"Doc Other" product. New bugs will be assigned to qa@g.o.
Currently devmanual's project page is outdated:
<http://www.gentoo.org/proj/en/qa/devmanual.xml>
But I don't know what should be added there.
The future:
- moving to guide-xml?
- moving to rst?
- diff mailinglist for reviewing changes and to keep people up to date?
BTW:
the QA team has a new member: Steve Dibb (beandog) joined the team and
Alec Warner (antarus) has left this hellhole some time ago.
Welcome and farewell.
--
gentoo-qa@gentoo.org mailing list
next reply other threads:[~2006-12-02 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 13:11 Torsten Veller [this message]
2006-12-02 15:53 ` [gentoo-qa] Devmanual status Stephen Bennett
2006-12-02 16:35 ` Stephen Bennett
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=20061202133803.TAb6a5a.tv@veller.net \
--to=tove@gentoo.org \
--cc=gentoo-qa@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