Fix BarnOwl capitalization

[wiki.git] / projects / ideas.mdwn

diff --git a/projects/ideas.mdwn b/projects/ideas.mdwn
index 0847055e13aa2daa8dd0d0b33ae73eeeaab2c9d6..2433d3a25f316484f78036d62f3c77312902a343 100644 (file)
--- a/projects/ideas.mdwn
+++ b/projects/ideas.mdwn
@@ -27,8 +27,11 @@ Kerberos / Moira) for the website, and write a script to set that keytab
 as the list's "membership ACL" and a webapp to use that capability to
 add or remove people from the list.
 
 as the list's "membership ACL" and a webapp to use that capability to
 add or remove people from the list.
 

+[adehnert notes 2013-02-24: More recently, WebMoira has been redone, and might more conveniently support this. It might be possible to directly integrate with WebMoira, or you might conclude that WebMoira is already good enough.]
+

 _Contact: geofft_
 
 _Contact: geofft_
 

+

 ## debdiffs of Debathena packages
 
 We have [a webpage](http://debathena.mit.edu/package-list/proposed) to
 ## debdiffs of Debathena packages
 
 We have [a webpage](http://debathena.mit.edu/package-list/proposed) to


@@ -129,7 +132,7 @@ Debathena bug tracker listing what should be a better implementation.
 
 _Contact: broder, debathena_
 
 
 _Contact: broder, debathena_
 

-## Checking scripts.mit.edu servers for consistency
+## [Checking scripts.mit.edu servers for consistency](http://scripts.mit.edu/trac/ticket/84)

 
 Now that we have five or six web servers (I've lost count), it's
 become entirely too easy to change something on one or some but not
 
 Now that we have five or six web servers (I've lost count), it's
 become entirely too easy to change something on one or some but not


@@ -164,7 +167,7 @@ Currently, it is a pain to get someone else set up using zephyr
 within screen on Linerva with automatically-renewing tickets.
 We should write scripts to set them up so that that all they
 have to do is enter a command or click an icon, type their kerberos
 within screen on Linerva with automatically-renewing tickets.
 We should write scripts to set them up so that that all they
 have to do is enter a command or click an icon, type their kerberos

-password, and then know how to use Barnowl.
+password, and then know how to use BarnOwl.

 
 _Contact: afarrell_
 
 
 _Contact: afarrell_
 


@@ -197,7 +200,7 @@ _Contact: xavid_
 
 ## A zephyr log viewer
 
 
 ## A zephyr log viewer
 

-Many SIPB-affiliated people use the [Zephyr](http://zephyr.1ts.org/) messaging system, and the [Barnowl](http://barnowl.mit.edu/) client for it in particular. Barnowl has a number of very nice features that make it easy to follow large amounts of zephyr traffic: search, color coding, auto-narrowing, etc. Barnowl can also store logs of zephyrs sent and received for future reference, but the logs are saved separated by class in a way that's quite annoying to navigate sometimes. A Barnowl-like interface (perhaps implemented as a Barnowl plugin) for viewing zephyr logs would be a great thing to have.
+Many SIPB-affiliated people use the [Zephyr](http://zephyr.1ts.org/) messaging system, and the [BarnOwl](http://barnowl.mit.edu/) client for it in particular. BarnOwl has a number of very nice features that make it easy to follow large amounts of zephyr traffic: search, color coding, auto-narrowing, etc. BarnOwl can also store logs of zephyrs sent and received for future reference, but the logs are saved separated by class in a way that's quite annoying to navigate sometimes. A BarnOwl-like interface (perhaps implemented as a BarnOwl plugin) for viewing zephyr logs would be a great thing to have.

 
 _Contact: oremanj_
 
 
 _Contact: oremanj_
 


@@ -270,10 +273,20 @@ _Contact: zhangc, kasittig_
 
 ## Zephyr Client Hints
 
 
 ## Zephyr Client Hints
 

-Some time ago I wrote [a spec for zephyr client hints](http://geofft.mit.edu/p/zephyr-client-hints.txt), optional extensions that zephyr clients can easily implement to add nifty stuff like typing indicators and [preventing zwgc from starting more than once per user](http://debathena.mit.edu/trac/ticket/206) and such. I got lazy before actually implementing these specs, but I believe they'd be relatively easy extensions to both zwgc and barnowl (in their respective extension languages, even — no changes needed to core).
+Some time ago I wrote [a spec for zephyr client hints](http://geofft.mit.edu/p/zephyr-client-hints.txt), optional extensions that zephyr clients can easily implement to add nifty stuff like typing indicators and [preventing zwgc from starting more than once per user](http://debathena.mit.edu/trac/ticket/206) and such. I got lazy before actually implementing these specs, but I believe they'd be relatively easy extensions to both zwgc and BarnOwl (in their respective extension languages, even — no changes needed to core).

 
 _Contact: geofft_
 
 
 _Contact: geofft_
 

+
+## Project Waverly
+
+[Project Waverly](http://waver.ly/) is attempting to rethink collaborative text editing. We are starting a project to do collaborative text (and other
+stuff) editing right -- clean protocol, reasonable algorithms, good web
+client, good plugins for desktop text editors, nice API, version control
+integration, etc. etc.
+
+_Contact: lizdenys, geofft, maria89_
+

 ## Your Project Here
 
 SIPB can help you out in terms of both computing resources and
 ## Your Project Here
 
 SIPB can help you out in terms of both computing resources and