<div dir="ltr"><div dir="ltr">Dear all,<div><br></div><div>I'd like to add some information in preparation for the OSGeo meeting.</div><div><br></div><div>MapFish has multiple tribes: the python one, a PHP one as well as a Ruby on Rails one. With time and experience, the python tribe (developers and the users community) identified some shortcomings in the technical architecture and decided to rewrite the mapfish python part to make it easier to implement rich webgis applications. It has been implemented without coordination with the other tribes in a new version, lead by Eric Lemoine (MapFish PSC Chair), Brunot BInet (MapFish PSC member) and many others from the MapFish community contributors, [2] like Alexandre Saunier, Yves Bolognini, Frédéric Junod, Pierre Giraud and others.
So the development team is the same, as the one that participated to the incubation process for the python and the front end part.</div><div><br></div><div>Comparing the obsolete mapfish description with the geomapfish one tells us, the same goal is pursued:<br><ul><li><a href="http://mapfish.org" target="_blank">mapfish.org</a>: "MapFish is a flexible and complete framework for building rich web-mapping applications."</li><li><a href="http://geomapfish.org" target="_blank">geomapfish.org</a>: "GeoMapFish allows to build rich and extensible WebGIS in an easy and flexible way."</li></ul></div><div><br></div><div></div><div>On the technology side, the implementation team kept the same frameworks they worked on in the previous version: pylons, geoalchemy, etc on the server side, and geoext on the client side.<br></div><div><br></div><div>The Python tribes users base is the same, with users migrating to this new version. the community grew as this new implementation has been successful.</div><div><br></div><div>As time passes, some developers moved on and others joined. The
python implementation and the front end side are well maintained. It welcomes contributions and receives some, having on the backend 6 organisations contributing to it and 10 organisations contributing to the front end.</div><div><br></div><div>I see no kindness in some past members saying the project should be removed from the OSGEO and see no advantage for the community doing so. It's right, the architecture is no longer exactly the same, but the project goal, the community and the frameworks are the same.</div><div><br></div><div>I think the current issue we face is having an updated PSC reflecting current engagements in the community and being ready to update all related material. How should a retired PSC team act when developers work on the project and make it thrive, without their implications? I think it would be time for the PSC to resign and acknowledge, the community is de facto lead be a new generation of developers. Doing so, the osgeo could organize the nomination of a new PSC, granting the community committers the voting rights.</div><div><br></div><div>Best regards</div><div><br></div><div>Emmanuel</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div>[1] <a href="https://github.com/mapfish/mapfish/wiki/Community_PSC" target="_blank">https://github.com/mapfish/mapfish/wiki/Community_PSC</a></div><div>[2] <a href="https://github.com/mapfish/mapfish/wiki/Community_Committers" target="_blank">https://github.com/mapfish/mapfish/wiki/Community_Committers</a></div><div>[3] <a href="https://github.com/camptocamp/c2cgeoportal/graphs/contributors" target="_blank">https://github.com/camptocamp/c2cgeoportal/graphs/contributors</a></div><div>[4] <a href="https://github.com/camptocamp/ngeo/graphs/contributors" target="_blank">https://github.com/camptocamp/ngeo/graphs/contributors</a></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 19 Nov 2019 at 01:02, Jody Garnett <<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr">Earlier this year we places several osgeo projects that were not communicating (or no longer meeting osgeo expectations) into the OSGeo community program.<div><br></div><div>One project that asked for some more time was mapfish:</div><div><br></div><div>* The <a href="http://mapfish.org" target="_blank">mapfish.org</a><a href="http://www.mapfish.org/" target="_blank">http://www.mapfish.org/</a> website uses the old logo and documents MapFish 2.2 released in 2016</div><div>* The osgeo project page was never filled in <a href="https://www.osgeo.org/projects/mapfish/" target="_blank">https://www.osgeo.org/projects/mapfish/</a> (1)<br></div><div><br></div><div>The good news is that the the project is very much alive, has a new GeoMapFish name, <a href="https://geomapfish.org" target="_blank">website</a>, <a href="http://github.com/camptocamp/c2cgeoportal" target="_blank">code base</a>, and a new development team (indeed I am not sure if any current members took part in the incubation process).<br></div><div><br></div><div>On the bright side Emmanuel and the MapFisk PSC produced a page for the AGM (slide 59) which is great and really improves communication.<br></div><div><br></div><div>My question though is simple - should we remove MapFish as an OSGeo project, and invite GeoMapFish to apply to the OSGeo Community program, or should we ask this PSC to quick march this project through the incubation checklist requirements to preserve continuity?</div><div><br></div><div>Emmanuel would you be able to attend the board meeting to provide an update on this project? If you need help setting up osgeo project page we are happy to do so on the incubation email list.</div><div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>--</div><div>Jody Garnett</div><div><br></div><div>(1) Wishing to recommend mapfish today and finding this page is what promoted this email</div></div></div></div></div></div></div></div></div></div>
</blockquote></div><br clear="all"></div><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><span style="font-size:12.8px">Emmanuel Belo</span><br></div><div>Camptocamp<br><br>Mon. Tue. Thu. Fri. <div>+41 79 936 46 62<div><br></div></div></div></div></div></div></div></div></div></div></div></div></div>