1 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.
3 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.
5 If you have a project and want people to help, go ahead and add it.
7 * `scripts.mit.edu` -- Talk to `geofft` or `quentin`
8 * Find some software we don't have an autoinstaller for, and write an
9 autoinstaller for it. Or update an autoinstaller to a newer version of the
10 software. This doesn't require a lot of code, since we have several
11 autoinstallers already written, but will require a bit of testing.
12 * Add a web interface for scripts users to edit their LDAP entries, which are
13 internal entries that affect several things about their site
14 * Read through already answered e-mails and update the FAQ on the website and
15 other parts of our documentation. This is a great way to learn how scripts
17 * Write a blog aggregator, something like planet.debian.org, so that scripts
18 blog users can publish their entries on certain topics to an MIT-wide blog
19 * install `old-faithful`; see [http://scripts/trac/browser/server/doc/install-howto `server/doc/install-howto`] for the steps
21 * XVM - talk to `price` or `broder`
22 * (done) make `validation.py` available on remote
23 * validate more operations at remote rather than web
24 * expose more operations over remctl in addition to web
25 * put our hosts in Moira
26 * ajaxify / javascriptify the website
27 * get SPNEGO working, i.e. accept Kerberos auth on the website
28 * Give the website a stylistic facelift.
30 * voip-scripts - talk to `geofft`
31 * read about Asterisk, AGI, study `captain-crunch:/etc/asterisk` and `/var/lib/asterisk`
32 * figure out draft suexec code at `/var/lib/asterisk/agi-bin/suexec.c`
33 * figure out or ask what's not working, figure out how to do it
35 * Documentation project
36 * Assemble good documentation of AFS from a user's perspective. There's lots of
37 documentation, but only small parts are good and useful.
38 * Cull old Ask SIPB columns into documentation.
39 * Cull documentation into new Ask SIPB columns.
41 * Debathena - talk to `broder` or `geofft`
42 * a livecd would be awesome; there are tools these days to make this tractable
44 * Archiver - talk to `nelhage`
45 We want to build a mail archiving system for Moira lists. We're
46 planning to store mail into AFS, and expose archives via AFS, IMAP,