Here are ideas you can try to get started on a SIPB project. Some of these are mature projects with active new development a new contributor can help out with, others are only grand plans that need someone to take them on as their own. Talk to the people identified for each project to see how you can help, or ask the SIPB Chair (`price`) or Vice-Chair (`nelhage`). The descriptions here are usually accurate but the projects are constantly changing. If you have a project and want people to help, go ahead and add it. * `` -- Talk to `geofft` or `quentin` * Find some software we don't have an autoinstaller for, and write an autoinstaller for it. Or update an autoinstaller to a newer version of the software. This doesn't require a lot of code, since we have several autoinstallers already written, but will require a bit of testing. * Add a web interface for scripts users to edit their LDAP entries, which are internal entries that affect several things about their site * Read through already answered e-mails and update the FAQ on the website and other parts of our documentation. This is a great way to learn how scripts works * Write a blog aggregator, something like, so that scripts blog users can publish their entries on certain topics to an MIT-wide blog * install `old-faithful`; see [http://scripts/trac/browser/server/doc/install-howto `server/doc/install-howto`] for the steps * XVM - talk to `price` or `broder` * (done) make `` available on remote * validate more operations at remote rather than web * expose more operations over remctl in addition to web * put our hosts in Moira * ajaxify / javascriptify the website * get SPNEGO working, i.e. accept Kerberos auth on the website * Give the website a stylistic facelift. * voip-scripts - talk to `geofft` * read about Asterisk, AGI, study `captain-crunch:/etc/asterisk` and `/var/lib/asterisk` * figure out draft suexec code at `/var/lib/asterisk/agi-bin/suexec.c` * figure out or ask what's not working, figure out how to do it * Documentation project * Assemble good documentation of AFS from a user's perspective. There's lots of documentation, but only small parts are good and useful. * Cull old Ask SIPB columns into documentation. * Cull documentation into new Ask SIPB columns. * Debathena - talk to `broder` or `geofft` * a livecd would be awesome; there are tools these days to make this tractable * Archiver - talk to `nelhage` We want to build a mail archiving system for Moira lists. We're planning to store mail into AFS, and expose archives via AFS, IMAP, and the web.