Path: utzoo!attcan!uunet!altnet!edc From: edc@ALTOS.COM (Eric Christensen) Newsgroups: comp.mail.elm Subject: Re: A Call For Votes [REPOST] Keywords: Here's my brag sheet Message-ID: <486@altnet.ALTOS.COM> Date: 20 Jun 88 16:56:25 GMT References: <3189@tness7.UUCP> <568@sialis.mn.org> <1101@bellboy.UUCP> Reply-To: edc@altnet.ALTOS.COM (Eric Christensen) Organization: Altos Computer Systems, San Jose, CA. Lines: 106 In article <1101@bellboy.UUCP> hack@bellboy.UUCP (Greg Hackney) writes: > >If you 4 candidates would like to post something about yourselves, >i.e. Elm experience, background, etc., it would certainly be appropriate. >In fact, a couple of people has asked for this. Alright, due to popular demand, here's my "brag sheet": I am currently employed by Altos Computer Systems in the Sillycon Valley Gulch as a Software Service Engineer. My main responsability is sustaining engineering on our Unix and Xenix operating systems. I addition I coordinate all custom contract programming. I have be involved with Elm since 1.5 and have ported it to about 30 different systems in that time. At present, I have Elm running on Altos' corporate network which consists of about 600 users on 40 some systems in 9 contries. As a result, I have a vested interest in the continuation of the Elm project. I have actually been working with IPMS (Interpersonal Messaging Systems) for about 5 years now. I have written 4 full mail user agents, 7 delivery agents, and have implemented transport agents (mostly SMTP and X.400) in a variety of network environments. My latest project is ITFM; an Integrated Telex, Fax and Electronic Mail system. While this project is purely experimental at this point (read "blue sky pipe dream"), the technology which my partner and I have developed is currently in the initial stages of implementation into a full service messaging system. (BTW, we used Elm as a "base user agent" for most of the early development of the transport protocol.) I am experienced in managing large, distributed development projects, and run both RCS and SCCS source trees for various sustaining and development projects. In addition, I have done considerable work in the areas of remote system diagnostics and remote software maintenance (my senior project, many years ago, was entitled "RSMS - A Dial-up Remote Software Maintenance System Under RSX-11"). Ok, enough bragging about what I have done in the past, as far as what I can do for Elm now.... 1) I can provide anonymous uucp for a fully RCS'd and/or SCCS'd version of the Elm sources. 2) I can provide a limited number of people (i.e. the primary developers) access to my system via X.25 (Tymnet or Infonet), for the purposes of source tree access and such. I can also take a limited number of uucp links (sorry no news feeds) via these X.25 lines. I pay the bills on the X.25, so I won't just give it to anybody who asks though. Only significant contributers to the Elm project. (BTW, you folks overseas who have PDN connections can anonymous uucp via the X.25, but you'll pay the bill.) 3) I believe that it is VERY important to have the sources under full version control, especially with several people working on them in remote locations. This makes it very easy to tell where and when changes were made and greatly simplifies the ordeal of incorporating patches and enhancements to the master sources. Under RCS control, it's easy to tell exactly what version of source code the change was made to, so that the changes are applied in correct order. This has been a problem that I have fought with in the past on 2 other distributed development / sustaining projects. While I don't claim to have all the answers on this subject, I do have enough "hard knocks" experience to maintain the source tree correctly and efficently. 4) I will set up and maintain a mailing list for the Elm developers and testers to allow us to communicate directly with each other without cluttering up comp.mail.elm with rubbish that nobody else really cares about. This would also allow me to distribute "official" patches to the testers a few days before posting them to the net (just as a safety precaution to ensure that I'm not brain damaged). 5) I support the opne posting of "unofficial" patches to comp.mail.elm. This would allow users who are willing to / need to take the chance with these "unofficial" patches the ability to do so. Of course, official patches will be released to comp.sources.unix once they are tested and added to the source tree. I believe that official patches should not be unduly delayed. I prefer to release official patches in groups on a regular basis (i.e. every 2 weeks). If a very important patch is implemented, it should be posted within 1 week. I don't believe that any patch should be delayed more than 2 weeks. 6) I am very concerned with the "internationalization" of Elm. I am very interested in replaceing the crypt call with a PD version. In addition, I am interested in producing foriegn language translation kits for Elm. 7) I am more than willing, and cretainly able to devote the time required to coordinate the Elm project. I am very fortunate, in that my employer fully supports my involvement in the project, and has been more than gracious about letting me spend time working on it. They have assured me continued support (as long as I keep their network and messaging systems running). What the heck, it sure beats "working" for a living. I welcome your comments on the precedeing platform. Your tax-deductable contributions may be sent to: SAVE THE MAILERS, WASHINGTON D.C., 60609 :-) Don't flame me!!!! It's a joke!!! Only a joke!!! And I'm NOT J.J., or a J.J. impersonator!!!! -- +-------------------------+---------------------------------------------------+ | Eric D. Christensen | Email: edc@altnet.altos.com (uunet!altnet!edc) | | Altos Computer Systems +---------------------------------------------------+ | 399 West Trimble Road | Definitions: Bug - An Undocumented Feature | | San Jose, Ca. 95131 | Feature - A Documented Bug | +-------------------------+---------------------------------------------------+ | These views aren't Altos' - They're mine, all mine, and you can't have them | +-----------------------------------------------------------------------------+