From: Tom Wijsman <TomWij@gentoo.org>
To: hwoarang@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/bug-cleaners: index.xml
Date: Sat, 16 Nov 2013 12:39:25 +0100 [thread overview]
Message-ID: <20131116123925.7d843394@TOMWIJ-GENTOO> (raw)
In-Reply-To: <52875710.1030709@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2633 bytes --]
On Sat, 16 Nov 2013 11:29:20 +0000
Markos Chandras <hwoarang@gentoo.org> wrote:
> On 11/16/2013 10:27 AM, Tom Wijsman (tomwij) wrote:
> > tomwij 13/11/16 10:27:43
> >
> > Added: index.xml
> > Log:
> > Initial project directory for the Bug Cleaners project.
> >
> > Revision Changes Path
> > 1.1 xml/htdocs/proj/en/bug-cleaners/index.xml
> >
> > file :
> > http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/bug-cleaners/index.xml?rev=1.1&view=markup
> > plain:
> > http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/bug-cleaners/index.xml?rev=1.1&content-type=text/plain
> >
> > Index: index.xml
> > ===================================================================
> > <?xml version="1.0" encoding="UTF-8"?>
> > <?xml-stylesheet href="/xsl/project.xsl" type="text/xsl"?>
> > <?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
> > <!DOCTYPE project SYSTEM "/dtd/project.dtd">
> >
> > <project disclaimer="obsolete"
> > redirect="http://wiki.gentoo.org/wiki/Project:Bug_Cleaners">
> > <name>Bug Cleaners</name> <longname>Gentoo Bug Cleaners</longname>
> > <description>The Gentoo Bug Cleaners project aims to clean up the
> > oldest bugs in Bugzilla.</description> <longdescription><p>Our goal
> > is twofold, the main purpose of this project is to close bugs on
> > Bugzilla that do no longer apply due to versions and/or packages
> > that are no longer present in the Portage tree; as a side effect,
> > it also tries to look for solutions to the oldest bugs. For those
> > that still have use, it attempts to inform the persons involved in
> > the bug that the bug is still open if the bug is important;
> > inviting them to take a decision on it.</p></longdescription>
> > </project>
>
> I think this is unnecessary. Infra requested all new projects to be in
> the Wiki so I don't think that you are supposed to add a proj/en page
> anymore just so you can redirect it to the Wiki
True, GLEP 39 does still require it so a 11 lines file doesn't hurt;
not sure what the right approach to update that GLEP is, especially
given that its authors are no longer have commit access to it.
We could raise this at the open floor call of the Council meeting.
On a side note, while we're at it we could mark the authors there as
retired or update their e-mail address; whichever way fits better.
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-11-16 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131116102743.E880E2004B@flycatcher.gentoo.org>
2013-11-16 11:29 ` [gentoo-dev] Re: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/bug-cleaners: index.xml Markos Chandras
2013-11-16 11:39 ` Tom Wijsman [this message]
2013-11-16 12:09 ` Tomáš Chvátal
2013-11-16 13:40 ` Ulrich Mueller
2013-11-16 13:55 ` Tom Wijsman
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=20131116123925.7d843394@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=hwoarang@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