[259] in BarnOwl Developers

home help back first fref pref prev next nref lref last post

Regarding owl development

daemon@ATHENA.MIT.EDU (Alejandro R. Sedeno)
Thu Oct 29 18:04:14 2009

Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
Date: Mon, 30 Oct 2006 01:08:04 -0500
From: "Alejandro R. Sedeno" <asedeno@MIT.EDU>
Reply-To: dirty-owl-hackers@MIT.EDU
To: kretch@mit.edu
CC: dirty-owl-hackers@mit.edu

kretch,

The owl hacker community appears to have achieved some critical mass
last week. We've taken owl from cvs and dropped it into an svn
repository where have been hacking on it together. We've incorporated
the patches on bugzilla, and extended its functionality in new and
interesting ways.

We would like to collaborate on owl, but from our point of view owl
development appears to have stagnated; the last release is already over
a year and a half old. We would like to know what your plans are for owl
before we fork and release our own version.

We'd also like to share some of the ideas we've been working on. Over
the course of the last week, we've exposed more of owl's C functionality
to perl, allowing it to hook into main loop and inject arbitrary
messages. We've taken that base and and the owlconf system I (asedeno)
mailed you about in Jan 2005, and in the past couple of days have added
preliminary jabber support using Net::Jabber.

The svn repository is available at
/afs/athena.mit.edu/user/n/e/nelhage/svn/dirty-owl-hacks/
readable by the public LIST:dirty-owl-hackers.

We look forward to hearing from you,

Those dirty owl hackers,
dirty-owl-hackers@mit.edu


home help back first fref pref prev next nref lref last post