more for triaging / confirming bugs

[wiki.git] / projects / ideas.mdwn

diff --git a/projects/ideas.mdwn b/projects/ideas.mdwn
index 33bc53c5d2e129149256a715230a0e4bb08f3eb4..dcfa9f4ccca60045e77af4029438df251d91b46f 100644 (file)
--- a/projects/ideas.mdwn
+++ b/projects/ideas.mdwn
@@ -12,6 +12,8 @@ along with the person who's suggested the project or a team that would
 be good to contact. Feel free to get in touch if something sounds
 interesting or you want advice getting started.
 
+A [[list from 2008-2009|/doc/project-ideas]] may also have some relevant ideas.
+
 ## "add me to this list" button
 
 If I'm a webmaster for some group with an announcement list, it would be
@@ -107,19 +109,6 @@ support. If this is the kind of thing that interests you...
 
 _Contact: nelhage_
 
-## inotify logger for scripts and Debathena
-
-On both our [web hosting platform](http://scripts.mit.edu/) and Athena
-cluster machines, we have way more software packages installed than we
-suspect people use, but no good way of determining this. There's a Linux
-interface called [inotify](http://en.wikipedia.org/wiki/Inotify) that
-lets you get notifications when another user accesses the filesystem: it
-would be pretty simple to use this to collect aggregate (anonymous)
-statistics of what programs and packages are used frequently or even at
-all.
-
-_Contact: geofft_
-
 ## SIPB PostgreSQL server
 
 A lot of people prefer Postgres to MySQL, so having a community Postgres
@@ -179,6 +168,25 @@ database. One possible platform is the [Exhibit](http://simile-widgets.org/exhib
 
 _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_
+
 ## Your Project Here
 
 SIPB can help you out in terms of both computing resources and