[SM-Discuss] policy docs, developer lists, jargon, oh my
eric at sandall.us
Sat May 6 20:08:32 EDT 2006
-----BEGIN PGP SIGNED MESSAGE-----
Jeremy Blosser (emrys) wrote:
> To pull a few of these threads into one...
> To resolve that question and get on with things, I'm suggesting we add a
> few more cloaks/title so that basically each component has a general
> developer and a lead developer title available, and then we can say that
> you can be listed on the developer page and cloaked using whichever title
> you want from among the components you have access to. Karsten can
> basically manage our cloaks for us now (and is one of the ones asking for
> this ;P) so it shouldn't be an issue with freenode. Proposed cloaks:
I would propose the two following changes:
> general dev lead dev
> ----------- --------
> generic : mage -> elder
> cauldron : wizard -> warlock
> grimoire : guru -> ??? sage?
> sorcery : wizard -> warlock
> tome : ??? scribe? -> ??? bard?
Sage usually holds knowledge for others to reference/ask about, which
would fit more the Tome Team (documentation, website, forums, etc.) to
Archwizard just sounds cool (and I wanted to use sage for Tome ;)).
Eric Sandall | Source Mage GNU/Linux Developer
eric at sandall.us | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the SM-Discuss