public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: Re: [gentoo-dev] Treecleaner Project: Maintainer-needed page
Date: Fri, 20 Aug 2010 11:11:57 -0700	[thread overview]
Message-ID: <AANLkTikE29VpRaZewyrSQWxeyZOJKG89sr4b7qoMK1G-@mail.gmail.com> (raw)
In-Reply-To: <20100820113320.GA13020@Mystical>

Are you generating this and checking it in or is infra generating it
on their end?

I have some ideas for formatting and layout; plus it looks like you
are just blobbing all the packages directly into the GuideXML which
kind of sucks for structured data like this.  Typically I'd go for
something like maintainer-needed-packages.xml which just contains the
data and then maintainer-needed.xml is a small webpage (no data on it
at all) that includes some custom xsl that does the presentation.

Examples of said behavior:
http://www.gentoo.org/proj/en/glep/index.xml?passthru=1
http://www.gentoo.org/proj/en/glep/gleps.xml?passthru=1

-A

On Fri, Aug 20, 2010 at 4:33 AM, Markos Chandras <hwoarang@gentoo.org> wrote:
> Hi
>
> The Treecleaners project introduced ( over a month ) and new page[1] to track
> maintainer-needed packages. This page is automatically generated. You can make
> use of this page to track packages that needs your love instead of searching
> bugzilla or grep the entire tree.
>
> On behalf of the Treecleaners project
>
> [1]: http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml
> --
> Markos Chandras (hwoarang)
> Gentoo Linux Developer
> Web: http://hwoarang.silverarrow.org
> Key ID: 441AC410
> Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410
>



  parent reply	other threads:[~2010-08-20 18:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20 11:33 [gentoo-dev] Treecleaner Project: Maintainer-needed page Markos Chandras
2010-08-20 12:50 ` Thilo Bangert
2010-08-20 18:11 ` Alec Warner [this message]
2010-08-20 18:48   ` Markos Chandras
2010-08-20 19:19     ` Alec Warner
2010-08-20 19:41       ` Markos Chandras
2010-08-20 20:56         ` Thilo Bangert
2010-08-20 21:07           ` Markos Chandras
2010-08-20 22:13             ` Robin H. Johnson
2010-08-20 23:23               ` Markos Chandras

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=AANLkTikE29VpRaZewyrSQWxeyZOJKG89sr4b7qoMK1G-@mail.gmail.com \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev-announce@lists.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