[mapguide-psc] PSC vs DEV list

[Haris Kurtagic]

+1

________________________________

From: Bruce Dechant [mailto:bruce.dechant at autodesk.com] 
Sent: Thursday, November 02, 2006 5:10 AM
To: psc at mapguide.osgeo.org; psc at mapguide.osgeo.org
Subject: RE: [mapguide-psc] PSC vs DEV list


+1

	-----Original Message----- 
	From: Andy Morsell [mailto:amorsell at spatialgis.com] 
	Sent: Wed 11/1/2006 7:33 PM 
	To: psc at mapguide.osgeo.org 
	Cc: 
	Subject: RE: [mapguide-psc] PSC vs DEV list
	
	

	+1.  I guess I should subscribe to the dev list now..........
	
	
	Andy
	
	-----Original Message-----
	From: Robert Bray [mailto:rbray at robertbray.net]
	Sent: Wednesday, November 01, 2006 6:27 PM
	To: psc at mapguide.osgeo.org
	Subject: Re: [mapguide-psc] PSC vs DEV list
	
	I'll second and +1.
	
	Bob
	
	Jason Birch wrote:
	> Given the lack of objections, I'd like to move to archive the
PSC list
	> and move all future discussions to the DEV list.
	>
	> Consider this a +1 once somebody second's.
	>
	> Jason
	>
	> -----Original Message-----
	> From: Daniel Morissette [mailto:dmorissette at mapgears.com]
	> Sent: Wednesday, November 01, 2006 13:10
	> To: psc at mapguide.osgeo.org
	> Subject: [mapguide-psc] PSC vs DEV list
	>
	> After seeing the discussions on RFC-1 split between the PSC
and DEV
	> lists, it seems to me that having split PSC and DEV lists
results in
	> duplicate messages for those on both lists and on partial
threads for
	> those only on one list. In both cases that's no good. Am I the
only
	> one to think this way?
	>
	> Would we not be better with just one list? Or if we insist on
having
	> two lists then discuss RFCs and all technical issues to the
-dev list
	> *only* (including the vote), with the understanding that PSC
members
	> are required to follow the -dev list?
	>
	> Daniel
	> --
	> Daniel Morissette
	> http://www.mapgears.com/
	>
	>  
	
	
	
	

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide_psc/attachments/20061102/8072dfaa/attachment.html