A [[list from 2008-2009|/doc/project-ideas]] may also have some relevant ideas.
+[[!toc]]
+
## "add me to this list" button
If I'm a webmaster for some group with an announcement list, it would be
_Contact: pbaranay, fawkes_
-## Search across every public git repository
-
-The [git](http://www.git-scm.com/) version control system has been
-rapidly gaining in popularity both in the world of free software at
-large as well as at here at SIPB. One of the properties of git is
-that every object, whether it's a specific version of a file or a
-changeset to a project's source code, has a unique identifying hash
-(e.g., "8c5fa44b1a4902ba1f84a71df20bfe4f21867a7c"). Given one of these
-hashes, it should be possible to identify which project it came from
-and what it refers to.
-
-The "easy" way to do this is to create a massive single git repository
-with references to every public git repository we can find, but that
-probably causes performance problems, so you may need to be cleverer
-about how data is stored and expose a different interface. You'll
-also need to figure out a way to find all public git repositories.
-
-_Contact: geofft, nelhage_
-
## Improve the Setup and UI for new users of Zephyr
Currently, it is a pain to get someone else set up using zephyr
_Contact: afarrell_
+## MITeX
+
+Not a fully formed thought, yet, but the basic idea is to have a web app that lets users create a document, and then it texs the document nicely for them, based on some template that they've selected, and gives them a PDF. They should have the ability to edit the source or just use the WYSIWYG editor.
+
+_Contact: jhamrick_
+
+## Build a web client providing full control to the user
+
+Create a web browser extension (or possibly a stand-alone browser) that is "web-developer antagonistic". It essentially takes full advantage of the
+immense power of a web client, ignoring the wishes of the web developer and server while letting the user take full control. Every JavaScript event (ideally variable, function, etc.), every rendering decision, every cookie setting, every HTTP request, if the user so desires, etc. is not only made visible but easily changeable. When making a request, every aspect of the
+transaction can be completely fiddled with.
+
+There are several extensions that allow you to do stuff sort of like
+this (Firebug, Web Developer Toolbar, Chrome's web developer tools). But they're hard to use and really mostly just debuggers. Our goal here is to build something that goes out of its way to give you complete control via a nice UI.
+
+_Contact: leonidg_
+
+## Improve git with shared checkouts
+
+Around SIPB we're kind of [big](http://sipb.mit.edu/iap/git/) [fans](http://web.mit.edu/cluedumps/slides/understanding-git-2008.pdf) [of](http://blog.nelhage.com/2010/01/on-git-and-usability/) [git](http://negativespace.mit.edu/2010/03/08/gitionary-the-graphical-game-of-git-guessing/). But there is an area that git comes up short. We have a lot of common directories where people really just want to edit files in place (instead of wanting to clone/checkout, edit, commit, push...), but git doesn't support that well. It would be cool if there was a way to work with non-bare repositories in shared directories.
+
+One idea might be using FUSE to present a separate checkout to each person using the directory.
+
+_Contact: broder_
+
+## Scripts Pony Improvements
+
+[Scripts Pony](http://pony.scripts.mit.edu) is scripts.mit.edu's new hostname management system. It was just released recently, and has lots of bite-sized improvements remaining to be implemented. Particularly good ideas include adding the ability to show and edit hostname aliases, checking whether hostname paths exist and giving appropriate feedback, creating a zephyrbot to allow people to approve tickets easily, and adding the ability to check hostnames in Moira automatically.
+
+See [the project TODO file](http://web.mit.edu/pony/TODO) for more ideas.
+
+_Contact: xavid_
+
+## Bazki
+
+[Bazki](http://bazki.mit.edu/) is a wiki written in Python designed around several principles: structured data with object-oriented inheritance; using a wiki language with powerful macros that can be compiled into either HTML or PDF (via LaTeX); and making the content editable offline using a VCS. Bazki works enough to to be useful, but it has lots of room for improvement and probably would benefit from some major design changes.
+
+_Contact: xavid_
+
## Your Project Here
SIPB can help you out in terms of both computing resources and
sipb-www / wiki.git / blobdiff