public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Xavier Neys <neysx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 39 compliance
Date: Thu, 31 Aug 2006 00:00:45 +0200	[thread overview]
Message-ID: <44F60A8D.1010006@gentoo.org> (raw)
In-Reply-To: <44F59370.8040303@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]

Alec Warner wrote:
> Danny van Dyk wrote:
>> Am Mittwoch, 30. August 2006 14:26 schrieb Alec Warner:
>>
>>> Eselect, your project pages lists retired developers (Ciaran).[4]
>> Ciaran is the original Author, and he still helps more than ocassionally 
>> with problems and bugs. I won't remove him from that page.
>>
>> As precedences, the Gentoo Handbook list of authors contains former 
>> Gentoo devs.

Not just the handbook. Whenever any dev retires, all docs which he is credited
in should be updated with his new email, or no @gentoo.org email.
This has been mentioned on #gentoo-doc a few weeks ago.
Using the roll-call to replace the @gentoo.org email of a retired dev with his
new one or no email is on my todo list.

>> Danny
> 
> The only problem is that it lists him as contactable by
> "nickname@gentoo.org" aka ciaran@gentoo.org which is false.
> 
> I've actually wondered about this as well since I've been in projects as
> a non-dev and Treecleaners has non-devs.  Can we get some kind of
> modification to the <dev> tag for non-gentoo contributors?

Atm, using the <dev> implies the dev is listed in the roll-call.
The status can be tested to perform s/Member/Retired/
A fourth column with the email instead of the hardcoded text "All developers
can be reached by e-mail using nickname@gentoo.org." below the table is a
trivial thing to do.
Extending dev with something like
<dev role="Contributor" nick="fnord" email="foo.bar@fnord.tv">Mr. Foo
Bar</dev> would be no problem.

> I would agree with you that removing him would be immensely inconsiderate.

Once you guys have made up your mind, please do file a bug for me as I tend to
not read much of -dev. Thanks.


Wkr,
-- 
/  Xavier Neys
\_ Gentoo Documentation Project
/
/\ http://www.gentoo.org/doc/en/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  parent reply	other threads:[~2006-08-30 22:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 12:26 [gentoo-dev] GLEP 39 compliance Alec Warner
2006-08-30 13:54 ` 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 [this message]
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=44F60A8D.1010006@gentoo.org \
    --to=neysx@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