[OSGeo-Discuss] End of life for Community Mapbuilder

[Cameron Shorter]

End of life for Community Mapbuilder
We, the Mapbuilder Project Steering Committee, have agreed that the
time has come for the Community
Mapbuilder
project to gracefully retire. We will release a final, stable 1.5
version of the software, and afterwards there are no planned
enhancements to Mapbuilder. The web pages and code will be kept alive,
a few bugs might be fixed and we will likely continue answering user
queries, but we expect Mapbuilder will gradually fade away into
history. 
Why?
Mapbuilder is a stable,
feature rich, standards compliant, fast, webmapping framework with a
strong developer community. Why has it come to the end of its life?
The
browser based webmapping space has become crowded and other webmapping
clients have increased in functionality and attractiveness to users. In
particular, Openlayers is simpler to use, has attracted an increabibly
strong developer community, has good quality control and development
processes, and has developed most of the webmapping functionality
previously only offered by Mapbuilder. Basically Openlayers is
attacting the majority of the users and developers that previously
would have used Mapbuilder. One day someone will write a compelling
paper on the history of the two similar projects and analyse the key
differences and decision points which led to one project out shining
the other.
But we are not crying
Well,
maybe we feel a twing of loss for the Mapbuilder project we started
years ago, but in the bigger picture, we see the retiring of Mapbuilder
as a good thing. It will allow the greater web mapping community to
consolidate and rally around the remaining webmapping tools – in
particular, around Openlayers.
There has been significant
collaboration between the Mapbuilder and Openlayers communities over
the last couple of years. Mapbuilder has incorporated Openlayers as its
rendering engine and fetures have been shared between projects. In many
cases, developers from both projects worked together on the same
codebase (in Openlayers), then ported up to Mapbuilder. This was a
deliberate move toward the merging of the two developer communities and
most of the Mapbuilder Project Steering Committee have contributed to
the Openlayers codebase.
So in essence, by changing our
allegience from Mapbuilder to Openlayers we take with us some of our
code, we replace some features with equivalent Openlayers features, we
take our community with us, and we gain an existing, robust and
welcoming community.
What should Mapbuilder users do?
Users
have a few options. You already own the source code, so you are welcome
to continue maintaining and extending the Mapbuilder code for as long
as you like. At some point, users will likely want to upgrade, and at
that point we suggest considering Openlayers for your application. It
now provides the majority of the fuctionality that was previously only
offered by Mapbuilder.
What about Mapbuilder's standing with OSGeo?
Having
a graduated OSGeo project retire might be seen as an embarassment for
OSGeo, however, I'd argue it is a strength. It shows two projects
growing together under the OSGeo umbrella and evenually merging into a
stronger, more focused community.
However, it does raise a
dilemma with regards to what should be done with a retired project.
Some of the key OSGeo criteria, like “Community Backing” and “Best of
Breed Software” will gradually be lost, so we should not continue to
promote Mapbuilder. Still, we wouldn't want to erase Mapbuilder's
history with OSGeo as our community has documented valuable lessons
learned during the graduation process.
I suggest a new “retired” category be created which keeps track of
retired projects.
Thanks
We,
the project steering committee, have derived a huge amount of pleasure
building Mapbuilder and working with the Mapbuilder Community. For many
of us, Mapbuilder has been a launching pad into a fullfilling Open
Source and/or Geospatial career. We'd like to thank all the users,
developers and supporters of Mapbuilder we have met along the way.



The Mapbuilder Project Steering Committee, (in order of appearance):


  
Cameron Shorter
  
  
Mike Adair
  
  
Patrice Cappelaere
  
  
Steven M. Ottens
  
  
Matt Diez
  
  
Olivier Terral 
  
  
Andreas Hocevar 
  
  
Gertjan van Oosten 
  
  
Linda Derezinski 
  


-- 
Cameron Shorter
Geospatial Systems Architect
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Commercial Support for Geospatial Open Source Solutions
http://www.lisasoft.com/LISAsoft/SupportedProducts.html



___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

[OSGeo-Discuss] Martin Bunch is out of the office.

[Martin Bunch]

I will be out of the office starting Sat 07/26/2008 and will not return
until Tue 08/05/2008.

Your mail may not be read until I return.___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] End of life for Community Mapbuilder

[Milo van der Linden]

Hello Cameron!

Excellent decision! It takes a lot of courage to admit that the value of
a project is decreased because of the competition. Despite the fact that
some components of mapbuilder are really great!

I hope the knowledge of the people who worked on mapbuilder will find
its way into the OSGeo projects and that those people will find equal
pleasure in helping the other projects grow and mature!


Sincerely,

Milo van der Linden

Cameron Shorter wrote:
>   End of life for Community Mapbuilder
> 
> We, the Mapbuilder Project Steering Committee, have agreed that the time has 
> come for the Community Mapbuilder  project 
> to 
> gracefully retire. We will release a final, stable 1.5 version of the 
> software, 
> and afterwards there are no planned enhancements to Mapbuilder. The web pages 
> and code will be kept alive, a few bugs might be fixed and we will likely 
> continue answering user queries, but we expect Mapbuilder will gradually fade 
> away into history.
> 
> 
> Why?
> 
> Mapbuilder is a stable, feature rich, standards compliant, fast, webmapping 
> framework with a strong developer community. Why has it come to the end of 
> its life?
> 
> The browser based webmapping space has become crowded and other webmapping 
> clients have increased in functionality and attractiveness to users. In 
> particular, Openlayers is simpler to use, has attracted an increabibly strong 
> developer community, has good quality control and development processes, and 
> has 
> developed most of the webmapping functionality previously only offered by 
> Mapbuilder. Basically Openlayers is attacting the majority of the users and 
> developers that previously would have used Mapbuilder. One day someone will 
> write a compelling paper on the history of the two similar projects and 
> analyse 
> the key differences and decision points which led to one project out shining 
> the 
> other.
> 
> 
> But we are not crying
> 
> Well, maybe we feel a twing of loss for the Mapbuilder project we started 
> years 
> ago, but in the bigger picture, we see the retiring of Mapbuilder as a good 
> thing. It will allow the greater web mapping community to consolidate and 
> rally 
> around the remaining webmapping tools – in particular, around Openlayers.
> 
> There has been significant collaboration between the Mapbuilder and 
> Openlayers 
> communities over the last couple of years. Mapbuilder has incorporated 
> Openlayers as its rendering engine and fetures have been shared between 
> projects. In many cases, developers from both projects worked together on the 
> same codebase (in Openlayers), then ported up to Mapbuilder. This was a 
> deliberate move toward the merging of the two developer communities and most 
> of 
> the Mapbuilder Project Steering Committee have contributed to the Openlayers 
> codebase.
> 
> So in essence, by changing our allegience from Mapbuilder to Openlayers we 
> take 
> with us some of our code, we replace some features with equivalent Openlayers 
> features, we take our community with us, and we gain an existing, robust and 
> welcoming community.
> 
> 
> What should Mapbuilder users do?
> 
> Users have a few options. You already own the source code, so you are welcome 
> to 
> continue maintaining and extending the Mapbuilder code for as long as you 
> like. 
> At some point, users will likely want to upgrade, and at that point we 
> suggest 
> considering Openlayers for your application. It now provides the majority of 
> the 
> fuctionality that was previously only offered by Mapbuilder.
> 
> 
> What about Mapbuilder's standing with OSGeo?
> 
> Having a graduated OSGeo project retire might be seen as an embarassment for 
> OSGeo, however, I'd argue it is a strength. It shows two projects growing 
> together under the OSGeo umbrella and evenually merging into a stronger, more 
> focused community.
> 
> However, it does raise a dilemma with regards to what should be done with a 
> retired project. Some of the key OSGeo criteria, like “Community Backing” and 
> “Best of Breed Software” will gradually be lost, so we should not continue to 
> promote Mapbuilder. Still, we wouldn't want to erase Mapbuilder's history 
> with 
> OSGeo as our community has documented valuable lessons learned during the 
> graduation process.
> 
> I suggest a new “retired” category be created which keeps track of retired 
> projects.
> 
> 
> Thanks
> 
> We, the project steering committee, have derived a huge amount of pleasure 
> building Mapbuilder and working with the Mapbuilder Community. For many of 
> us, 
> Mapbuilder has been a launching pad into a fullfilling Open Source and/or 
> Geospatial career. We'd like to thank all the users, developers and 
> supporters 
> of Mapbuilder we have met along the way.
> 
> 
> 
> The Mapbuilder Project Steering Committee, (in order of appearance):
> 
> *
> 
>   Cameron Shorter
> 
> *
> 
>   Mike Adair
> 
>

Re: [OSGeo-Discuss] End of life for Community Mapbuilder

[andrea giacomelli]

Cameron - this is indeed an extremely interesting message.

I need to thank you (and your team) for drafting a communication that
may be of interest for many.

Just a sidebar note, below, as the concept of a "retired application"
made me smile...(see below)

2008/7/28 Cameron Shorter <[EMAIL PROTECTED]>:
> End of life for Community Mapbuilder
>
> We, the Mapbuilder Project Steering Committee, have agreed that the time has
> come for the Community Mapbuilder project to gracefully retire. ..
>
> I suggest a new "retired" category be created which keeps track of retired
> projects.
>

to expand on these lines...

...If the retired project belongs more to US, may I recommend it
spends some time on a server located in the Florida Keys.

...If it belongs more to Europe, maybe Provence or Tuscany or other
similar spots may be a good place for retired Mapbuilder to sit...

...If it feels like an Asian project, or from other regions of the
world, I would like to know where Asians, Africans etc - would like to
see it end its days.

no puns intended - I think we are going to investigate more and more
on the full life cycle of geospatial software (as more of these
dynamics should be expected in the future), and I will keep your
initial posting on Mapbuilder as a reference in this respect.

Regards

Andrea Giacomelli, aka pibinko
vicepresident and media relations manager - GFOSS.it - Italian OSGeo Chapter
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] End of life for Community Mapbuilder

[Frank Warmerdam]

Cameron Shorter wrote:


  End of life for Community Mapbuilder

We, the Mapbuilder Project Steering Committee, have agreed that the time 
has come for the Community Mapbuilder  
project to gracefully retire. We will release a final, stable 1.5 
version of the software, and afterwards there are no planned 
enhancements to Mapbuilder. The web pages and code will be kept alive, a 
few bugs might be fixed and we will likely continue answering user 
queries, but we expect Mapbuilder will gradually fade away into history.


Cameron,

I think this is an excellent and professional approach - given a clear heads
up to the community on the status of things.  In fact, I've been just thrilled
by the degree of cooperation achieved between several of the web mapping client
side projects in recent years.  The experience and efforts focused on
improvement and exploitation of OpenLayers by those involved in Mapbuilder,
ka-map and other projects has helped turn OpenLayers into what I would argue
is the "best of breed" role it plays now.

As far as OSGeo process, I agree that we (perhaps within the incubation
committee?) need to work out an end-of-life/retired status for projects.
There is no problem continuing to host project resources of course, but at
some point we would want to release the project from "live status" reporting
and governance requirements and to remove it from the front page so not too
many new users are guided to it as a promoted project.

If there is no objection, I'll distribute the eol announcement via the
OSGeo announce mechanism.

Best regards,
--
---+--
I set the clouds in motion - turn up   | Frank Warmerdam, [EMAIL PROTECTED]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush| President OSGeo, http://osgeo.org

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] End of life for Community Mapbuilder

[Jeroen Ticheler]

Hi Cameron and others,
Congratulations indeed for the decision and way forward!
Looking at what for instance the Apache Jakarta Project does, adding a  
"Retired projects" page seems a good solution. Elegant and clear. See http://jakarta.apache.org/site/retired-projects.html
I have no problem with seeing such a link in the current projects  
listing on the OSGeo homepage.

Ciao,
Jeroen

On Jul 28, 2008, at 4:32 PM, Frank Warmerdam wrote:


Cameron Shorter wrote:

 End of life for Community Mapbuilder
We, the Mapbuilder Project Steering Committee, have agreed that the  
time has come for the Community Mapbuilder  project to gracefully retire. We will release a final, stable 1.5  
version of the software, and afterwards there are no planned  
enhancements to Mapbuilder. The web pages and code will be kept  
alive, a few bugs might be fixed and we will likely continue  
answering user queries, but we expect Mapbuilder will gradually  
fade away into history.


Cameron,

I think this is an excellent and professional approach - given a  
clear heads
up to the community on the status of things.  In fact, I've been  
just thrilled
by the degree of cooperation achieved between several of the web  
mapping client

side projects in recent years.  The experience and efforts focused on
improvement and exploitation of OpenLayers by those involved in  
Mapbuilder,
ka-map and other projects has helped turn OpenLayers into what I  
would argue

is the "best of breed" role it plays now.

As far as OSGeo process, I agree that we (perhaps within the  
incubation
committee?) need to work out an end-of-life/retired status for  
projects.
There is no problem continuing to host project resources of course,  
but at
some point we would want to release the project from "live status"  
reporting
and governance requirements and to remove it from the front page so  
not too

many new users are guided to it as a promoted project.

If there is no objection, I'll distribute the eol announcement via the
OSGeo announce mechanism.

Best regards,
--
--- 
+--

I set the clouds in motion - turn up   | Frank Warmerdam, [EMAIL PROTECTED]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush| President OSGeo, http://osgeo.org

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] End of life for Community Mapbuilder

[Mateusz Loskot]

Milo van der Linden wrote:

Hello Cameron!

Excellent decision! It takes a lot of courage to admit that the value of
a project is decreased because of the competition. Despite the fact that
some components of mapbuilder are really great!


I'd like to second Milo's message and also drop my 5 cents of support to 
the MapBuilder community. At first, I felt a little crying smell, but 
while reading next parts of Cameron's message I found there is a victory 
print on that - the community is mature and strong enough to reorganize 
 itself and reallocate manpower for new benefits.


"For the loser now
Will be later to win
For the times they are a-changin'." -- Dylan

--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] End of life for Community Mapbuilder

[Mike Adair]

Frank Warmerdam wrote:

In fact, I've been just thrilled
by the degree of cooperation achieved between several of the web 
mapping client

side projects in recent years.  The experience and efforts focused on
improvement and exploitation of OpenLayers by those involved in 
Mapbuilder,
ka-map and other projects has helped turn OpenLayers into what I would 
argue
is the "best of breed" role it plays now. 
I just want to point out that a key event in this process was the web 
mapping client BoF at Lausanne where all of the FOSS client projects got 
together and decided to stop re-inventing the wheel.  For me, this is a 
tangible demonstration of the benefits that OSGeo can achieve.


Mike
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] End of life for Community Mapbuilder

[Frank Warmerdam]

Mike Adair wrote:

Frank Warmerdam wrote:

In fact, I've been just thrilled
by the degree of cooperation achieved between several of the web 
mapping client

side projects in recent years.  The experience and efforts focused on
improvement and exploitation of OpenLayers by those involved in 
Mapbuilder,
ka-map and other projects has helped turn OpenLayers into what I would 
argue
is the "best of breed" role it plays now. 
I just want to point out that a key event in this process was the web 
mapping client BoF at Lausanne where all of the FOSS client projects got 
together and decided to stop re-inventing the wheel.  For me, this is a 
tangible demonstration of the benefits that OSGeo can achieve.


Mike,

Agreed - though one could argue it is more a tangible demonstration that
getting together lots of people from different projects in one place can
have huge benefits.  I do like to believe that OpenLayers transition to
OSGeo with the guarantees of open governance that come with it, were helpful
in making other project developers more comfortable with making a bit
commitment to OpenLayers.

FOSS4G has a variety of goals, but for me it is this "meeting of tribes"
from different projects aspect that is most important.  It provides a
critical opportunity for inter-project cooperation and collaboration.

Best regards,
--
---+--
I set the clouds in motion - turn up   | Frank Warmerdam, [EMAIL PROTECTED]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush| President OSGeo, http://osgeo.org

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] End of life for Community Mapbuilder

[Allan Doyle]

I remember Mike Adair's demo of MapBuilder to me, long ago at an OGC  
meeting, and how impressed I was. The kinds of things they were doing  
were ground-breaking. I think the entire Geo FOSS community has been  
strengthened by the accomplishments of this project. I can understand  
the bittersweet nature of an announcement like this. I tip my hat to  
the entire MapBuilder steering committee for their obviously deep  
commitment to the OSGeo cause.


This is truly an example of thinking globally!

Allan

On Jul 28, 2008, at 7:02 AM, Cameron Shorter wrote:


End of life for Community Mapbuilder

We, the Mapbuilder Project Steering Committee, have agreed that the  
time has come for the Community Mapbuilder project to gracefully  
retire. We will release a final, stable 1.5 version of the software,  
and afterwards there are no planned enhancements to Mapbuilder. The  
web pages and code will be kept alive, a few bugs might be fixed and  
we will likely continue answering user queries, but we expect  
Mapbuilder will gradually fade away into history.


Why?

Mapbuilder is a stable, feature rich, standards compliant, fast,  
webmapping framework with a strong developer community. Why has it  
come to the end of its life?


The browser based webmapping space has become crowded and other  
webmapping clients have increased in functionality and  
attractiveness to users. In particular, Openlayers is simpler to  
use, has attracted an increabibly strong developer community, has  
good quality control and development processes, and has developed  
most of the webmapping functionality previously only offered by  
Mapbuilder. Basically Openlayers is attacting the majority of the  
users and developers that previously would have used Mapbuilder. One  
day someone will write a compelling paper on the history of the two  
similar projects and analyse the key differences and decision points  
which led to one project out shining the other.


But we are not crying

Well, maybe we feel a twing of loss for the Mapbuilder project we  
started years ago, but in the bigger picture, we see the retiring of  
Mapbuilder as a good thing. It will allow the greater web mapping  
community to consolidate and rally around the remaining webmapping  
tools – in particular, around Openlayers.


There has been significant collaboration between the Mapbuilder and  
Openlayers communities over the last couple of years. Mapbuilder has  
incorporated Openlayers as its rendering engine and fetures have  
been shared between projects. In many cases, developers from both  
projects worked together on the same codebase (in Openlayers), then  
ported up to Mapbuilder. This was a deliberate move toward the  
merging of the two developer communities and most of the Mapbuilder  
Project Steering Committee have contributed to the Openlayers  
codebase.


So in essence, by changing our allegience from Mapbuilder to  
Openlayers we take with us some of our code, we replace some  
features with equivalent Openlayers features, we take our community  
with us, and we gain an existing, robust and welcoming community.


What should Mapbuilder users do?

Users have a few options. You already own the source code, so you  
are welcome to continue maintaining and extending the Mapbuilder  
code for as long as you like. At some point, users will likely want  
to upgrade, and at that point we suggest considering Openlayers for  
your application. It now provides the majority of the fuctionality  
that was previously only offered by Mapbuilder.


What about Mapbuilder's standing with OSGeo?

Having a graduated OSGeo project retire might be seen as an  
embarassment for OSGeo, however, I'd argue it is a strength. It  
shows two projects growing together under the OSGeo umbrella and  
evenually merging into a stronger, more focused community.


However, it does raise a dilemma with regards to what should be done  
with a retired project. Some of the key OSGeo criteria, like  
“Community Backing” and “Best of Breed Software” will gradually be  
lost, so we should not continue to promote Mapbuilder. Still, we  
wouldn't want to erase Mapbuilder's history with OSGeo as our  
community has documented valuable lessons learned during the  
graduation process.


I suggest a new “retired” category be created which keeps track of  
retired projects.


Thanks

We, the project steering committee, have derived a huge amount of  
pleasure building Mapbuilder and working with the Mapbuilder  
Community. For many of us, Mapbuilder has been a launching pad into  
a fullfilling Open Source and/or Geospatial career. We'd like to  
thank all the users, developers and supporters of Mapbuilder we have  
met along the way.




The Mapbuilder Project Steering Committee, (in order of appearance):

Cameron Shorter
Mike Adair
Patrice Cappelaere
Steven M. Ottens
Matt Diez
Olivier Terral
Andreas Hocevar
Gertjan van Oosten
Linda Derezinski


--
Cameron Shorter
Geospatial Systems Arch

RE: [OSGeo-Discuss] End of life for Community Mapbuilder

[Gavin Fleming]

Mike's mention of the key role of a BoF in cooperation among projects is as 
good a reason as any to mention that you can plan your BoF session for 2008 
here: http://wiki.osgeo.org/wiki/FOSS4G2008_BOF_Sessions. Who knows where it 
will lead?
 
Gavin 
FOSS4G2008 conference chair
--
Frank Warmerdam wrote:
> In fact, I've been just thrilled
> by the degree of cooperation achieved between several of the web
> mapping client
> side projects in recent years.  The experience and efforts focused on
> improvement and exploitation of OpenLayers by those involved in
> Mapbuilder,
> ka-map and other projects has helped turn OpenLayers into what I would
> argue
> is the "best of breed" role it plays now.
I just want to point out that a key event in this process was the web
mapping client BoF at Lausanne where all of the FOSS client projects got
together and decided to stop re-inventing the wheel.  For me, this is a
tangible demonstration of the benefits that OSGeo can achieve.

Mike
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

<>___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

[OSGeo-Discuss] Annual Meeting at FOSS4G

[OSGeo]

Just a quick note to invite projects and committees to present a  
brief update at the meeting.  Just sign up here:


http://wiki.osgeo.org/wiki/Annual_General_Meeting_2008

Tyler
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

[OSGeo-Discuss] Borealis becomes OSGeo Sponsor

[Tyler Mitchell (OSGeo)]

I'm pleased to announce that Boreal – Information Strategies  
(Borealis) is the latest OSGeo Associate Sponsor!  Borealis is an  
information technology company providing geospatial data management  
and integration services to mining, oil & gas and energy industries.  
They focus on integrating geospatial data into business processes  
(geobusiness).


Patrick Grégoire, VP, describes:

"We develop custom solutions and all our geospatial components use  
only open source technologies. Open source software allows us to  
quickly package and deploy professional geospatial solutions to our  
clients.  We deliver Information Management Systems to help them to  
manage the social and environmental impacts of their projects in  
developing countries.


We want to contribute to OSGeo and participate in the future  
development and orientation of the open source geospatial software  
stack and share our implementation experiences with the community."


Please join me in thanking and welcoming this encouraging support  
from Borealis.


You can learn more about Borealis at: http://www.boreal-is.com

Sincerely,
Tyler


Tyler Mitchell
Executive Director
Open Source Geospatial Foundation
[EMAIL PROTECTED]
P: +1-250-277-1621
M: +1-250-303-1831___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

[OSGeo-Discuss] Do your Police Geocache?

[Tyler Mitchell (OSGeo)]

Thought this might interest you.
http://www.cbc.ca/canada/ottawa/story/2008/07/28/ot-bomb-080728.html

It makes me wonder how "in touch" my local authorities are with the  
"suspicious packages" I'm planting around our urban fringe.  Hmmm...  
I hope they know geospatial information is important and can check it  
in a timely manner.


Anyone have any stories about how astute their local authorities are  
regarding geospatial technologies and data?


Tyler
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

Re: [OSGeo-Discuss] End of life for Community Mapbuilder

[Cameron Shorter]

Thanks to everyone for their kind words.

In specific answer to some of Frank's questions:
* Yes, feel free to forward on this announcement through whatever 
channels you wish.


* Yes, we should:
1. Through the incubation committee set up a process for retiring projects.
2. Hide mapbuilder references from all the key public facing web pages.

Frank Warmerdam wrote:

Cameron Shorter wrote:


  End of life for Community Mapbuilder

We, the Mapbuilder Project Steering Committee, have agreed that the 
time has come for the Community Mapbuilder 
 project to gracefully retire. We 
will release a final, stable 1.5 version of the software, and 
afterwards there are no planned enhancements to Mapbuilder. The web 
pages and code will be kept alive, a few bugs might be fixed and we 
will likely continue answering user queries, but we expect Mapbuilder 
will gradually fade away into history.


Cameron,

I think this is an excellent and professional approach - given a clear 
heads
up to the community on the status of things.  In fact, I've been just 
thrilled
by the degree of cooperation achieved between several of the web 
mapping client

side projects in recent years.  The experience and efforts focused on
improvement and exploitation of OpenLayers by those involved in 
Mapbuilder,
ka-map and other projects has helped turn OpenLayers into what I would 
argue

is the "best of breed" role it plays now.

As far as OSGeo process, I agree that we (perhaps within the incubation
committee?) need to work out an end-of-life/retired status for projects.
There is no problem continuing to host project resources of course, 
but at
some point we would want to release the project from "live status" 
reporting
and governance requirements and to remove it from the front page so 
not too

many new users are guided to it as a promoted project.

If there is no objection, I'll distribute the eol announcement via the
OSGeo announce mechanism.

Best regards,



--
Cameron Shorter
Geospatial Systems Architect
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Commercial Support for Geospatial Open Source Solutions
http://www.lisasoft.com/LISAsoft/SupportedProducts.html

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss

[OSGeo-Discuss] RE: Discuss Digest, Vol 19, Issue 27

[Bui Hong Son]

Thank to Community Mapbuilder and CS.
I learned a lot from Mapbuilder.

Bui Hong Son
Deputy Chief of SCIREN 
http://ciren.vn 
http://www2.hcm.ciren.gov.vn/cirengis



No virus found in this outgoing message.
Checked by AVG. 
Version: 7.5.524 / Virus Database: 270.5.6 - Release Date: 7/25/2008 12:00
AM
 


___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss