[hyades-dev] Communicating with and within the Hyades Project

[Michael.Norman@xxxxxxxxxxxxx]

The internal project communication issue has raised its head again.  
Below is the current state of play (slight clarifications and 
corrections to the previously posted version).  The feeling I am getting 
is that 

1) Some people think things are being circulated on hyades-team that 
should be on hyades-dev
2) There are some subgroup conversations that don't get onto either list 
that probably should be on one or the other.

Mike

---------------------------------
Subject: Communicating with and within the Hyades Project
From: mgn@xxxxxxxxxxxxx (Mike Norman)
Newsgroups: eclipse.tools.hyades
Organization: http://www.eclipse.org
Date: Mar 31 2003 16:55:08 (with minor amendments June 12 2003)

The hyades newsgroup should contains discussion about released drivers 
etc.

There are two lists for active participants. hyades-dev@xxxxxxxxxxx
should be used for technical discussion.  It is in the public domain 
there
are no access controls and you can subscribe via Eclipse.org. The other
one is hyades-team@xxxxxxxxxxxxx which is designed for active 
participants
only, and should be used for non-technical discussion relating to the 
organization and management of the project. It requires
sponsorship from a group leader or me. 

If people want to maintain links with the project they should first join
hyades-dev.  If they require to get more deeply involved with the 
project
they can ask a group leader (or me) to request membership of 
hyades-team.
The hyades-team mailing list manager (mailto:systems@xxxxxxxxxxxxx) will
action requests if and only if they come from these sources.

For record the group leaders are

Model, Harm Sluiman (IBM Toronto) sluiman@xxxxxxxxxx
Execution, Kent Siefkes (IBM Rational), ksiefkes@xxxxxxxxxxxx
           Joe Toomey (IBM Rational), jptoomey@xxxxxxxxxx
Data, Richard Duggan (IBM Toronto), rduggan@xxxxxxxxxx
UI, Valentina Popescu (IBM Toronto), popescu@xxxxxxxxxx

I am

Project Lead, Mike Norman (Scapa Technologies), mgn@xxxxxxxxxxxxx