Index: [thread] [date] [subject] [author]
  From: Steffen Seeger <s.seeger@physik.tu-chemnitz.de>
  To  : ggi-develop@eskimo.com
  Date: Tue, 2 Feb 1999 11:19:46 +0100 (MET)

Re: Mailing lists

> On Mon, 1 Feb 1999, Marcus Sundberg wrote:
> 
> > Stefan Mars wrote:
> > > 
> > > > > Could we please split this mailing list now. Traffic is now back on
> > > > > the levels it was on a year ago, and still increasing. But most of
> > > > > it is quite unrelated to GGI development.
> > > 
> > > Last time we did such a fork traffic after that (3D) dropped to almost
> > > nothing, and so the 3d list was closed. Do we really have enough traffic
> > > to warrant _4_ new lists?
> > 
> > Well, maybe 4 lists are still a little overkill.
> > But at least we should have one list concerning development of our
> > core components LibGII/LibGGI/KGI, and one "ggi-misc" list.
> 
> 	Yeah.  Now we have LibGGI2D, LibGGI3D, LibGWT, LibGIC, and the
> SVGALib wrapper.  As I said six months ago, the GGI project needs to split
> up.  Your split would divide everything into low-level and high-level
> halves, which seems natural to me.
> 
> > Other lists can then be forked of ggi-misc as neccesary.
> 
> 	I'm for it.  Anyone else?

I think a split into kernel/library development would take of the most
load from people that need/want to work on kernel stuff only (at the moment).

As this would imply that we don't subscribe generally to the 'other' list(s),
I would suggest to have a ggi-develop (as usual) and a kgi-develop, 
mainly about driver/internal stuff. But, we sould name two persons responsible
to post a summary once a week from each 'other' list. I think this is neccessary
not to loose contact... However, doesn't seem too practical to me.

> Jon 

			Steffen

----------------- e-mail: seeger@physik.tu-chemnitz.de -----------------

Index: [thread] [date] [subject] [author]