- **Pony for autoinstalls.** We have [a nice interface](https://pony.scripts.mit.edu:44) for managing all of the hostnames you own. We do not have a nice interface for managing all of the autoinstalls you have made. Using [wizard](http://scripts.mit.edu/wizard) build an interface that lets you know about all the autoinstalls you have, and lets you upgrade them, check what your diff with upstream is, back them up, or delete them.
+- **Pony for cron.** Editing crontabs? That's so 90s! Code up a spiffy interface for editing your cronjobs, scheduling them, and testing to make sure they work (even when all your environment variables get nuked.)
+
- **Scripts Liberation.** It's your data. Write an application which makes it easy to take all of your information off of Scripts (SQL especially) and move it somewhere else.
- **Reset my password from the command line.** OK, so you forgot your password. You click "Forgot my password" and you get emailed a password. Oh, you say you didn't set your password? Well, then you might have to go edit the database. Maybe that's not so user friendly. What if you could run 'wizard change-password' and then have a nice, application-aware tool to change passwords? Might be handy. Add a 'change-password' command to [wizard](http://scripts.mit.edu/wizard).
-- **A more friendly Forbidden sign.** There are any number of conditions that could lead to a 403 on Scripts, including an explicit Deny rule, a poorly chosen file extension, a CGI script lacking an executable bit, etc. Right now, we give no guidance about what of these many, many problems is afflicting any given page. If you don't know much about coding but want to write documentation that will make a difference, try redesigning a 403 page that is actually helpful! If it's good, we'll deploy it on our servers and you will aid new Scripts users all over MIT's campus.
+- **A more friendly Forbidden sign.** There are any number of conditions that could lead to a 403 on Scripts, including an explicit Deny rule, a poorly chosen file extension, a CGI script lacking an executable bit, etc. Right now, we give no guidance about what of these many, many problems is afflicting any given page. If you don't know much about coding but want to write documentation that will make a difference, try redesigning a 403 page that is actually helpful! If it's good, we'll deploy it on our servers and you will aid new Scripts users all over MIT's campus. A similar project is for the **Welcome** page, which we should place in a new signup's web_scripts directory, to let them know how to use their shiny new Scripts instance.
[Straversity](http://straversity.com/mit/)
sipb-www / wiki.git / blobdiff