Lynx2-3-9 BETA:
===============

	This archive contains the Lynx source set with bug fixes
and enhancements as implemented at the WFEB.  Read the CHANGES
file for a description of the modifications through the date of
this archive.  Thereafter, check the CHANGES file in:

	  http://sci.wfeb.edu/dir/lynx
or:	gopher://sci.wfeb.edu/11/_fileserv/_lynx

for any further bug fixes or enhancements.

	This distribution contains all the files for building Lynx with
all flavors of Unix and on VMS with VAXC/VAX, DECC/VAX or DECC/AXP, and
the associated documentation and example files.

	It is not an "official" Lynx distribution, i.e., it might not be
incorporated into the code distributed by the University of Kansas.  Read
the appended messages from Michael Grobe and Jeff Porter, and contact them
if you have any questions concerning their plans for Lynx development.

	Whether or not this code is incorporated into the "official" Lynx
distribution, it is encompassed by the University of Kansas copyright on
Lynx and the CERN copyright on the Common Library (WWWLib).

	Report bugs to:  lynx-dev@ukanaix.cc.ukans.edu.

	Request general help from:  lynx-help@ukanaix.cc.ukans.edu

				Fote

=========================================================================
 Foteos Macrides           Worcester Foundation for Experimental Biology
 MACRIDES@SCI.WFEB.EDU     222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================


From:   IN%"lynx-dev@ukanaix.cc.ukans.edu" 28-OCT-1994
Subj:   RE: Is Lynx dead?                  ^^^^^^^^^^^

KU has absolutely no plans to "kill lynx".

lynx is alive and well, recovering from a period of partial catatonia.

we have hired a full-time programmer and 2 part-time students to
keep lynx alive and upgrade it as the web evolves.  the full-time
person is jeff porter, who started this month and is busy acclimating.
jeff and i both attended the developer's conference in chicago.

the issue of whether or not we have to license is not determined
yet.  i continute to want to avoid licensing, and i continue to face
funding problems, so licensing continues to hold some allure.

i hope that helps clarify what is going on.

:michael grobe

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                            Michael Grobe
Manager                                  Director
Distributed Computing Support            Kansas Research and Education
Academic Computing Services                  Network    (KANREN)
                         The University of Kansas
                            Lawrence, KS 66045
                              (913) 864-0452
			grobe@ukanaix.cc.ukans.edu

==============================================================================


From:   IN%"lynx-dev@ukanaix.cc.ukans.edu" 24-FEB-1995
Subj:   RE: lynx development (longish)     ^^^^^^^^^^^

> > From: d-lewart@uiuc.edu (Daniel S. Lewart)
> > Lynx-Dev,
> > 
> > 5) Is `lynx' development based at UKans or at WFEB now?

Thank you for the input and the questions.  I believe the first four 
comments have been addressed, but please notify me if they require 
further discussion.  I would like to address the last question you asked.
Lynx development is, and always has been, based at the University of 
Kansas.  Before I took the lynx development position here, just about 
everyone involved in lynx development left to engage in other pursuits.  
Fortunately, many of the people on this list have been involved with lynx 
development, some from nearly the beginning of the project.  Many of you 
continue to provide specific fixes and new features.  Lynx would not be 
the program that it is without the great work that the people on this 
list have contributed.

I think that there comes a time in any large project to take a serious 
look at the way the code has "grown" over the years and do some 
re-engineering.  It's important to add new features and provide quick 
fixes, but it is also important to strengthen the foundation.  This will 
improve everything built on top of it.  The downside is that it takes 
longer for this kind of development to reach the users.

Rest assured that lynx development is ongoing at KU and there is no 
reason to believe that it will not continue.  In fact, we have plans to 
increase the staff time devoted to it.  Now is a good time to look beyond 
simple fixes and do some more fundamental development.  I believe that 
the efforts made to improve the structure of the code and it operation 
will make future development much more efficient and enjoyable.

As always, your comments are welcome.  I am very interested in ways you 
think that lynx can be improved.  There is no need to limit your ideas to 
things that would be easy to accomplish.  I want to make lynx a better 
tool, and sometimes that requires larger shifts in capabilities.

Thanks,
Jeff

--
Jeff Porter - Distributed Applications Programmer
Computing Services - University of Kansas
email: jporter@stat1.cc.ukans.edu
phone: 913-864-0460

==============================================================================

