LYNX-DEV I'm back + Re: Lynx development process (fwd)

[Klaus Weide]

Re-sending this message, now that I am subscribed correctly:

---------- Forwarded message ----------
Date: Sat, 5 Jul 1997 16:36:13 -0500 (CDT)
From: Klaus Weide <address@hidden>
To: address@hidden
Subject: I'm back + Re: Lynx development process

Hello lynx-devvers,

1. I'm back, after some enitirely net-less weeks (longer than
expected).  Sorry for the confusion and concern this may have
caused.

I'll have (maybe much) less time to spend for lynx dev then for some
time, but will try to continue working for lynx (and the development
code).  Right now I am still trying to catch up on what I have missed.
I notice, from browsing through my mailbox, that quite a few things
have happened...

On Sun, 29 Jun 1997, Bela Lubkin wrote:
> Michael Sokolov wrote:
> 
> >    I propose that the Lynx development process be made a bit more formal.
> 
> Mike Brown replied:
> 
> > No one is going to argue with that, but from what I have seen, no one
> 
> I beg to differ.  I think the process works fine the way it is.  Wasting
> people's energies on formalizing the process will only reduce the amount
> of actual development that occurs.
> 
> Yes, the Lynx development process is anarchic.  So what: the results are
> good.
> 
> All that's needed is a "code collector" -- formerly Fote, then Klaus for
> a while, now perhaps Fote is drifting back into that role, or maybe
> someone else will.  I am confident that *someone* will.  And if not, why
> would anyone imagine that a set of formal rules would have changed that?

I certainly don't want to be the sole "code collector".  But let's
focus more on the "collection" than the "collector" - the "development
code" set maintained on sol.slcc.edu.  Several people can directly
update it (currently Tom, Jim, Wayne, Scott, and me).  So if one
contributor does less, the others are still there to "collect" new
code; and this is more or less what has happened or is happening (with
Jim's updates, and Tom working on combining Fotemods with the devel
code).

In the hypothetical event that development of this development code
should stop or not keep up, people will start regarding other code
sets as "the" development code and look to some other group or person
as the "collector".  Or more contributors will join the number of
those updating the current "development code".

   Klaus


;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;