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 - Human readable quota output
9 - Nice error message on --continue if you forgot to git add your
10 resolved file (look for conflict markers)
11 - The merge interface is a kind of major UI disaster; you won't
12 be able to use it unless you know how Git works. Also, the
13 merges can be quite difficult to resolve if upstream has made
14 large formatting changes like reindenting. We may also consider
15 providing a --rebase option, which seems to do better when
16 big problems like this show up.
18 - Better mass-* support for just one user (this includes letting
19 a user mass upgrade just his own autoinstalls)
21 - Show progress or something when upgrading
22 - Allow 'sticky notes' for future upgraders to notice
23 - .wizard/url semantics are subtly wrong: in particular, if we
24 explicitly configure a URL at install, we should be able to
25 detect this URL as baked in from the configuration
27 - Rerere support doesn't actually work
28 - "Version 3.0.0 doesn't exist; did you mean 3.0?"
29 - Be a little more intelligent when perform web checks; for example,
30 if we get a forbidden message, that probably means we go the right
31 address but it's blocked off; if we get a 404 message, that probably
32 means wrong address. Account Unknown is something particularly good
34 - Wordpress module can do something intelligent if we get redirected
35 to the installation page.
36 - wizardResolve* files seem to get left in tmp en-mass, and we don't
39 - [SCRIPTS] Wordpress needs to get rid of the siteurl hack, so that it
40 actually has a fully-qualified URL http://foo.scripts.mit.edu/blah.
41 This will also fix Wordpress's cron functionality. We should be
42 careful not to write over users who are on vhosts. We should figure
43 out who is still on twiddle paths. We should make sure the redirect
46 - Remerges aren't reflected in the parent files, so `git diff` output is
47 spurious. Not sure how to fix this w/o tree hackery.
48 - Sometimes users remove files. Well, if those files change, they automatically
49 get marked as conflicted. Maybe we should say for certain files "if they're
50 gone, they're gone forever"? What is the proper resolution?
52 - Parse output HTML for class="error" and give those errors back to the user (done),
53 then boot them back into configure so they can enter in something different
55 - [SCRIPTS] If you try to do an install on scripts w/o sql, it will sign
56 you up but fail to write the sql.cnf file. This sucks.
58 - [SCRIPTS] Web application for installing autoinstalls has a hard
59 problem with credentials (as well as installations that are not
60 conducted on an Athena machine.) We have some crazy ideas involving a
61 signed Java applet that uses jsch to SSH into athena.dialup and
65 - Tidy up common code in callAsUser and drop_priviledges in shell;
66 namely cooking up the sudo and environment variable lines
67 - Summary script should be more machine friendly, and should not
68 output summary charts when I increase specificity
69 - util.fetch() should use urllib under the hood, not httplib. Code
70 has to be changed. We should log if we get redirected.
73 - Add support for mypristine workflow
74 - Figure out why Sphinx sometimes fails to crossref :func: but wil
75 crossref :meth:, even though the dest is very clearly a function.
76 Example: :func:`wizard.app.php.re_var`
77 - The TODO extension for Sphinx doesn't properly force a full-rebuild
78 - Make single user mass-migrate work when not logged in as root. The
79 primary difficulty is making the parallel-find information easily
80 accessible to individual users: perhaps we can do a single-user
81 parallel-find on the fly.
82 - Don't use the scripts heuristics unless we're on scripts with the
83 AFS patch. Check with `fs sysname`
84 - Make 'wizard summary' generate nice pretty graphs of installs by date
85 (more histograms, will need to check actual .scripts-version files.)
86 - It should be able to handle installs like Django where there's a component
87 that gets installed in web_scripts and another directory that gets installed
90 - [SCRIPTS] ACLs is a starting point for sending mail to users, but it
91 has several failure modes:
92 - Old maintainers who don't care who are still on the ACL
93 - Private AFS groups that aren't mailing lists and that we can't get
94 to A question is whether or not sending mail actually helps us:
95 many users will probably have to come back to us for help; many
96 other users won't care.
97 - Whatever happens here should be used to improve user.email()
101 COMMIT MESSAGE FIELDS:
103 Installed-by: username@hostname
104 Pre-commit-by: Real Name <username@mit.edu>
105 Upgraded-by: Real Name <username@mit.edu>
106 Migrated-by: Real Name <username@mit.edu>
107 Wizard-revision: abcdef1234567890
108 Wizard-args: /wizard/bin/wizard foo bar baz
112 Committer: Real Name <username@mit.edu>
113 Author: lockername locker <lockername@scripts.mit.edu>
117 [ XXX: doc/deps.rst ]
118 * Some parts of the infrastructure will not be touched, although I plan
119 on documenting them. Specifically, we will be keeping:
121 - get-homedirs.sh. which needs to be run as root on scripts. Store
122 in /mit/scripts/sec-tools/store/scriptslist
124 - parallel-find.pl, and the resulting
125 /mit/scripts/sec-tools/store/versions
127 [ XXX: doc/deploy.rst ]
128 GET APPROVAL BEFORE PROCEEDING ANY FURTHER;
129 THIS IS PUSHING THE CHANGES TO THE PUBLIC
131 NOTE: The following commands are to be run on not-backward.mit.edu.
132 You'll need to add daemon.scripts-security-upd to
133 scripts-security-upd to get bits to do this. Make sure you remove
134 these bits when you're done.
136 10. Run `wizard research appname`
137 which uses Git commands to check how many
138 working copies apply the change cleanly, and writes out a logfile
139 with the working copies that don't apply cleanly. It also tells
140 us about "corrupt" working copies, i.e. working copies that
141 have over a certain threshold of changes.
143 11. Run `wizard mass-upgrade appname`, which applies the update to all working
146 12. Run parallel-find.pl to update our inventory
148 [ XXX: doc/metadata.rst ]
149 * The repository for a given application will contain the following files:
151 - The actual application's files, as from the official tarball
153 - A .scripts directory, with the intent of holding Scripts specific files
154 if they become necessary.
156 - .scripts/dsn, overriding database source name