mechjgh@tness7.UUCP (Greg Hackney ) (06/16/88)
This is a call for votes to elect the official Elm Coordinator for future releases of Elm and bug fixes. (David Taylor of HP has resigned from this position.) All readers of comp.mail.elm and users of Elm are encouraged to vote. Please choose 1 name from the following list of people who volunteered as a result of a call for volunteers posted in comp.mail.elm: Eric Christensen - Altos Computer Systems ---------------- San Jose, CA edc@altnet.altos.com Steven Donegan - Western Digital Corp. -------------- Irvine, CA. donegan@stanton.TCC.COM Brian O'Neill - Wang Institute of Boston University ------------- Tyngsboro, MA oneill@bu-tyng.UUCP Syd Weinstein - Datacomp Systems Inc. ------------- Huntington Valley, PA syd@dsinc.UUCP Please email your vote to me. DO NOT post your vote to the net. (Unless you just want to.) -- Greg Hackney (214+464-2771) Southwestern Bell Telephone Co. root@tness7.UUCP --<some possible paths to me>-- ihnp4!tness7!root rutgers!bellcore!tness7!root gatech!petro!tness7!root cbosgd!killer!tness7!root codas!killer!tness7!root sun!texsun!rpp386!tness7!root ucbvax!ihnp4!tness7!root
rjg@sialis.mn.org (Robert J. Granvin) (06/16/88)
In article <3189@tness7.UUCP> mechjgh@tness7.UUCP (Greg Hackney ) writes: > >This is a call for votes to elect the official Elm >Coordinator for future releases of Elm and bug fixes. >(David Taylor of HP has resigned from this position.) > >All readers of comp.mail.elm and users of Elm are >encouraged to vote. > >Please choose 1 name from the following list of people >who volunteered as a result of a call for volunteers >posted in comp.mail.elm: Whoa...! Wait a sec... It's entirely possible that I have missed some postings or items of importance in previous messages, but I personally will refuse to vote for anyone until I know something about the "candidates". What qualifications do each of these gentlemen have? How much time and effort will they be able to guarantee to the coordination of elm? Why should I vote for one and not another? Even if this has been hashed out in the past (faithful reader here, but not perfect :-), this type of information should still be included in the message requesting votes. My only criteria today is voting for someone whose name I like, or maybe because I like the company. Not good criteria for something of this nature... (No offense intended to the individuals involved... I'm sure they may all be qualified, but someone should still say why...) -- "I've been trying for some time to Robert J. Granvin develop a life-style that doesn't National Information Systems, Inc. require my presence." rjg@sialis.mn.org -Garry Trudeau ...{{amdahl,hpda}!bungia,rosevax}!sialis!rjg
hack@bellboy.UUCP (Greg Hackney) (06/18/88)
In article <568@sialis.mn.org> rjg@sialis.mn.org (Robert J. Granvin) writes: >In article <3189@tness7.UUCP> mechjgh@tness7.UUCP (Greg Hackney ) writes: >>This is a call for votes to elect the official Elm >>Coordinator >Whoa...! Wait a sec... >It's entirely possible that I have missed some postings or items of >importance in previous messages, but I personally will refuse to vote >for anyone until I know something about the "candidates". What >qualifications do each of these gentlemen have? How much time and >effort will they be able to guarantee to the coordination of elm? Why >should I vote for one and not another? 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. Otherwise, I would suggest that a voter judge the candidates by their previous postings. -- Greg
syd@dsinc.UUCP (Syd Weinstein) (06/18/88)
In article <568@sialis.mn.org> rjg@sialis.mn.org (Robert J. Granvin) writes: >In article <3189@tness7.UUCP> mechjgh@tness7.UUCP (Greg Hackney ) writes: >> >>This is a call for votes to elect the official Elm >>Coordinator for future releases of Elm and bug fixes. > >(No offense intended to the individuals involved... I'm sure they may >all be qualified, but someone should still say why...) OK, folks here goes with my qualifications. I suggest each of the other three to do likewise. I am the owner of Datacomp Systems, Inc. a Unix software development and testing house that has been developing under Unix since 1979. We currently do systems testing and kernel development for several Unix OEM's. We have been using elm since 1.5 and have made many changes to it for local needs. We have a site that is relatively well connected, as well as supporting anon uucp on TB+'s. We have, currently at least, disk space to spare for a while (two spare drives even) on our backbone node in our local net. We run Unix V.2 and V.3 locally. We are used to supporting large distributed development projects. One of which we have been managing for 11 years is the Medicare Reimbursement System, and that is about 50MB of C source code. we have been using Source Code Librarians from back in my CDC 6600 days of 1973 and do use SCCS extensively for our in house projects. As for time committments, I am willing to devote the time to elm, However, I cannot state that I always will be able to do so. All I can promise is that I will pass the baton when I find I cannot support it. Does that help? I have made various policy statements in previous discussions with Greg, these include: 1. The coordinator will have to be a moderator of sorts, deciding what features get into the new elm, as some features are bound to conflict with some others and some might not be universally desirable. (In fact the corrdinator might have to ifdef some features to allow for smaller systems and size or for local choice of conflicts) 2. I guess the coordinator will have to keep two copies of elm. Their local copy for their system and a master copy without their local mods that is not localized. 3. It would help if the coordinator kept annon uucp for the full system or even ftp if so connected. But a archive server like the alt.gourmand one for patches to distribute bug fixes and new features would be useful. 4. I don't think posting patches is the best way. I feel we need some minor control, such as was used for the Perl Patches. Using a coordinator to send out official patches would prevent some conflicting ones from going out. I can see simple workarounds being posted, but real patches should come from some central source. 5. I do believe in sending out patchs, not just releases. The dist package for patches should be used. Also branch sccs id's for patch revs vs development revs should be used. -- ===================================================================== Sydney S. Weinstein, CDP, CCP Datacomp Systems, Inc. Voice: (215) 947-9900 {allegra,bellcore,bpa,vu-vlsi}!dsinc!syd FAX: (215) 938-0235
boneill@hawk.ulowell.edu (SoftXc Coordinator) (06/18/88)
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. > Well, here it goes... I'm currently a system operator for Wang Institute of Boston University and a student at the University of Lowell. At WIBU, I use an Encore Multimax, which allows me to run things a little quicker than usual, as it is seldom bogged down. At the moment, news and mail are somewhat slow, but we're working on it. It runs UMAX 4.2, a BSD 4.2 equivalent. At ULowell, I have access to A Sequent Balance 21000 (Dynix 2.1.2), Vax 11/780 (I think) (BSD4.3), and a Data General MV10000 (DG/UX). Although I'm not a system operator there, I usually pass the stuff along to the operators, one of which (Warren Lavallee) has volunteered as a tester. Also, ULowell is much better connected. I can get news and mail in and out much faster (that's why I'm sending from there now) and can provide anonymous ftp of Elm. Also, I can send the files through a semi-automatic file server which receives requests and send files via e-mail. I plan to do most of the work at WIBU, as I can fully test everything there, but they do not have SCCS. They do have RCS, and I'm reading the documentation on using it. Here's my thoughts on the Coordinator: 1) Would release 'official' patches, after fully tested by the volunteers, and suggestions on improving them made. 2) Further coordinate full upgrades with the testers for future releases. 3) Once 2.0g is fully debugged and everyone is satisfied, make an "official" release (2.01???) to comp.sources.unix. 4) Anything else people come up with in comp.mail.elm, or changes to the above, if agreed upon, are certainly welcome. ============================================================================ Brian O'Neill, MS-DOS Software Exchange Coordinator ArpaNet: boneill@hawk.ulowell.edu UUCP : {(backbones),harvard,rutgers,et. al.}!ulowell!hawk!boneill
donegan@stanton.TCC.COM (Steven P. Donegan) (06/20/88)
In article <1101@bellboy.UUCP>, hack@bellboy.UUCP (Greg Hackney) writes: > In article <568@sialis.mn.org> rjg@sialis.mn.org (Robert J. Granvin) writes: > >In article <3189@tness7.UUCP> mechjgh@tness7.UUCP (Greg Hackney ) writes: > >>This is a call for votes to elect the official Elm > >>Coordinator > > >Whoa...! Wait a sec... > >It's entirely possible that I have missed some postings or items of > >importance in previous messages, but I personally will refuse to vote > >for anyone until I know something about the "candidates". What > >qualifications do each of these gentlemen have? How much time and > >effort will they be able to guarantee to the coordination of elm? Why > >should I vote for one and not another? > > 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. > > Otherwise, I would suggest that a voter judge the candidates by their > previous postings. > > -- > Greg Well: I am 31 years old. Currently working for Western Digital as Sr. Telecommunications Analyst. (5 yrs) Own Stanton Public Domain Systems, a consulting firm which runs the stanton! system and provides public access unix and XBBS BBS access. I am a C, Fortran, SPL (HP) and Assembler(various) programmer. Other various and sundry hobbies etc: racing, electronics, motorcycling I am willing and able to provide access to any software via uucp access, shortly both X.25 (Telenet/Infonet) access and FTP access will be added (FTP if AT&T doesn't mind the add'l traffic on their net). And, of course, uucp access via PC-PURSUIT. I am an unofficial archive site for all the UNIX sources from the news, minix, GNU etc. The stanton! system is a NOVAS 16mhz 0 wait state 80286 system (Norton 18.7, dhrystones in the 3k range, whetstones in the 340k range) tower system, home built, with 6 megs of RAM and 160 meg of fast HD. Media compatability includes 360, 720, 1.2 meg 5 1/4 inch floppy, 720/1.44 3 inch floppy, DC600A tape (soon) and 800/1600/3200 BPI full size mag tape (QUALSTAR system). I would like to serve as a beta site, a self-serve (check-out/in) style project coordinator, archive site or whatever for the elm 2.0/1.7 project. I am normally on the road or working very long hours so voice contact would be less available. My voice mail number is 714-474-2033 x7998, unix uucp addr is either root@stanton.TCC.COM or donegan@stanton.TCC.COM -- Steven P. Donegan Sr. Telecommunications Analyst Western Digital Corp. donegan@stanton.TCC.COM
donegan@stanton.TCC.COM (Steven P. Donegan) (06/20/88)
I would like to sugest that all elm coordinator candidates join together, make a team effort, and work on elm. There should be a primary coordinator (such as the current vote is vectored towards), but multiple interested parties could do elm coordination. Let's rally around the elected candidate and form a group that will make elm a better system. My .02$ worth...:-) -- Steven P. Donegan Sr. Telecommunications Analyst Western Digital Corp. donegan@stanton.TCC.COM
edc@ALTOS.COM (Eric Christensen) (06/20/88)
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 | +-----------------------------------------------------------------------------+