1 - [SCRIPTS] MediaWiki 1.6.7, 1.9.3 and 1.10.0
4 - phpBB or phpbb? (right now it's the former)
5 - need an upgrade story; srv needs more versions
6 - need a story about install/ contrib/
8 - The merge interface is a kind of major UI disaster; you won't
9 be able to use it unless you know how Git works. Also, the
10 merges can be quite difficult to resolve if upstream has made
11 large formatting changes like reindenting. We may also consider
12 providing a --rebase option, which seems to do better when
13 big problems like this show up.
15 - Show progress or something when upgrading
16 - Allow 'sticky notes' for future upgraders to notice
17 - .wizard/url semantics are subtly wrong: in particular, if we
18 explicitly configure a URL at install, we should be able to
19 detect this URL as baked in from the configuration
21 - Rerere support doesn't actually work
22 - "Version 3.0.0 doesn't exist; did you mean 3.0?"
23 - Be a little more intelligent when perform web checks; for example,
24 if we get a forbidden message, that probably means we go the right
25 address but it's blocked off; if we get a 404 message, that probably
26 means wrong address. Account Unknown is something particularly good
28 - Wordpress module can do something intelligent if we get redirected
29 to the installation page.
30 - wizardResolve* files seem to get left in tmp en-mass, and we don't
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
63 - util.fetch() should use urllib under the hood, not httplib. Code
64 has to be changed. We should log if we get redirected.
67 - Add support for mypristine workflow
68 - Figure out why Sphinx sometimes fails to crossref :func: but wil
69 crossref :meth:, even though the dest is very clearly a function.
70 Example: :func:`wizard.app.php.re_var`
71 - The TODO extension for Sphinx doesn't properly force a full-rebuild
72 - Make single user mass-migrate work when not logged in as root. The
73 primary difficulty is making the parallel-find information easily
74 accessible to individual users: perhaps we can do a single-user
75 parallel-find on the fly.
76 - Don't use the scripts heuristics unless we're on scripts with the
77 AFS patch. Check with `fs sysname`
78 - Make 'wizard summary' generate nice pretty graphs of installs by date
79 (more histograms, will need to check actual .scripts-version files.)
80 - It should be able to handle installs like Django where there's a component
81 that gets installed in web_scripts and another directory that gets installed
84 - [SCRIPTS] ACLs is a starting point for sending mail to users, but it
85 has several failure modes:
86 - Old maintainers who don't care who are still on the ACL
87 - Private AFS groups that aren't mailing lists and that we can't get
88 to A question is whether or not sending mail actually helps us:
89 many users will probably have to come back to us for help; many
90 other users won't care.
91 - Whatever happens here should be used to improve user.email()
95 COMMIT MESSAGE FIELDS:
97 Installed-by: username@hostname
98 Pre-commit-by: Real Name <username@mit.edu>
99 Upgraded-by: Real Name <username@mit.edu>
100 Migrated-by: Real Name <username@mit.edu>
101 Wizard-revision: abcdef1234567890
102 Wizard-args: /wizard/bin/wizard foo bar baz
106 Committer: Real Name <username@mit.edu>
107 Author: lockername locker <lockername@scripts.mit.edu>
111 [ XXX: doc/deps.rst ]
112 * Some parts of the infrastructure will not be touched, although I plan
113 on documenting them. Specifically, we will be keeping:
115 - get-homedirs.sh. which needs to be run as root on scripts. Store
116 in /mit/scripts/sec-tools/store/scriptslist
118 - parallel-find.pl, and the resulting
119 /mit/scripts/sec-tools/store/versions
121 [ XXX: doc/deploy.rst ]
122 GET APPROVAL BEFORE PROCEEDING ANY FURTHER;
123 THIS IS PUSHING THE CHANGES TO THE PUBLIC
125 NOTE: The following commands are to be run on not-backward.mit.edu.
126 You'll need to add daemon.scripts-security-upd to
127 scripts-security-upd to get bits to do this. Make sure you remove
128 these bits when you're done.
130 10. Run `wizard research appname`
131 which uses Git commands to check how many
132 working copies apply the change cleanly, and writes out a logfile
133 with the working copies that don't apply cleanly. It also tells
134 us about "corrupt" working copies, i.e. working copies that
135 have over a certain threshold of changes.
137 11. Run `wizard mass-upgrade appname`, which applies the update to all working
140 12. Run parallel-find.pl to update our inventory
142 [ XXX: doc/metadata.rst ]
143 * The repository for a given application will contain the following files:
145 - The actual application's files, as from the official tarball
147 - A .scripts directory, with the intent of holding Scripts specific files
148 if they become necessary.
150 - .scripts/dsn, overriding database source name