[Board] mapfish project status

Jody Garnett jody.garnett at gmail.com
Wed Nov 20 07:29:21 PST 2019


Thanks everyone, this is all a good discussion - and one of the reasons the
board has been reaching out to projects and promoting involvement in osgeo
activities (AGM and annual budget).

I invite board members to read the above exchange and we will discuss on
Monday's meeting.
--
Jody Garnett


On Wed, 20 Nov 2019 at 00:48, Till Adams <till.adams at fossgis.de> wrote:

> Dear Jody,
>
> I am also little surprised about the movememtns in the mapfish project,
> for me it looks little like a "take over" of the "old" Mapfish-project.
> Wehen Mapfish applied for incubation (around 2009/2010), I was voted
> into the PSC and I accompanied MapFish through this process. To be
> honest, since our incubation not much happened in PSC.
>
> On the Github "https://github.com/mapfish/mapfish/wiki/Community_PSC", I
> am still listed as a PSC-member, I never stepped back and AFAIK I was
> not asked to migrate the project into a new one. So, still, this
> mapfish-project is for me the incubated project and it seems, that
> nothing happens any more here.
>
> In general I wonder, that projects once they are incubated, never get a
> check towards license/code again, even if they move on a completely new
> platform and code-base. This may open the door to exactly, what we want
> to prevent: That projects get hijacked by one single company.
>
> Loking on the new github pages
> (http://github.com/camptocamp/c2cgeoportal), there is no PSC listed at
> all.
>
> I would suggest to invite the new geomapfish project to become an
> OSGeo-community project and, I agree with Primin, the (old) Mapfish
> should be retired.
>
> Just my 2 Cents,
>
> Till
>
>
>
>
> Am 20.11.19 um 08:18 schrieb Pirmin Kalberer:
> > Hi Jody,
> >
> > On 19.11.19 01:02, Jody Garnett wrote:
> >> Earlier this year we places several osgeo projects that were not
> >> communicating (or no longer meeting osgeo expectations) into the
> >> OSGeo community program.
> >>
> >> One project that asked for some more time was mapfish:
> >>
> >> * The mapfish.org <http://mapfish.org>http://www.mapfish.org/ website
> >> uses the old logo and documents MapFish 2.2 released in 2016
> >> * The osgeo project page was never filled in
> >> https://www.osgeo.org/projects/mapfish/ (1)
> >>
> >> The good news is that the the project is very much alive, has a new
> >> GeoMapFish name, website <https://geomapfish.org>, code base
> >> <http://github.com/camptocamp/c2cgeoportal>, and a new development
> >> team (indeed I am not sure if any current members took part in the
> >> incubation process).
> >
> > This is quite surprising news for a former MapFish commiter. I wasn't
> > aware that there is any relaton between the MapFish project and the
> > c2cgeoportal project besides the new name.
> > MapFish had a very compelling architecture with a clear separation of
> > server and client side with a JSON API in between. As far as I
> > remember, C2C later decided to start a new project with a classic
> > monolithic approach. On our part we kept the Ruby on Rails server
> > implementation, which is actively developed under the name Mapfish
> > Appserver. It's not a real community project, since it's mainly
> > developed by the Canton of Zurich on their internal Git server today.
> >
> >>
> >> On the bright side Emmanuel and the MapFisk PSC produced a page for
> >> the AGM (slide 59) which is great and really improves communication.
> >>
> >> 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?
> >
> > Since only MapFish Print is still alive, which is a Java application
> > inherited from the CartoWeb project, the MapFish project should be
> > officially retired.
> >
> > Regards
> > Pirmin
> > _______________________________________________
> > Board mailing list
> > Board at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/board
> _______________________________________________
> Board mailing list
> Board at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/board
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/board/attachments/20191120/4c420c03/attachment.htm>


More information about the Board mailing list