My MapServer Foundation thoughts
Puneet Kishor
mapserver at EIDESIS.ORG
Tue Nov 29 04:30:07 PST 2005
Tyler Mitchell wrote:
> In a nutshell, several groups and individuals have agreed that a foundation is
> a good idea and they want to see it move forward.
Yes, the foundation is a great idea. I believe so, and, I think, Ed
echoed the same sentiment.
> All that's been decided is that there will be a foundation and
> that Autodesk wants to contribute code to it.
The problem seems to lie with how it came about, and with some of the
result --
It was done in 'secrecy,' or so it seems. MapServer is all about
community, and the community was note roped in. Just having a poll, or
an animated list discussion, or even a half-a-day discussion at a
MapServer meeting, whatever, would have helped tremendously. Sure, there
would have been detractors even then, but know one could have said,
"Holy crap! where did that come from?" I remember when we all first met
at the first MUM... we were all putting faces to the names we had known
from the list for a long while. It was like a large family get-together.
Less than 200 folks, but there was joy in seeing and "recognizing" each
other. This secretive seeming maneuver has led to bickering. It should
have been not so... put the 'open' back in open source, because OS is
not just about the source, it is being open about everything.
> Autodesk's Role
> The assumption that Autodesk has somehow rolled in and taken the best seat in
> the house is far from the truth. We debated the issues such as naming and
> branding. Our group became comfortable with the ideas and thought they could
> at least serve as a starting place for community discussion. There was no
> name stealing, these were mutually debated and agreed upon ideas.
see, here is the problem... who is 'we'? who was in 'our group'? It
would have been nice if publicly the community (which is mostly the
denizens of these lists), had backed the 'group' and said, "Hey, great!
go ahead." It is all about the process.
As far as we here in our group see, the naming is terrible. I have an
idea... let our product be "MapServer Enterprise" (as loath as I am to
elongate the name), and let Autodesk call their product the "Autodesk
Plug-in/Extension for MapServer Enterprise."
That way, the focus will be very clear, and the traditionally MapServer
developers and users will continue to work on/with the product they
love, and those who want to use the Autodesk Plug-in for M2EE will do so
as well.
More information about the MapServer-users
mailing list