Here documents Scripts specific code inside Wizard that should
be moved away:
- * We store Wizard info inside .scripts/; this should really be
- .wizard. This might be kind of crappy to change, though. Maybe
- .scripts should still contain Scripts specific info, but we
- should instantiate a .wizard directory automatically (which should
- be ignored) that doesn't need to be created in repositories.
-
- * wizard.scripts is the location that all Scripts specific code
- will eventually live.
-
- * [HOOK] wizard.sql does a Script's specific call to get SQL
- information if no SQL credentials are explicitly passed.
-
- * In wizard.util
- - [HOOK] get_dir_owner performs a PTS query if normal pwd
- querying fails
- - [HOOK] get_operator_name_from_gssapi requires a patch to SSH
- that we patched support for
- - [HOOK] get_operator_info consults Hesiod for more information
- based on a username.
- - [HOOK] set_author_env guesses emails using scripts.mit.edu
- addresses
-
- * [HOOK] wizard.install contains strategies for guessing variables
- for an installation that are Scripts specific
-
- * We should have `wizard install` do something intelligent about
- prompting a user about possibilities; not everyone is going to
- use the scripts-start wrapper.
+ * wizard/app/__init__.py still has some Scripts stuff
+
+ - Tags
+
+ * [DEFER] `wizard migrate` should be moved to Scripts plugin
+
+ * [DEFER] We should have `wizard install` do something intelligent
+ about prompting a user about possibilities; not everyone is going
+ to use the scripts-start wrapper.
+
+ * [DEFER] old_log is Scripts specific, and any code that uses it
+ should be plugin-ified.
* [DEFER] The mass-* commands are especially designed for Scripts,
so while they're ostensibly portable, they'd probably need a bit