sm-discuss AT lists.ibiblio.org
Subject: Public SourceMage Discussion List
List archive
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my
- From: "Matt Donovan (Kitche)" <kitche AT reddphoenix.com>
- To: sm-discuss AT lists.ibiblio.org
- Subject: Re: [SM-Discuss] policy docs, developer lists, jargon, oh my
- Date: Fri, 05 May 2006 06:55:24 -0500
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arwed von Merkatz wrote:
> On Sun, May 07, 2006 at 12:18:49AM -0500, Jeremy Blosser wrote:
>> On May 06, Eric Sandall [eric AT sandall.us] wrote:
>>> Jeremy Blosser (emrys) wrote:
>>>> To pull a few of these threads into one...
> [...]
>>> I would propose the two following changes:
>>>
>>>> general dev lead dev ----------- -------- generic :
>>>> mage -> elder
>>>>
>>>> cauldron : wizard -> warlock grimoire : guru ->
>>>> ??? sage?
>>> archwizard
>>>> sorcery : wizard -> warlock tome : ??? scribe? ->
>>>> ??? bard?
>>> sage
>>>
>>> Sage usually holds knowledge for others to reference/ask about,
>>> which would fit more the Tome Team (documentation, website,
>>> forums, etc.) to me. :)
>> Yeah, makes sense, Jason what do you think?
>>
>>> Archwizard just sounds cool (and I wanted to use sage for Tome
>>> ;)). <snip>
>> I was going to suggest just 'arch' to keep it shorter and be less
>> likely to confuse people with the similarity to 'wizard', but
>> what about 'archon' instead (yes, it's more Greek and less D&D,
>> but where in D&D did 'guru' come from anyway)? Arwed, do you
>> have any thoughts?
>
> archon sounds good to me.
>
ok I believe this is worded like I want it.
The guru ->warlock naming scheme might make some people confused, due
to guru usually means support usually or something along those lines.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEWz0rbJ8ccEoJ3f4RAmZJAJ47K1uZWzn74gZ53GlsXpPMJ7B0jwCgxVRZ
vNAi5/nr0FP/Xgg/ABjTyDA=
=Q+iE
-----END PGP SIGNATURE-----
-
[SM-Discuss] policy docs, developer lists, jargon, oh my,
Jeremy Blosser (emrys), 05/06/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Eric Sandall, 05/06/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Jeremy Blosser, 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Eric Sandall, 05/07/2006
- Re: [SM-Discuss] policy docs, developer lists, jargon, oh my, Mathieu L., 05/22/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Arwed von Merkatz, 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Jeremy Blosser, 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Eric Sandall, 05/07/2006
- Re: [SM-Discuss] policy docs, developer lists, jargon, oh my, Jeremy Blosser, 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Eric Sandall, 05/07/2006
- Re: [SM-Discuss] policy docs, developer lists, jargon, oh my, Matt Donovan (Kitche), 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Jeremy Blosser, 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Eric Sandall, 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Jeremy Blosser, 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Robin Cook, 05/06/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Andraž "ruskie" Levstik, 05/07/2006
- Re: [SM-Discuss] policy docs, developer lists, jargon, oh my, Karsten Behrmann, 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Juuso Alasuutari, 05/07/2006
- Re: [SM-Discuss] policy docs, developer lists, jargon, oh my, Jeremy Blosser, 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Andraž "ruskie" Levstik, 05/07/2006
-
Re: [SM-Discuss] policy docs, developer lists, jargon, oh my,
Eric Sandall, 05/06/2006
Archive powered by MHonArc 2.6.24.