Codename G-OS

["Lazy Bone" <zhulien@alphalink.com.au>]

Hi All on the Codename G-OS mailing list.  

Thanks
======

Firstly I would like to thank all who responded to the original email and
newspostings, the responses have been both positive and in great number.  In
addition to that many people made positive suggestions regarding the project.


Codename G-OS needs a Name
==========================

Codename G-OS needs a name, I had one email stating how similar the name
'Codename G-OS' was to 'GEOS' on the Commodore 64.  Although for several
reasons, I would like to disagree (ie: our name has 4 sillables, GEOS has 2) 
I think a better name could be given, perhaps GENOS?  Then an Integrated
Development Environment could be called GENOSIDE :)


A couple of people also made me aware of their concern regarding the slowness
of a JIT compiler on an 8 bit computer.  Firstly, the JIT compiler would NOT
be JAVA based, but could have some parallels - ie: being JIT.  Also, it is
likely that the system would be created around a Virtual Machine with a
Virtual Machine Language (VML) that would be designed specifically to execute
reasonably fast on an 8 bit computer if interpreted and maximum speed when
compiled.  Even interpreted BASIC is reasonable on some systems and when
compiled, very quick.  One great idea from one of you who emailed me was to
have the compilation part of application installation so most users wouldn't
even be aware it was happening - personally I like the idea.


Programmers needed
==================

Programmers are needed for a project of this scope.  At this stage, a list of
possible developers is being created.  

It currently looks like this:


   Wen Carkner         6502/Commodore 64
   Luke Adams          6502/BBC Model B
   MagerValp           6809/Tandy CoCo
   Xavier Urton        z80/Amstrad CPC
   Julian Cassin       z80/Amstrad CPC (AMSDOS & CP/M)


Other non-programmers
=====================

Although many people would consider themselves non-programmers, they are not
at all useless for this project - Other useful things people can do are supply
IDEAS, BETA-TESTING etc...


To be or Not to be - Commercial that is
=======================================

The 'commercial' concept I outlined previously had a few critisms.  This is
good to have feedback, but here is the reasoning behind the suggestion of
being commercial.

To be commercial has the following benefits:

-  The product will controlled centrally (in concept) by a SINGLE development
group.
-  Full legal control over other commercial product spinoffs.
-  Full legal control over incompatible spinoff versions.
-  The product will be supported by both individuals AND commercial
organisations.
-  An Individual developer will have EXACTLY EQUAL rights as all others
including
   organisations.
-  It seems that commercial has better reputations over freeware and shareware
as far
   as Enterprises are concerned.  Who runs companies of a Public Domain OS?
-  ALL source code will be delivered WITH the OS so every man and his dog can 
   customise it.  Do you like the way the OS looks? Everyone has their own    
   opinions.  The public can suggest better code to the developers.
-  We can promote the OS in the same way as other organisations.  ie:
Advertising?

Of course this means a contract should be written out sometime that EVERY
developer gets - the same EQUAL contract for everyone.

The only downside is the Fred cannot legally give Barney a copy, but Barney
can himself get a FREE copy from somewhere (ie: the web, email, snailmail).


Development Coordination
========================

To coordinate the development of this project, because it is both
international AND multiplatform, several resources will be necessary.

WWW   - This will be used for general/technical/progress information and
advertising.
      - Also ALL current source code/related utilities will be available from
here.
EMAIL - More up to date communication amongst developers.
FAX   - People can FAX information to anyone with a FAX machine.
NEWS  - General updates for everyone, and to attract newcomers.


Where will we start?
====================

Well, we are starting now...

1. Initially, a plan will be drawn up - anyone interested in playing a role in
the 
   project should email me and let me know what they can do for the project.

2. All developers will be asked to communicate and come to agreement on what
the OS will
   do, how we will implement it etc...

3. Design phase.

4. Implementation phase.

5. Testing phase.


Of course this is a very basic outline at this stage, but it will surely
progress.


Regards



Julian Cassin
(Director - Computer Kingdom Pty Ltd)