+There are a lot of projects: Scripts, Barnowl, Straversity, smiopp and cyclist all have different things to work on. Skim through, see what catches your fancy.
+
[Scripts](http://scripts.mit.edu)
=================================
talk to:
- **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.**
+- **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 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.
+
+
+[BarnOwl](http://barnowl.mit.edu/)
+==================================
+talk to:
+--------
+- [David Benjamin](mailto:davidben@mit.edu)
+- [Jason Gross](mailto:jgross@mit.edu)
+- [Edward Z. Yang](mailto:ezyang@mit.edu)
+
+BarnOwl is a curses-based IM client used by many MIT students. Work you do here will be appreciated by many excited BarnOwl users. Here are some projects to work on:
+
+- **More tab completion**. BarnOwl supports tab completion for a subset of its commands. Enlarge this subset; it's not particularly hard.
+
+- **Google Plus support**. Google Plus recently published an [API](http://developers.google.com/+/api/). Integrate it with BarnOwl! We have lots of other plugins adding support for things like Facebook and Twitter which you can use to get some inspiration. A subproject would be making Perl bindings for the Google Plus API.
+
+- **Facebook direct message support**. We recently landed Facebook support in the trunk, but it only supports messaging on walls. Add support for direct messages.
+
+- **GMail new message support**. Now you can obsess over your new emails in realtime! Add support for GMail's notification API: http://code.google.com/apis/talk/jep_extensions/gmail.html (see our existing XMPP bindings.)
+
+- **Setup [gerrit](http://code.google.com/p/gerrit/)**. We've been talking about moving from github to gerrit, which seems to have a better code review model, but we haven't had the chance nor time to set one up.
+
+- **Solve and close some trac tickets**. We have a bunch of [open issues on trac](http://barnowl.mit.edu/query). Look through them and pick one to work on. In particular, [#119](http://barnowl.mit.edu/ticket/119), [#122](http://barnowl.mit.edu/ticket/122), [#156](http://barnowl.mit.edu/ticket/156), [#162](http://barnowl.mit.edu/ticket/162), [#167](http://barnowl.mit.edu/ticket/167), [#192](http://barnowl.mit.edu/ticket/192), and possibly [#17](http://barnowl.mit.edu/ticket/17), [#193](http://barnowl.mit.edu/ticket/193), [#194](http://barnowl.mit.edu/ticket/194) all seem fairly reasonable for someone not particularly familiar with the code.
+
[Straversity](http://straversity.com/mit/)
==========================================
The project needs someone who is proficient in either Ruby or Python. In addition, C knowledge would be useful.
I am able to spend as much time as needed to get someone up-to-speed. After that I'll be spending time making the documentation and packaging not suck, which would also help someone new.
+
+
+cyclist
+=======
+talk to:
+--------
+- [Dafydd Harries](mailto:daf@rhydd.org)
+
+I'm working on tools for interactive audio and video processing.
+
+Most recently, I wrote an interface that converts mathematical expressions into sound. I also have projects that do music visualization.
+
+ I'm using Python, LLVM, Gtk+, NumPy, GStreamer, and OpenGL.
+
+All the code is in Python. Being familiar with some of the libraries I mentioned would be handy, but there are a lot of different directions to take things in, so the main thing is enthusiasm and curiosity. I'm happy to mentor people in any of the tools I'm using.
sipb-www / wiki.git / blobdiff