Source Mage utilizes a magic and mythology metaphor for the names of many of our project components. Some of these are defined below.
Source Mage's package management system component.
A collection of scripts, processed by Sorcery, to install a particular software package (similar to an RPM, ebuild, etc. for other distributions).
Generally, Source Mage's package collection component. More specifically, a collection of spells for a particular purpose.
A collection of grimoires.
Source Mage's installer and ISO generation scripts component.
Source Mage's documentation component, including general docs as well as end user-facing services such as web-sites, mailing lists, bug-tracking system, etc.
A Lead Developer or Assistant Lead as defined in our Developer Organization document.
An optional title for an elder who works with the cauldron or sorcery set of scripts.
An optional title for an elder who works with the grimoire.
An optional title for an elder who works with the tome.
A General Developer as defined in our Developer Organization document.
An optional title for a mage who works with the cauldron or sorcery set of scripts.
An optional title for a mage who works with the grimoire, especially those who are responsible for a particular section, e.g. "mail Guru".
An optional title for a mage who works with the tome.
See also: Other commands, Scribe.
Council of Elders
The Lead Developer Team and their Assistants, as defined in our Developer Organization document.
Circle of Mages
The General Developer Team, as defined in our Developer Organization document.
A developer in training, whose development commits must be approved by another developer before they reach the user-facing "test" releases. This is a voluntary restriction; all of our new developers have the option to immediately become full developers, and apprentices can become full developers any time they believe they are ready.
A Source Mage user (not a developer).
An automated process, e.g. an IRC-bot.
Sorcery command to modify the tracked files of an already-installed spell.
A tool to allow management of several Source Mage systems from a single machine.
Sorcery command to install a spell.
Sorcery command to inspect, clean, and repair broken systems.
Sorcery command to merge staged configuration files into the system.
Sorcery command to uninstall a spell.
Sorcery command to query system and spell information.
Sorcery command to install a spell from a cache tarball.
Sorcery command to copy spells between grimoires.
Sorcery command to add, remove, and manage grimoires installed on a system.
See also: People, Scribe.
Sorcery command to download upstream sources for a spell.