1 - [SCRIPTS] MediaWiki 1.9.3 and 1.6.7
3 - Blacklist should allow an easy way for a user to override it,
4 described in the error message.
5 - .wizard/url semantics are subtly wrong: in particular, if we
6 explicitly configure a URL at install, we should be able to
7 detect this URL as baked in from the configuration
9 - gct has accidentally set the +x bit on a lot of files >.>.
10 - Make gct do the right thing with no arguments
11 - Rerere support doesn't actually work
12 - Utility scripts gct should support multiple filenames
13 - "Version 3.0.0 doesn't exist; did you mean 3.0?"
14 - util.fetch() should use urllib under the hood, not httplib. Code
15 has to be changed. We should log if we get redirected.
16 - Be a little more intelligent when perform web checks; for example,
17 if we get a forbidden message, that probably means we go the right
18 address but it's blocked off; if we get a 404 message, that probably
19 means wrong address. Account Unknown is something particularly good
21 - Wordpress module can do something intelligent if we get redirected
22 to the installation page.
23 - The need to run egg_info can make things a little fragile when pulling
24 if you forget. How can we make this less easily forgotten?
25 - wizardResolve* files seem to get left in tmp en-mass, and we don't
28 - Plugin-ify! Hook-ify! In more detail, applications should all be moved
29 out into plugins, scripts specific behavior should be moved into
30 plugins, and hooks need to be made available so that we can exert
31 the correct level of control.
33 - [SCRIPTS] Wordpress needs to get rid of the siteurl hack, so that it
34 actually has a fully-qualified URL http://foo.scripts.mit.edu/blah.
35 This will also fix Wordpress's cron functionality. We should be
36 careful not to write over users who are on vhosts. We should figure
37 out who is still on twiddle paths. We should make sure the redirect
40 - Remerges aren't reflected in the parent files, so `git diff` output is
41 spurious. Not sure how to fix this w/o tree hackery.
42 - Sometimes users remove files. Well, if those files change, they automatically
43 get marked as conflicted. Maybe we should say for certain files "if they're
44 gone, they're gone forever"? What is the proper resolution?
46 - Parse output HTML for class="error" and give those errors back to the user (done),
47 then boot them back into configure so they can enter in something different
49 - [SCRIPTS] If you try to do an install on scripts w/o sql, it will sign
50 you up but fail to write the sql.cnf file. This sucks.
52 - [SCRIPTS] Web application for installing autoinstalls has a hard
53 problem with credentials (as well as installations that are not
54 conducted on an Athena machine.) We have some crazy ideas involving a
55 signed Java applet that uses jsch to SSH into athena.dialup and
59 - Tidy up common code in callAsUser and drop_priviledges in shell;
60 namely cooking up the sudo and environment variable lines
61 - Summary script should be more machine friendly, and should not
62 output summary charts when I increase specificity
65 - Add support for mypristine workflow
66 - Figure out why Sphinx sometimes fails to crossref :func: but wil
67 crossref :meth:, even though the dest is very clearly a function.
68 Example: :func:`wizard.app.php.re_var`
69 - The TODO extension for Sphinx doesn't properly force a full-rebuild
70 - Make single user mass-migrate work when not logged in as root. The
71 primary difficulty is making the parallel-find information easily
72 accessible to individual users: perhaps we can do a single-user
73 parallel-find on the fly.
74 - Don't use the scripts heuristics unless we're on scripts with the
75 AFS patch. Check with `fs sysname`
76 - Make 'wizard summary' generate nice pretty graphs of installs by date
77 (more histograms, will need to check actual .scripts-version files.)
78 - It should be able to handle installs like Django where there's a component
79 that gets installed in web_scripts and another directory that gets installed
82 - [SCRIPTS] ACLs is a starting point for sending mail to users, but it
83 has several failure modes:
84 - Old maintainers who don't care who are still on the ACL
85 - Private AFS groups that aren't mailing lists and that we can't get
86 to A question is whether or not sending mail actually helps us:
87 many users will probably have to come back to us for help; many
88 other users won't care.
89 - Whatever happens here should be used to improve user.email()
93 COMMIT MESSAGE FIELDS:
95 Installed-by: username@hostname
96 Pre-commit-by: Real Name <username@mit.edu>
97 Upgraded-by: Real Name <username@mit.edu>
98 Migrated-by: Real Name <username@mit.edu>
99 Wizard-revision: abcdef1234567890
100 Wizard-args: /wizard/bin/wizard foo bar baz
104 Committer: Real Name <username@mit.edu>
105 Author: lockername locker <lockername@scripts.mit.edu>
109 [ XXX: doc/deps.rst ]
110 * Some parts of the infrastructure will not be touched, although I plan
111 on documenting them. Specifically, we will be keeping:
113 - get-homedirs.sh. which needs to be run as root on scripts. Store
114 in /mit/scripts/sec-tools/store/scriptslist
116 - parallel-find.pl, and the resulting
117 /mit/scripts/sec-tools/store/versions
119 [ XXX: doc/deploy.rst ]
120 GET APPROVAL BEFORE PROCEEDING ANY FURTHER;
121 THIS IS PUSHING THE CHANGES TO THE PUBLIC
123 NOTE: The following commands are to be run on not-backward.mit.edu.
124 You'll need to add daemon.scripts-security-upd to
125 scripts-security-upd to get bits to do this. Make sure you remove
126 these bits when you're done.
128 10. Run `wizard research appname`
129 which uses Git commands to check how many
130 working copies apply the change cleanly, and writes out a logfile
131 with the working copies that don't apply cleanly. It also tells
132 us about "corrupt" working copies, i.e. working copies that
133 have over a certain threshold of changes.
135 11. Run `wizard mass-upgrade appname`, which applies the update to all working
138 12. Run parallel-find.pl to update our inventory
140 [ XXX: doc/metadata.rst ]
141 * The repository for a given application will contain the following files:
143 - The actual application's files, as from the official tarball
145 - A .scripts directory, with the intent of holding Scripts specific files
146 if they become necessary.
148 - .scripts/dsn, overriding database source name