Q: Why create this page?
A: The life blood of every Open Source Project is its Community. Communities are made up of people willing to devote some of their time, creativity and energy to the project. But a Community is more than just a set of people. There is a social aspect, and people like to know that they have company. So let us know who you are.
The first step is simply saying to yourself: I want to help.
Placing yourself on this page has no meaning other than to let people know that you exist, what your interests are, and how you might like to help.
Welcome to James.
Noel J. Bergman - James Committer. Interested in helping James become a robust, scalable, enterprise-class messaging server. Primary area of interest: infrastructure.
Sergei Sozonoff - James volunteer. I like the concept of Mailets a lot and I would like to help James continue to develop. My main interest is in Mailets until my Java knowledge reaches a point where I can contribute in other areas. I am hoping to use James in several projects.
Danny Angus. - James commiter, I turned up one day looking for a mail server and got hooked. Interests? I think email is the coolest invention, particularly MIME, SMTP, MailetAPI, and to a lesser extent Icalendar and Vcard.
Kenny Smith - Earnest Newbie who finds it hard to find time to contribute. I needed an extensible mail server and found James. I've been wanting to contribute to Jakarta and I really think James is an excellent project.
Steve Short - James user and occasional contributor. Interested in pipeline processing, JMX, performance, directory integration, message personalization.
StephenMcConnell - { { { James/Avalon } } } liason. Working on the integration of the James mail services and related components within an advanced container platform - AvalonMerlin.
Leo A. D'Angelo - Interested in enhancing James to support encryption/decryption as well as spam management and message filtering. At some point I would like to play with james as a personal mail "proxy" for personal message management as well.
Christian Myrvold - Have a mailsystem at home in use by family and friends. Came across JAMES when looking for the right mailserver, but because of the lack of IMAP I'm currently using a different server for my "live" system. I need IMAP, so that would be the area of my most interest when it comes to contributing.
Jason Webb - Developer of high-volume MLM solutions with James. We use James as a mail server to "front" our MLM code. My interest is turning James into a high-volume, attack-resistant mail system
Peter Svensson - Using James at home and for enterprise application. Interested in contributing to open source and I hope to help with the next release of JAMES. Trying to get IMAP into JAMES.
Sivasundaram Umapathy - Using James at office for the past 6 months.Interested in contributing to open source.Working as a J2EE developer.Had done a good deal of SMTP/POP programming at my college days and also at work.Hoping to join hands with the JAMES community for the next release
Serge Knystautas - James committer. I originally donated the code and help put together the mailet API we have now. Have been running James in production since 1999 and want to see it replace sendmail and maybe even Exchange. I'm the current PMC (Project Management Committee) Chairman for James.
Aaron Knauf - James ponderer. I use James behind sendmail as a way to process incoming email from Java, rather than as the MX for a domain. I have developed mailets that serve as part of the mobile network infrastructure for a major telco. Interested in extending James to make it more sophisticated and useful in this role.
Steven Smith - Sendmail convert - Dynamic Anti-Virus integration and implimentation with per-user/per-domain rules and server-side 'access' rules. RDBMS (PG7.3.1) based message store with triggers.
Fred Bloomhanasaki email. Would be happy to team up with one, or more, to work on IMAPS and LDAP/JNDI related activities. Also interested in mabye being the understudy to someone already well versed in James APIs to work on migration tools.
Mark Imel - James user/volunteer and interested in contributing to the James project. Specifically, as it relates to List Management.
Michael Percy - Free Software enthusiast. Interested in taking IMAP and LDAP in James to a world-class level, and replacing Exchange with a Free Software equivalent. Main concerns: having a full-featured product, wide compatibility, and ease of administration.