[mapguide-psc] PSC vs DEV list

[Paul Spencer]

I think the original intention was to shield the developers from  
process oriented discussions :)

I'm okay with merging the lists ...

Paul

On 1-Nov-06, at 6:09 PM, Jason Birch wrote:

>
> Given the size of the project, I think it makes sense to merge the
> lists.  If it gets busier and confusing later then we can look at
> splitting it back out.  If we have agreement on this, then we can make
> this our first e-Vote on process change and the last email on the PSC
> list (which we will archive, not delete) :)
>
> I wish this list stripped email addresses from replies  
> automagically...
> I keep forgetting.
>
> Jason
>
> -----Original Message-----
> From: Daniel Morissette
> 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/

+-----------------------------------------------------------------+
|Paul Spencer                          pspencer at dmsolutions.ca    |
+-----------------------------------------------------------------+
|Chief Technology Officer                                         |
|DM Solutions Group Inc                http://www.dmsolutions.ca/ |
+-----------------------------------------------------------------+