The Keep:Elven Grove

UNDER CONSTRUCTION

"Inspired by the pirates, the elves have come out of hiding, and now wander the forest of challenges, hunting any that are past their time (or the more dangerous undead tasks, completely hollow and empty), nurturing the young growing ones, and guiding those that have been separated from their herd."

Terminology
The language of the elves as spoken in the forest.

Adopted: Taken on by one of the elves or another responsible caretaker who will look after it until it's completion.

Dead: A challenge with an inactive owner and few or no participants.

Hunting: Deleting challenges, or requestion their deletion.

Lost: In a guild that is urelated to the challenges theme or subject, and better placed elsewhere.

Orphaned: A working challenge with active participants, but an inactive owner.

Undead: A challenge completely devoid of tasks. These are to be destroyed without mercy.

Not yet established:
A challenge that is past its stated completion date, but has active particpants. (Elderly? but then it sounds mean to kill it...)

Appealing to the Guardians
When appealing to the Great Forest Guardians for aid, one must heed the advice of the Guardian Goblin. For it is written:

I'd like to see: 
 * The URL for the challenge (it will contain the challenge's unique ID).
 * The name of the challenge (not strictly necessary since the URL will be given, but it's useful for checking that a copy-paste mixup hasn't included the wrong URL).
 * A brief note about whether the owner is inactive or non-responsive, or a statement that the person requesting the move is the owner. We can find the owner's details ourselves from the challenge so no need to include the details.
 * Reason for believing it is closable / movable.
 * If it is movable and the owner is active, they should either request moving it themselves (preferred but not essential) or their permission should be visible in a guild that an admin has access to (ideally a public guild, but also a private guild if the admin is sent an invitation).
 * The URL and name of the guild to move it to (URL will contain the guild's ID).
 * Requests should be placed in this guild. (Disagreements about this are especially welcome, including from the non-staff/mods who use this guild! Note though that I'd really prefer to not have to handle these by email for reasons I can describe if desired.)
 * No limit on how many requests at once or how often. If a request hasn't been handled after a week, please send a reminder.

 Some points to note:
 * Any staff or moderator can close or delete any challenge. However for moving a challenge, only  staff/mods with database access can do it. This is just FYI. Don't worry about tagging specific staff/mods - we'll sort out ourselves who does each request, probably just by whoever gets to it first. :)
 * Requests might be denied if we feel they're inappropriate. I would expect this would happen rarely or never, but it's worth mentioning. It might happen more often for moving a challenge.
 * If the move is to a guild that some might see as controversial, we'd have to be more careful (e.g., moving a cooking challenge to a guild where either the challenge or guild have a strict vegan focus and the focus isn't clearly shared by both challenge and guild).
 * When moving a challenge, we might need to consider whether the challenge participants should be notified in advance of the move. We'll look into this more when it happens, and it might be a case-by-case thing for every challenge that's moved.

And thus it shall be.