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