Zap Documentation      Latest release     
ZapRedraw      Contact      Download     

Zap contact details

We prefer to be contacted via email; if you really need to write to us, write to James at the address given below.

General email addresses

Note that the following are mailing lists. For information on how to subscribe to the lists, see the Zap mailing lists page. Before reporting a bug or suggesting a feature, try to make sure it hasn't already been reported/proposed (this is difficult until we collate the lists of each).

zap-users@zap.tartarus.org
All bugs reports, non-technical queries or suggestions should be sent here
zap-technical@zap.tartarus.org
For technical queries and discussions.

In addition, the usual 'master' addresses exist for the Zap domain: webmaster@zap.tartarus.org, hostmaster@zap.tartarus.org and postmaster@zap.tartarus.org. In addition, listmaster@zap.tartarus.org runs the mailing lists.

Maintainers

Principal maintainers

'Emeritus' :-)


Darren Salt

Darren maintains ZapEmail, ZapDS and sometimes ZapBASIC. In the core, he is responsible (amongst other things) for the command language, ClickSend, menus, internationalisation, and mode handling (including clone modes). He's also responsible for ZapRedraw's Viewfinder support.

ds@zap.tartarus.org

James Aylett

James maintains ZapFonts, the combined command extensions (although, to some extent, this is a shared responsibility), the 'glue' (documentation, web and ftp sites, domain, mailing lists), and an air of omniscience. He is also responsible (amongst other things) for c-vars and the general shape of the distribution.

dj@zap.tartarus.org

Christian Ludlam

Christian maintains ZapRedraw and is responsible for driving that in the direction it's going. In Zap proper he fritters his time away fixing bugs, dreaming up wonderful ideas for the future, and correcting James' mistakes.

christian@zap.tartarus.org

Tim Tyler

Tim did lots of the work on v1.40, including coordinating its release. He also wrote vast numbers of syntax colouring modes, and maintained Martin's programming modes. Since v1.40 Tim has decided to try to use his time more wisely (:-), and avoid getting dragged into Zap too much.

Justin Fletcher

Justin is responsible for enhancing Code mode beyond common sense, and a few other things. He's currently suffering from lack of time to devote to Zap (if 'suffering' is really the right word).

Dominic Symes

Dominic was the initial developer of Zap, and its sole maintainer until the end of 1996.

Martin Ebourne

Martin wrote the C, C++, Java, Assembler and Pascal modes which form much of the use of Zap (at least by its current developers). He also wrote the plug and play auto-configuration system we've been using since v1.40.


© Copyright Zap Developers 1992-2008. All rights reserved.
Updated: 2007/10/21 14:08:16. webmaster@zap.tartarus.org
Valid HTML 4.01!