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