> > > Is it time to create an ogml-advocacy list that intended for rather
> > > noisier discussions?

A list called advocacy should be about just that, advocacy.  Aka public
relations, evangelism, marketing.

I think we need to go *up* a level, and have an open hardware mailing
list.  This would be a place to discuss SMP/NUMA, DSP, SATA, Ethernet,
Hypertransport, audio, DRM, etc.  If a specific topic gets sufficient
sustained traffic, or if a group wants to escape the chatter of the
general group, a focused mailing list can be split off.

The open-graphics list could then concentrate on graphics.

But even within graphics we have

        OGD  (FPGA board)

        OGA  arch (e.g. CPU instruction set and assembler)

        TRV10 ASIC

        OGC (TRV10 ASIC board)

        external Ethernet graphics/video/X11 box

        general graphics questions and discussion

So perhaps

        open-hardware
        open-graphics           (general)
        open-graphics-ogd
        open-graphics-oga
        open-graphics-trv10
        open-graphics-ogc
        open-graphics-oge

If that is too many lists, perhaps

        open-hardware
        open-graphics           (general)
        open-graphics-ogd
        open-graphics-ogc       (including oga and trv10)
        open-graphics-oge

I suspect that some of you are thinking that this is still too many lists.
More work for the maintainer to create all those new lists, more work to
subscribe to all those new lists, etc.  But Usenet has taught us that
having fine control over topics is very useful.  Someone may be interested
in the FPGA board but not at all interested in the ASIC, or visa-versa.
Same for an expansion card vs. an external box.  A developer might be
interested in all of them, but wants to concentrate on the topic they
are working on and automagically file the rest in a folder to be read later.
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)

Reply via email to