From: Stephen Bennett <spb@gentoo.org>
To: gentoo-qa@lists.gentoo.org
Subject: Re: [gentoo-qa] Devmanual status
Date: Sat, 2 Dec 2006 15:53:32 +0000 [thread overview]
Message-ID: <20061202155332.206fdfd8@blashyrk> (raw)
In-Reply-To: <20061202133803.TAb6a5a.tv@veller.net>
On Sat, 2 Dec 2006 14:11:46 +0100
Torsten Veller <tove@gentoo.org> wrote:
> 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`
That's about it. For the moment, anyone else will have to push updates
through one of the above. Other QA members can request commit access if
they're going to be doing significant work on it.
> 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.
So I'm told, yes.
> 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.
Ouch, yes. I'll update that; thanks for pointing it out.
> The future:
> - moving to guide-xml?
I'd rather not, personally. I won't rule it out though, if someone
presents a convincing argument.
> - moving to rst?
This would be preferable from my point of view -- it's much nicer to
work with than the current XML.
> - diff mailinglist for reviewing changes and to keep people up to
> date?
Not a bad idea. Someone might consider asking infra to set this up.
--
gentoo-qa@gentoo.org mailing list
next prev parent reply other threads:[~2006-12-02 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 13:11 [gentoo-qa] Devmanual status Torsten Veller
2006-12-02 15:53 ` Stephen Bennett [this message]
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=20061202155332.206fdfd8@blashyrk \
--to=spb@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