<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Mateusz,<br>
<br>
What we have found on the mapguide project is that all users are
developers, some people like yourself write code on the project and
others (the majority) are application developers that use our APIs.
Often the second category posts app development questions to
mapguide-dev when in reality they should have been posted to
mapguide-users. I think as the FDO lists grow we'll experience the same
problems, which is why I have backed this change. Both the PHP and
MySQL projects use -internals to avoid that type of confusion.<br>
<br>
The reality is I don't like it either, but I think it will be
beneficial to the project in the long run. <br>
And you my friend are never interfering, just asking good questions.<br>
<br>
Bob<br>
<br>
Mateusz Loskot wrote:
<blockquote cite="mid45A728D8.6000605@loskot.net" type="cite">
<pre wrap="">Hi,
Sorry for interfering, but what about:
fdo-dev - for FDO dev team discussions
fdo-users - for FDO users, all who use FDO in their applications
Mateusz
Robert Bray wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Shawn,
If you see this before you make the MapGuide and FDO list changes,
please alter the plan as follows:
Mapguide-dev => mapguide-internals
Fdo-dev => fdo-internals
I agree with Jason that this will hopefully prevent application
developers from posting questions on the development list.
Thanks,
Bob
Jason Birch wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I know that this might be late, but can I suggest that we use "mapguide-internals" rather than "mapguide-dev" ???
This avoids the inherent confusion that results from many of our end users being developers.
It appears that MySQL and PHP are both using this convention, likely for the same reason.
Jason
________________________________
From: <a class="moz-txt-link-abbreviated" href="mailto:sac-bounces@lists.osgeo.org">sac-bounces@lists.osgeo.org</a> on behalf of shawn barnes
Sent: Thu 2007-01-11 11:29 AM
To: System Administration Committee Discussion/OSGeo
Subject: Re: [SAC] Mailing List Change Request
Jason, Bob,
www_admin was a list for cn mail server to send mail to. It's now deleted
I've also deleted the following lists:
Webcommittee_announce
Webcommittee_commits
Webcommittee_issues
Www_news-item
Www_cvs
Mg-sandbox_commits
Mg-sandbox_issues
Fdoarcsde_commits
Fdocore_commits
Fdogdal_commits
Fdoogr_commits
Fdooracle_commits
Fdordbms_commits
Fdosdf_commits
Fdoshp_commits
Fdowfs_commits
Fdowms_commits
lists removed with archives left intact:
Mapguide_issues
Mapguide_psc
Fdo_issues
Fdo_psc
Mail_mse-users
archives are accessible at lists.osgeo.org/pipermail/
Tomorrow i will move/rename the following lists
Webcommittee_dev => webcom
Mapguide_announce => mapguide-announce
Mapguide_dev => mapguide-dev
Mapguide_users => mapguide-users
Mapguide_commits => mapguide-commits
Fdo_announce => fdo-announce
Fdo_commits => fdo-commits
Fdo_dev => fdo-dev
Fdo_users => fdo-users
shawn
Jason Birch wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Shawn,
If possible, could you please do the following at the same time?
Delete:
Webcommittee_announce@
Webcommittee_commits@
Webcommittee_issues@
Www_news-item@
Www_cvs@
Rename:
Webcommittee_dev@ to webcom@
and if you have time... investigate:
Www_admin
(I have no idea what this is)
Thanks,
Jason
________________________________
From: <a class="moz-txt-link-abbreviated" href="mailto:sac-bounces@lists.osgeo.org">sac-bounces@lists.osgeo.org</a> on behalf of shawn barnes
Sent: Thu 2007-01-11 6:12 AM
To: System Administration Committee Discussion/OSGeo
Subject: Re: [SAC] Mailing List Change Request
Bob,
I'll can do the deleting and deactivating today and tomorrow morning
i'll do the renaming.
shawn
Robert Bray wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Shawn,
I would like to request some changes to the MapGuide and FDO project mailing
lists. Specifically I would like to rename some of mailing lists, deactivate
some lists, and remove some lists altogether.
*The lists to be renamed are:*
Mapguide_announce => mapguide-announce
Mapguide_dev => mapguide-dev
Mapguide_users => mapguide-users
Mapguide_commits => mapguide-commits (should be hooked to broadcast SVN commits)
Fdo_announce => fdo-announce
Fdo_commits => fdo-commits (should be hooked to broadcast all FDO project SVN
commits)
Fdo_dev => fdo-dev
Fdo_users => fdo-users
*The lists to be deactivated (but I would like access to the archives if possible):*
Mapguide_issues
Mapguide_psc
Fdo_issues
Fdo_psc
Mail_mse-users
*Lists to be deleted:*
Mg-sandbox_commits
Mg-sandbox_issues
Fdoarcsde_commits
Fdocore_commits
Fdogdal_commits
Fdoogr_commits
Fdooracle_commits
Fdordbms_commits
Fdosdf_commits
Fdoshp_commits
Fdowfs_commits
Fdowms_commits
Please let me know if this will be possible and when the changes could be made.
Thanks,
Bob
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>