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