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
Subject: [gentoo-dev] GLEP 39 compliance
Date: Wed, 30 Aug 2006 08:26:41 -0400	[thread overview]
Message-ID: <44F58401.1030104@gentoo.org> (raw)

"A project exists if it has a web page at www.g.o/proj/en/whatever that
is maintained. ("Maintained" means that the information on the page is
factually correct and not out-of-date.) If the webpage isn't maintained,
it is presumed dead."

I'm not trying to pick on any projects.  Some pages are out of date but
look ok ( like catalyst!  Thats an old page! but i know you are writing
2.0 docs soon ;)).  I'm used my own descretion in picking out projects
(including projects for which I am a member).  Very few are dead, mostly
just listing retired devs as active.

Gentoo/MIPS, your project page needs updates (last updated 2005, by the
looks of things).  Your page also lists retired developers (Ciaran).[1]

Gentoo/PPC64, you also need to update your website (last updated 2005)[2]

Gentoo/Sparc, some of your developers were retired (todd,cjr)[3]

Eselect, your project pages lists retired developers (Ciaran).[4]

GLEP - I actually e-mailed Grant a bunch of updates and I'm waiting for
those to get done ;)

Portage/Sandbox - I say we just remove this, afaik no development has
happened in a long time.[5]

Installer - I know you guys have news, post some tidbits ;)[6]

kernel/security - Your page is bare, and lists brix as a member, he
resigned months ago.  Unless you feel this page is useful to some
people, I'm not sure what good it does.[7]

Gentoo/Status - Oh the irony ;) many of the projects listed never
updated their webpages, hopefully this mail will encourage some, lest I
just cvs rm -f their project pages for lack of updates ;)  no updates
for 4 months.[8]

Gentoo/QA - You have no lead, and your pages list retired developers
(Halcy0n).[9]

[1] http://www.gentoo.org/proj/en/base/mips/index.xml
[2] http://www.gentoo.org/proj/en/base/ppc64/index.xml
[3] http://www.gentoo.org/proj/en/base/sparc/index.xml
[4] http://www.gentoo.org/proj/en/eselect/index.xml
[5] http://www.gentoo.org/proj/en/portage/sandbox/index.xml
[6] http://www.gentoo.org/proj/en/releng/installer/index.xml
[7] http://www.gentoo.org/proj/en/security/kernel.xml
[8] http://www.gentoo.org/proj/en/userrel/gentoostatus/index.xml
[9] http://www.gentoo.org/proj/en/qa/index.xml
-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2006-08-30 12:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 12:26 Alec Warner [this message]
2006-08-30 13:54 ` [gentoo-dev] GLEP 39 compliance Danny van Dyk
2006-08-30 13:32   ` Alec Warner
2006-08-30 14:36     ` Wernfried Haas
2006-08-30 14:11       ` Alec Warner
2006-08-30 15:37         ` Wernfried Haas
2006-08-30 16:00           ` Simon Stelling
2006-08-30 15:49             ` Alec Warner
2006-09-01  0:52           ` [gentoo-dev] " Ryan Hill
2006-08-30 15:18       ` [gentoo-dev] " Christian Heim
2006-08-30 15:39         ` Wernfried Haas
2006-08-30 22:00     ` Xavier Neys
2006-08-30 17:09   ` [gentoo-dev] " Duncan
2006-08-30 17:35 ` [gentoo-dev] " Brian Harring

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=44F58401.1030104@gentoo.org \
    --to=antarus@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