Re: TK Added Value Items - Take 2

Need to preface this with a disclaimer.  My comments below may wander a bit and may not even make a specific point.  Somewhere this week I lost a day, don't know where it went but it's gone.


> cedarlakebuzzards wrote:

> > halfmeg wrote:

> > So I guess, after all this musing, my questions are:

> > 1.  Should and/or how would a single repository for software added
> > to TK exist?

> Having worked in the capacity of being a "code cop" for application
> code, I found the idea of a single code repository, in theory, an
> excellent idea.  In practice, the repository is hard to implement.

Yes, we have numerous file areas:

Yahoo Groups file areas
CBT Tape
Ibibilio
Sourceforge
many individual's web pages

There are also the different models as to how projects are developed.  From http://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar

" The Cathedral model, in which source code is available with each software release, but code developed between releases is restricted to an exclusive group of software developers."

" The Bazaar model, in which the code is developed over the Internet in view of the public. Raymond credits Linus Torvalds, leader of the Linux kernel project, as the inventor of this process."

TK and it's added items seem to fit more with the Cathedral model even though several people may work on something.

Sometimes things disappear when there is only one or a small group working on a project.

Some disappearing sites which from time to time someone wishes they had something from:

http://www.shedlock.org/
http://www.vm-370.com/
http://www.homerow.net/hax/
http://www.kiyoinc.com/herc390.html
http://pweb.uunet.de/schwarzer.d/projects/hercules/
http://www.schaefernet.de/hercules

And there are other sites which are still around but difficult to remember ( for me anyway ) like :

http://www.webring.com/hub?ring=dinos  which has many dino sites 
http://www.mvsdasd.org/
http://www.mountaindesigns.com/jcc/
http://www.lightlink.com/mhp/3705/

Some stuff is simply not available anymore.  Some is stuffed away after a download but not readily remembered as to file name or where.  DL/I was a recent example.  Both the tape and documentation were gone from the web.  Both now available but in different places I think.

> > 2.  Should items like the Compiler Pack be incorporated into a TK
> > CD ?

> Yes.

The slight problem with this is the same with many items, they get modified or updated while the TK distribution remains static.

RPF was updated several times since the TK3 CD was created.  Mike has reservations about permitting inclusion of KICKS which is understandable as it is in the 'toddler' stage of life.  I haven't been able to keep up with where GCCMVS and BREXX have progressed, but would like to include them along with (B)REXX utilities that have been developed but not released (TSO COPY ? ).

Independent DASD which can be attached to the system may be a good solution for somewhat complex additions like the Compiler Pack or GCCMVS and friends which may change frequently.  I don't know about the complexity of KICKS as I haven't downloaded it.  Since it 'touches' several system datasets, it is at the very least important to backup your system before installation.

Smaller additions, such as RPF, JRP or  have different install methods.  RPF uses a jcl stream and a tape and pretty much is done.  JRP is packaged in a XMIT and may require password entries into the source code for restricted access and parm modification depending upon whether you want a WTO issued or not.  RPF is also in xmit form if obtained from CBT Tape site.
 
> > 3.  Should a minimal TK (1) be available for quick download for
> > trial and the 'CD' have the kit and kaboodle ?

> I would like to suggest "packages", each depending on the previous 

>     1. base operating system ("vanilla" as delivered by IBM)

With PTFs or without ?
With UserMODS like 3390 support or without ?
Greg Price TSO addition MODs ?

RAKF ?


>     2. utilities (other than those include in the above).

REVIEW, DSAT, FSE, RPF, DSSREST/DSSDUMP ( an CBT ? )

>     3. development tools (i.e. compiler pack)

Was thinking of dropping compilers in TK4 if favor of Compiler Pack.  This would mean only IFOX available to do any programming with until Compiler Pack installed.

>     4. applications

Hmmmm, what applications are folks running ?  What is available ?

> > 4.  Who's going to write the documentation?

> Unfortunately, most techies I know (including me) don't like writing
> documentation.

One reason we are sticking with some things is they remain aligned with Volker's web pages and cookbook.

Phil