[3718] in BarnOwl Developers

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

Fwd: Notes from Zephyr maintenance discussion meeting

daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Sun Feb 2 00:39:57 2014

Date: Sun, 2 Feb 2014 00:39:49 -0500 (EST)
From: Geoffrey Thomas <geofft@ldpreload.com>
To: barnowl-dev@mit.edu

Hi BarnOwl folks,

Karl's stepped down from active Zephyr maintenance and we're building up a 
new upstream Zephyr development team. If you're interested in helping or 
following along with development discussion, please blanche yourself onto 
zephyr-im or ask me to add you. See the email below for more info.

-- 
Geoffrey Thomas
https://ldpreload.com
geofft@ldpreload.com

---------- Forwarded message ----------
Date: Sun, 2 Feb 2014 00:38:07 -0500 (EST)
From: Geoffrey Thomas <geofft@ldpreload.com>
To: zephyr-im@mit.edu
Cc: David A Benjamin <davidben@mit.edu>, Mark W. Eichin <eichin@mit.edu>,
     Jeffrey Hutzelman <jhutz@cmu.edu>, Timothy G Abbott <tabbott@mit.edu>
Subject: Notes from Zephyr maintenance discussion meeting

Karl's stepping down from active Zephyr maintenance, so a bunch of us who were 
interested met in the SIPB office to discuss setting up a team of folks to 
maintain zephyr and run the project infrastructure. I've attached some notes, 
which are also available at

https://ldpreload.com/p/zephyr-notes-2014-02-01.txt

In the very short term, zephyr-im@mit.edu is a public Moira list for people who 
are interested. Please blanche yourself on, or ask one of us to add you, if 
you're interested in developing Zephyr, developing against Zephyr, deploying 
Zephyr, etc. In the somewhat short term (days), we'll get a domain name and 
install Mailman, and convert things over.

The room seemed pretty happy to move to GitHub for issue tracking and pull 
requests, since it opens up development to people who aren't Kerberos-peered 
with us and also avoids the problem of spam from opening up Trac access. 
There's a GitHub organization at https://github.com/zephyr-im that Anders and I 
are currently importing the Trac tickets and code into.

I think in general we'll be happy to have as many contributors as are 
interested. I would like to have some sort of development summit in maybe two 
or three months to talk about immediate and long-term goals, possibly including 
major protocol work, so it'd be good if people could think about availability 
for that. There was a suggestion from the room that it be in Pittsburgh -- 
Jeff, are you interested in making that happen?

There will be another email when
- GitHub is open for development
- There's a non-temporary mailing list
- I'm looking at actually planning a development meeting
so please add yourself to zephyr-im@mit.edu if you're interested in getting 
followups.

Feel free to forward this mail / the notes to interested parties. I'm certain 
I've missed people who are interested in Zephyr development.

I'd like to close this by thanking Karl for all his work in maintaining Zephyr 
for the last few years (the 3.0 release, in particular, comes to mind). As a 
happy user of Zephyr I'm indebted to his work in keeping it running and honored 
to be helping with its development.

-- 
Geoffrey Thomas
https://ldpreload.com
geofft@ldpreload.com

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