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