Set admin e-mail address properly on MediaWiki >= 1.18.0

[wizard.git] / SCRIPTS

diff --git a/SCRIPTS b/SCRIPTS
index b2707810759d3a736fbecf989c5791546209c37b..a98886c11466f1ad336a9d7263f9ceaca982d332 100644 (file)
--- a/SCRIPTS
+++ b/SCRIPTS
@@ -1,5 +1,5 @@
 Wizard and Scripts
-------------------
+==================
 
 We'd like Wizard to be sufficiently general so as to not work
 on Scripts. To some degree, it already is; Wizard can be easily
@@ -8,35 +8,20 @@ set up in a development type environment on a non-Scripts server.
 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.
-
-    * wizard.sql does a Script's specific call to get SQL information
-      if no SQL credentials are explicitly passed.
-
-    * In wizard.util
-        - get_dir_owner performs a PTS query if normal pwd querying
-          fails
-        - get_operator_name_from_gssapi requires a patch to SSH that
-          we patched support for
-        - get_operator_info consults Hesiod for more information based
-          on a username.
-        - set_author_env guesses emails using scripts.mit.edu addresses
-
-    * 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.
-
-    * The mass-* commands are especially designed for Scripts, so while
-      they're ostensibly portable, they'd probably need a bit of working
-      to be easy-to-use for other people.  They also rely on a
-      "versions" directory whose code exists independently of Wizard.
+    * 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
+      of working to be easy-to-use for other people.  They also rely on
+      a "versions" directory whose code exists independently of Wizard.