[Zoo-discuss] ZOO-Project version 2.0.0 has been released

2024-03-02 Thread Gérald Fenoy via ZOO-discuss 
Dear community,
as the release manager, I am happy to announce that the release of the 
ZOO-Project version 2.0.0 is available online [1].

Thanks everyone for your contributions to the project and its enhancement!

If you'd like to cite this release in your research article, refer to the DOI 
associated with the release [2].

This new release contains new features and fixes listed below.

  * Update the remote process support to enable multi-valued processes.
  * Add option to output log on stderr rather than a dedicated file.
  * Update relation type to monitor for the status location.
  * Add support for the conformance class remote processes from the
  OGC API - Processes - Part 3: Workflow & chaining. Execution of
  remote processes are automatically run asynchronously in case the
  root process was invoked asynchronously.
  * Parse the Location header from ulinet and the cookie if any.
  * Add schemas to the components and support description stored in the file.
  * Add a trivial DeployOnHpc service for automating the installation
  and the deployment of a singularity container using the image
  parameter provided in the executionUnit used when deploying the
  process.
  * Set the key json_response_object with the JSON response that the
  ZOO-Kernel produced for the request, it can be updated from a
  filter_out process.
  * Update filter_in to support returning a response directly by
  adding a response key in the lenv section (binary is supported for
  this response)
  * Provide an initial Dockefile dedicated to the DRU support with
  remote HPC execution support
  * Add a USE_HPC_NESTEDOUTPUTS build option to activate the nested
  inputs and outputs addition (not supported with OGC API - Processes - Part 1: 
Core)
  * Update C-API errorException and printExceptionResponse* signatures
  to handle the main configuration maps memory properly  
  *  Build Docker image with DRU supporting OpenEO UDP encoding 
  * Add support for deploying and executing OpenEO User Defined
  Processes by using an OpenEO graph for the executionUnit
  * Add support for schema type string for request body, providing a
  way to include CWL example files in the published OpenAPI
  * Integrate the OGC API - Processes - Part 2: Deploy, Replace,
  Undeploy optional support.
  * Build Docker image based on MDL4EO/OTBTF and the onnx runtime for
  models sharing
  * Integrate the TeamEngine and ETS for OGC API - Processes
  * Add JWT parser in security_service.py as filter_in to allocate
  resources per authenticated user
  * Integrate the work done during GSoC 2022 to support Node.js
  ZOO-Services (cf. updated documentation for NodeJS)
  * Update support to filter the jobs list using the user_id
  * Add support for nested processes n OGC API - Processes - Part 3: 
  Workflows & Chaining
  * Add filter_in and filter_out service array to be invoked previously
  of and after the service run
  * Add trivial support for OpenAPI security, basicAuth / openId, and add
  sample services implementation
  * Add support for MapServer 8.0 (actually 7.7-dev), including
  returning result as OGC API -Features
  * Integrate downloading MapServer 8.0 and building from the
  dedicated Dockerfile-MS8
  * Include basicAuth build instructions in the Dockefile
  * Add basicAuth service illustrating how to secure access to OGC API - 
Processes using Basic Authentication
  * Use the osecurity section to detect secured path, request method
  from the published OpenAPI
  * Update the printHeaders function to allow Status definition at runtime
  * Add a [osecurity] section to secure access to path, method couple
  from the published OpenAPI
  * Update the database connection handling to make it independent from
  instantiation order
  * Use the RabbitMQ also for OGC API - Processes
  * Pass the subscriber if any is passed from the original request
  * Make C OGR base-vect-ops compatible with memory=protect
  * Add volumes to be shared by the ZOO-Kernel and the ZOO-FPM
  * Add a RabbitMQ and a ZOO-FPM container to docker-compose
  * Add documentation for RabbitMQ support and ZOO Fast Process
  Manager (ZOO-FPM)
  * Optional use of ZOO-Kernel Fast Process Manager backends to handle
  asynchronous execution  
  * Partial integration of the code from the
  Publicamundi_David_integration01-devel branch

We appreciate and welcome any feedback.

Best regards,



[1] https://github.com/ZOO-Project/ZOO-Project/releases/tag/rel-2.0.0
[2] https://zenodo.org/badge/latestdoi/353351321


Gerald Fenoy
gerald.fe...@geolabs.fr
Chair, ZOO-Project PSC

___
ZOO-discuss mailing list
ZOO-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

[Zoo-discuss] ZOO-Project 2.0.0-rc2 now available!

2024-02-24 Thread Gérald Fenoy via ZOO-discuss 
Dear community,
As the current release manager, I announce that the latest release of 
ZOO-Project, version 2.0.0 release candidate 2, has been made available! [1]

Modifications compared to release candidate 1 are the following:

 * Update the remote process support to enable multi-valued processes.
 * Add configure option to output log on stderr rather than a dedicated file.

We will wait for one more week to have the final 2.0.0 release.

Best regards,

[1] https://github.com/ZOO-Project/ZOO-Project/releases/tag/rel-2.0.0-rc2


Gerald Fenoy
gerald.fe...@geolabs.fr
Chair, ZOO-Project PSC

___
ZOO-discuss mailing list
ZOO-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

[Zoo-discuss] ZOO-Project 2.0.0-rc1 has been released!

2024-02-17 Thread Gérald Fenoy via ZOO-discuss 
Dear community,
As the current release manager, I announce the ZOO-Project version 2.0.0 
release candidate 1.

The release contains new features and fixes listed below.

The ZOO-Project has been accepted as part of the Docker-Sponsored Open Source 
Program [1]. You can now find various Docker images with different flavors on 
DockerHub [2] under the ZOO-Project organization [3].

This release introduces the support for OGC API - Processes - Part 2: Deploy, 
Replace, Undeploy draft specification [4] (DRU). You may be interested in the 
ZOO-Project-DRU Helm Chart [5] published in a dedicated GitHub repository: 
ZOO-Project/charts [6] for deploying the solution with the DRU and CWL support 
on Kubernetes. The EOEPCA project [7] supported the development of the DRU with 
CWL. The ZOO-Project's HPC support has been updated to enable the *deployment* 
and execution of Singularity containers on remote HPC. The following 
Engineering Report [8] documents the implementation resulting from the 
Testbed19 HPGC activity. The ZOO-Project provides a dedicated Docker image 
named MDL4EO [9] with OTBTF [10] support (the original OTBTF Docker image [11] 
has proven to be working with the HPC support).


New Features and Fixes:

  * Update relation type to monitor for the status location.
  * Add support for the conformance class remote processes from the
  OGC API - Processes - Part 3: Workflow & chaining. Execution of
  remote processes are automatically run asynchronously in case the
  root process was invoked asynchronously.
  * Parse the Location header from ulinet and the cookie if any.
  * Add schemas to the components and support description stored in the file.
  * Add a trivial DeployOnHpc service for automating the installation
  and the deployment of a singularity container using the image
  parameter provided in the executionUnit used when deploying the
  process.
  * Set the key json_response_object with the JSON response that the
  ZOO-Kernel produced for the request, it can be updated from a
  filter_out process.
  * Update filter_in to support returning a response directly by
  adding a response key in the lenv section (binary is supported for
  this response)
  * Provide an initial Dockefile dedicated to the DRU support with
  remote HPC execution support
  * Add a USE_HPC_NESTEDOUTPUTS build option to activate the nested
  inputs and outputs addition (not supported with OGC API - Processes - Part 1: 
Core)
  * Update C-API errorException and printExceptionResponse* signatures
  to handle the main configuration maps memory properly  
  *  Build Docker image with DRU supporting OpenEO UDP encoding 
  * Add support for deploying and executing OpenEO User Defined
  Processes by using an OpenEO graph for the executionUnit
  * Add support for schema type string for request body, providing a
  way to include CWL example files in the published OpenAPI
  * Integrate the OGC API - Processes - Part 2: Deploy, Replace,
  Undeploy optional support.
  * Build Docker image based on MDL4EO/OTBTF and the onnx runtime for
  models sharing
  * Integrate the TeamEngine and ETS for OGC API - Processes
  * Add JWT parser in security_service.py as filter_in to allocate
  resources per authenticated user
  * Integrate the work done during GSoC 2022 to support Node.js
  ZOO-Services (cf. updated documentation for NodeJS)
  * Update support to filter the jobs list using the user_id
  * Add support for nested processes n OGC API - Processes - Part 3: 
  Workflows & Chaining
  * Add filter_in and filter_out service array to be invoked previously
  of and after the service run
  * Add trivial support for OpenAPI security, basicAuth / openId, and add
  sample services implementation
  * Add support for MapServer 8.0 (actually 7.7-dev), including
  returning result as OGC API -Features
  * Integrate downloading MapServer 8.0 and building from the
  dedicated Dockerfile-MS8
  * Include basicAuth build instructions in the Dockefile
  * Add basicAuth service illustrating how to secure access to OGC API - 
Processes using Basic Authentication
  * Use the osecurity section to detect secured path, request method
  from the published OpenAPI
  * Update the printHeaders function to allow Status definition at runtime
  * Add a [osecurity] section to secure access to path, method couple
  from the published OpenAPI
  * Update the database connection handling to make it independent from
  instantiation order
  * Use the RabbitMQ also for OGC API - Processes
  * Pass the subscriber if any is passed from the original request
  * Make C OGR base-vect-ops compatible with memory=protect
  * Add volumes to be shared by the ZOO-Kernel and the ZOO-FPM
  * Add a RabbitMQ and a ZOO-FPM container to docker-compose
  * Add documentation for RabbitMQ support and ZOO Fast Process
  Manager (ZOO-FPM)
  * Optional use of ZOO-Kernel Fast Process Manager backends to handle
  asynchronous execution  
  * Partial integration of the code from the

[Zoo-discuss] ZOO-Project has graduated

2023-06-22 Thread Gérald Fenoy 
Dear all,
It is a great pleasure for me to come to you today to announce a great 
achievement for the ZOO-Project.

With the OSGeo board approval, the ZOO-Project is now officially an OSGeo 
Project. 

I would like to thanks the PSC members for their active support during the 
incubation period and their patience.

We would also like to thank the community for their support all over the years.

We invite everyone in the community to update the documentation were needed and 
push the information about incubation status on different communication 
channels to celebrate this great achievement.

We hope that everyone can celebrate this great event.

Best regards,



Gerald Fenoy
Chair, ZOO-Project PSC

___
ZOO-discuss mailing list
ZOO-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

[Zoo-discuss] OGC-OSGeo-ASF Code Sprint 2023 report

2023-05-15 Thread Gérald Fenoy 
Dear all,
You can find here: [1] the report about my participation in the OGC-OSGeo-ASF 
Code Sprint in Lausanne from April 25th to 27th.

Any feedbacks, remarks, or requests for modification are welcome.

I hope you enjoy the read.

Best regards,

[1] 
https://github.com/ZOO-Project/ZOO-Project/wiki/OGC-ASF-OSGeo_Code_Sprint_Report

Gerald Fenoy
Chair, ZOO-Project PSC

___
ZOO-discuss mailing list
ZOO-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

[Zoo-discuss] Fwd: [ZOO-Discuss] ZOO-Project Developper call for agreement

2022-11-29 Thread Gérald Fenoy 
Hi all,
This is simply a copy of a very old email 2013 where contributors agreed on the 
commuter guidelines.

I cannot found it on the list archive.

Best regards,

Gerald Fenoy
Chair, ZOO-Project PSC

> Début du message réexpédié :
> 
> De: "Clarke, Trevor" 
> Objet: Rép. : [ZOO-Discuss] ZOO-Project Developper call for agreement
> Date: 2 juillet 2013 à 16:51:50 UTC+2
> À: 
> 
> Accepted and agreed.
> 
> --
> Trevor R.H. Clarke
> Software Engineer, Ball Aerospace
> (937)320-7087
> 
> 
>> -Original Message-
>> From: Fenoy Gérald [mailto:gfe...@gmail.com]
>> Sent: Tuesday, July 02, 2013 8:51 AM
>> To: Angelos Tzotsos; Clarke, Trevor; David Saggiorato; Jeff McKenna; Luca
>> Delucchi; Markus Neteler; Ren√(c)-Luc D'Hont; marco.negre...@polimi.it
>> Subject: ZOO-Project Developper call for agreement
>> 
>> Dear ZOO-Project commiters,
>> I would like to ask you to send a short email on the ZOO-Discuss mailing list
>> saying that you reviewed and agreed on the ZOO-Project Commiter
>> Guidelines available at [1].
>> 
>> I wish to get your confirmation as soon as possible as I would like to 
>> release
>> rc2 quickly and it will depend on your confirmation.
>> 
>> Hope to hear back from you,
>> Best regards,
>> 
>> Gérald Fenoy
>> ZOO-Project Developper
>> 
>> [1]  http://zoo-project.org/docs/community/developper.html
> 
> 
> 
> This message and any enclosures are intended only for the addressee.  Please 
> notify the sender by email if you are not the intended recipient.  If you are 
> not the intended recipient, you may not use, copy, disclose, or distribute 
> this 
> message or its contents or enclosures to any other person and any such 
> actions 
> may be unlawful.  Ball reserves the right to monitor and review all messages 
> and enclosures sent to or from this email address.
> ___
> Zoo-discuss mailing list
> zoo-disc...@gisws.media.osaka-cu.ac.jp
> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo.cgi/zoo-discuss

___
ZOO-discuss mailing list
ZOO-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

[Zoo-discuss] Fwd: [ZOO-Discuss] ZOO-Project Developper call for agreement

2022-11-29 Thread Gérald Fenoy 
Hi all,
This is again a copy of a very old email 2013 where contributors agreed on the 
commuter guidelines.

I cannot found it on the list archive.

Best regards,



Gerald Fenoy
Chair, ZOO-Project PSC

> Début du message réexpédié :
> 
> De: David Saggiorato 
> Objet: Rép. : [ZOO-Discuss] ZOO-Project Developper call for agreement
> Date: 2 juillet 2013 à 16:58:56 UTC+2
> À: zoo-disc...@gisws.media.osaka-cu.ac.jp
> 
> Accepted and agreed.
> 
> 
> David Saggiorato - CLEOLYS SARL - Tel: 0678983530
> 
> 
> 
> 
> Le 2 juil. 2013 à 14:50, Fenoy Gérald a écrit :
> 
>> Dear ZOO-Project commiters,
>> I would like to ask you to send a short email on the ZOO-Discuss mailing 
>> list saying that you reviewed and agreed on the ZOO-Project Commiter 
>> Guidelines available at [1].
>> 
>> I wish to get your confirmation as soon as possible as I would like to 
>> release rc2 quickly and it will depend on your confirmation. 
>> 
>> Hope to hear back from you,
>> Best regards,
>> 
>> Gérald Fenoy
>> ZOO-Project Developper
>> 
>> [1] http://zoo-project.org/docs/community/developper.html
>> 
> 
> ___
> Zoo-discuss mailing list
> zoo-disc...@gisws.media.osaka-cu.ac.jp
> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo.cgi/zoo-discuss

___
ZOO-discuss mailing list
ZOO-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

[Zoo-discuss] 2022 OGC-OSGeo-ASF Code Sprint report

2022-03-15 Thread Gérald Fenoy 
Hello everyone,
I am glad to provide a short report about the ZOO-Proect participation during 
this year OGC-OSGeo-ASF Code Sprint.

Number of people from various organisations including the OGC, the OSGeo and 
the ASF gathered during three days, from March 8th to 10th 2022,  to make a 
joint effort in exploring and investigating the various standards available.

On the ZOO-Project specific side, as you already know, we had published an 
ideas page [1] for this code sprint. As always, we had many goals but we cannot 
get all of them accomplished only some, some partially, and for some in which 
we have made big progresses in, we realized that it may have been a wrong way 
to go.

Anyway, let start with the bright side. First of all, the first idea [2] has 
been partially implemented. Meaning that asynchronous requests are now 
effectively using RabbitMQ if there is any available. The last point, which is 
considering the use of such a mechanism in case of synchronous request, we 
evaluated that the current implementation would require significant 
modifications and refactoring for handling synchronous request as asynchronous 
per default. In addition, it would add new steps in the processing implying the 
run to take longer that it does now. On the other hand, it would add advantages 
amongst which, we can mention the ability to be able to return a statusInfo of 
the service in case the execution take longer than a predefined threshold that 
we may add to the main.cfg or the client would be able to send within a 
dedicated header parameter associated with the request. This has been discussed 
in the OGC API - Processes SWG already and this would be a way for us to 
support this new functionality in case it become a requirement.

The second idea [3] in the list was also considered during the code sprint 
period, and I would like to personally thanks Blasco Brauzzi for joining the 
Code Sprint and helping us in various way. First of all, he did help me for 
setting up properly on my platform the ADES software and get it working 
properly until the stage-out phase which was the one on which we get blocked. 
But once the min.io S3 bucket was correctly setup and access to it from other 
pods used by the ADES platform correctly configured, then this step was also 
working. So, as it is greatly explained on their GitHub repo [4], the ADES 
platform gives you the opportunity to deploy (and undeploy) new services then 
execute them. These services are written in Common Workflow Language (CWL), 
when a client trigger the execution of the CWL « execution unit » (so, a 
service) ADES do create a namespace with dedicated pods inside it for executing 
every steps of the service. In case, there are operation that may be run in 
parallel, then the pods are started at the same time and the execution can run 
in parallel. Obviously, once the service execution ended, the pods and 
dedicated namespace is automatically removed by ADES. I would like to mention 
that I am impressed by the capability offered out of the box by the ADES 
platform.

Still about this third idea, Blasco have implemented the support for automatic 
workspace creation relying on a shell script and made it available from here 
[5] in the feature/user-services branch. By investigating this new feature we 
realized that it may be better to use a similar mechanism but that would not 
rely on the use of the external shell script but on a directory that would be 
considerate as a skeleton for creation of the new workspaces. Something very 
similar to what is used on Unix and GNU/Linux platform when you create a new 
user and specify a directory to be used as a model for creating the new home 
directory. We expect this new feature to be available in the coming weeks.

About the third idea [6], we did not have enough time to work actively on this. 
Nevertheless, we have detected some issues in the answer provided by the 
ZOO-Kernel for the execute request [7], we have extras keys that are not 
required. So, this has proven that some minimal testing of the OGC API - 
Processes would be a real asset to the project helping us to detect issues when 
they are inserted in the code as it is the case for WPS already. So, this is a 
target we should keep in mind and planned for future work items.

For the forth idea [8], we have started by creating a new Dockerfile adding the 
MapServer latest version available on the official GitHub repository [9]. 
Nevertheless, by doing so, we realized that when you are willing to use OGC API 
- Feature, you should use a simplified URLs such as /mapserv/MyMap/ogcapi/ 
where MyMap should point to the full path of the corresponding MapServer’s 
mapfile as an entry in the /etc/mapserver.conf (cf. RFC 135 [10]). So, it was a 
requirement for being able to publish outputs as OGC API - Features, to be able 
to update the mapserver.conf by adding a new entry for all the created 
mapfiles. We tried locally to modify the Mapserver source code

[Zoo-discuss] OGC OSGeo ASF Code Sprint

2022-03-07 Thread Gérald Fenoy 
Dear all,
I would like to remind you that tomorrow is the first day of the 2022 OGC OSGeo 
ASF Code Sprint.

I hope you will be able to register [1] and to join us for the tasks [2] we 
have identified to be handled during this 3 days Code Sprint.

In case you have other ideas and you want them to be added to the list, please 
feel free to add them to the GitHub repository specifically made available by 
the organizers [3].

Wishing all the best to everyone.

Best regards,

[1] https://portal.ogc.org/public_ogc/register/220225asf_codesprint.php
[2] 
https://github.com/GeoLabs/developer-events/tree/master/2022/Joint-OGC-OSGeo-ASF-Code-Sprint%202022/ideas/ZOO-Project
[3] https://github.com/opengeospatial/developer-events


Gerald Fenoy
Chair, ZOO-Project PSC

___
ZOO-discuss mailing list
ZOO-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

Re: [OSGeo-Discuss] [GSoC 2022 - Call for Project Ideas] Final Extension in Deadline for Submitting Ideas Page | New Deadline - Feb 19, 2022 1800 UTC

2022-02-19 Thread Gérald Fenoy via Discuss 
Dear All,
You can find the ZOO-Project ideas for this year Google Summer of Code in the 
link bellow.

https://github.com/ZOO-Project/ZOO-Project/wiki/Google-Summer-of-Code-2022-Project-Ideas

Thanks a lot for the effort Rajat!

Best regards,

Gerald Fenoy
Chair, ZOO-Project PSC

> Le 18 févr. 2022 à 16:38, Rajat Shinde via Discuss  
> a écrit :
> 
> Dear All,
> 
> We are extending the deadline till February 19th, 2022 1800 UTC. Please note 
> that this is the final extension. We sincerely hope to receive your Project 
> ideas page for the GSoC 2022 with OSGeo.
> 
> Thank you.
> Kind regards,
> OSGeo GSoC Admins Team
> 
> On Thu, Feb 10, 2022 at 8:42 PM Rajat Shinde  > wrote:
> Dear All,
> 
> This is regarding our earlier call for project ideas for Google Summer of 
> Code 2022 with OSGeo [1]. Please note that we are extending the deadline to 
> share the URL to the project ideas page by February 16, 2022.
> 
> Please follow [1] for instructions on preparing the Project ideas page.
> 
> (PS: Org Application period has already started (February 7, 2022 onwards) 
> and shall be open till February 21, 2022. Kindly share the news in your 
> project community. Thanks.)
> 
> As always, please feel free to reach us for further queries.
> 
> Stay safe!
> Kind regards,
> OSGeo GSoC Administration Team
> 
> [1] https://lists.osgeo.org/pipermail/announce/2022-January/000585.html 
> ___
> Discuss mailing list
> Discuss@lists.osgeo.org 
> https://lists.osgeo.org/mailman/listinfo/discuss 
> 
___
Discuss mailing list
Discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss

[Zoo-discuss] ZOO-Project 1.9.0 release

2022-02-01 Thread Gérald Fenoy 
Dear all,
I am pleased to announce the publication of the ZOO-Project 1.9.0 release.

You can see the release note and download the source archives from here [1], 
[2].

Don’t hesitate to share your experience on the mailing list, to report bugs 
using the GitHub issue tracking [3] or, to request for new feature [4].

Best regards,

[1] https://github.com/ZOO-Project/ZOO-Project/releases/tag/rel-1.9.0
[2] https://zenodo.org/record/5940464#.YflhofXMJzU
[3] 
https://github.com/ZOO-Project/ZOO-Project/issues/new?assignees==bug=bug_report.md=
[4] 
https://github.com/ZOO-Project/ZOO-Project/issues/new?assignees==enhancement=feature_request.md=

Gerald Fenoy
Chair, ZOO-Project PSC

___
ZOO-discuss mailing list
ZOO-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

Re: [Zoo-discuss] ZOO-Project 1.9.0 release candidate 1

2022-01-28 Thread Gérald Fenoy 
With the following missing references form the previous mail:

[1] 
https://github.com/ZOO-Project/ZOO-Project/commit/581b8532d4f3bd4480c34adcd9e53ae70b08f3ab
[2] https://github.com/ZOO-Project/ZOO-Project/issues/11#issuecomment-1024181397

Gerald Fenoy
Chair, ZOO-Project PSC


> Le 28 janv. 2022 à 13:52, Gérald Fenoy  a écrit :
> 
> Dear Jeff,
> Thanks a lot for your feedbacks.
> 
> I used the GitHub Release to publish previous versions of the ZOO-Project and 
> the brand new 1.9.0-rc1. I updated the corresponding documentation section 
> [1] and updated the associated ticket [2].
> 
> Best regards
> 
> 
> Gerald Fenoy
> Chair, ZOO-Project PSC
> 
>> Le 25 janv. 2022 à 20:15, Jeff McKenna > <mailto:jmcke...@gatewaygeomatics.com>> a écrit :
>> 
>> Dear Gérald,
>> 
>> Thank-you for this effort.
>> 
>> Please also add to your release process: creating the RC & releases at 
>> https://github.com/ZOO-Project/ZOO-Project/releases 
>> <https://github.com/ZOO-Project/ZOO-Project/releases>
>> 
>> (for example, I like how GRASS GIS team lists the release candidates at 
>> https://github.com/OSGeo/grass/releases 
>> <https://github.com/OSGeo/grass/releases>   Or you can see how I do it at 
>> https://github.com/MapServer/MapServer/releases 
>> <https://github.com/MapServer/MapServer/releases> )
>> 
>> Once you click the "Create a new release" button there, then GitHub 
>> automagically notifies the repository's "followers".
>> 
>> Thanks,
>> 
>> -jeff
>> 
>> 
>> 
>> -- 
>> Jeff McKenna
>> GatewayGeo: Developers of MS4W, MapServer Consulting and Training
>> co-founder of FOSS4G
>> http://gatewaygeo.com/ <http://gatewaygeo.com/>
>> 
>> 
>> 
>> On 2022-01-25 2:56 p.m., Gérald Fenoy wrote:
>>> Dear community,
>>> As Release Manager, I am glad to announce the publication of the 
>>> ZOO-Project 1.9.0 release candidate 1.
>>> It can be downloaded from here [1].
>>> This new ZOO-Project release contains new features but also fixes.
>>> In November 2021, the Open Geospatial Consortium approved the OGC API - 
>>> Processes (Part 1: Core) standard. The new ZOO-Project release supports 
>>> this newly approved version. The MapServer support was integrated with this 
>>> new standard, even if the output data are only available through WMS, WFS 
>>> and WCS OGC standards, by now (see issue #1 [2]).
>>> =-= New Features and Fixes =-=
>>> * Update ZOO-Kernel internal messages natural languages po files
>>> * Fix issue with synchronous execution from the HTML UI when requesting 
>>> something else than raw data output.
>>> * Add support for natural languages to be available within the 
>>> docker-compose setup.
>>> * Add support for automatic natural languages support.
>>> * Add getValueFromMaps function the C-API to be used from C services 
>>> requiring to be functional in every memory management mode (load or 
>>> protected)
>>> * Add support for datetime parameter for jobs filtering as defined in OGC 
>>> API - Processes.
>>> * Add support for type parameter for jobs filtering as defined in OGC API - 
>>> Processes.
>>> * Add support for minDuration and maxDuration parameters for jobs filtering 
>>> as defined in OGC API - Processes.
>>> * Change the table structure for storing ongoing execution status 
>>> informations to add required field for outputing correct statusInfo.
>>> * Addition in the C-API: function addToMapA, in case there is already a 
>>> value, then the value is appended to the string and values are coma 
>>> separated (reason of the change: support for filtering using processId and 
>>> status in OGC API - Processes).
>>> * Add support for filtering using array of string the jobs list from OGC 
>>> API - Processes using processId or status parameter
>>> * Change docker-compose to use binary docker image published from GitHub 
>>> action.
>>> * Minor updates in docker-compose to target the right arch and potentially 
>>> cross compile in case you run from another arch
>>> * Get back the MapServer automatic publication of outputs/results through 
>>> OGC Web Services (WMS, WFS, and WCS)
>>> * Update the Basic HTML UI to use the Prefer header in case the execution 
>>> scenario requires to run the execute request asyncrhonously
>>> * Support the Prefer header for choosing between execution mode scenarios 
>>> which

Re: [Zoo-discuss] ZOO-Project 1.9.0 release candidate 1

2022-01-28 Thread Gérald Fenoy 
Dear Jeff,
Thanks a lot for your feedbacks.

I used the GitHub Release to publish previous versions of the ZOO-Project and 
the brand new 1.9.0-rc1. I updated the corresponding documentation section [1] 
and updated the associated ticket [2].

Best regards


Gerald Fenoy
Chair, ZOO-Project PSC

> Le 25 janv. 2022 à 20:15, Jeff McKenna  a 
> écrit :
> 
> Dear Gérald,
> 
> Thank-you for this effort.
> 
> Please also add to your release process: creating the RC & releases at 
> https://github.com/ZOO-Project/ZOO-Project/releases 
> <https://github.com/ZOO-Project/ZOO-Project/releases>
> 
> (for example, I like how GRASS GIS team lists the release candidates at 
> https://github.com/OSGeo/grass/releases 
> <https://github.com/OSGeo/grass/releases>   Or you can see how I do it at 
> https://github.com/MapServer/MapServer/releases 
> <https://github.com/MapServer/MapServer/releases> )
> 
> Once you click the "Create a new release" button there, then GitHub 
> automagically notifies the repository's "followers".
> 
> Thanks,
> 
> -jeff
> 
> 
> 
> -- 
> Jeff McKenna
> GatewayGeo: Developers of MS4W, MapServer Consulting and Training
> co-founder of FOSS4G
> http://gatewaygeo.com/ <http://gatewaygeo.com/>
> 
> 
> 
> On 2022-01-25 2:56 p.m., Gérald Fenoy wrote:
>> Dear community,
>> As Release Manager, I am glad to announce the publication of the ZOO-Project 
>> 1.9.0 release candidate 1.
>> It can be downloaded from here [1].
>> This new ZOO-Project release contains new features but also fixes.
>> In November 2021, the Open Geospatial Consortium approved the OGC API - 
>> Processes (Part 1: Core) standard. The new ZOO-Project release supports this 
>> newly approved version. The MapServer support was integrated with this new 
>> standard, even if the output data are only available through WMS, WFS and 
>> WCS OGC standards, by now (see issue #1 [2]).
>> =-= New Features and Fixes =-=
>> * Update ZOO-Kernel internal messages natural languages po files
>> * Fix issue with synchronous execution from the HTML UI when requesting 
>> something else than raw data output.
>> * Add support for natural languages to be available within the 
>> docker-compose setup.
>> * Add support for automatic natural languages support.
>> * Add getValueFromMaps function the C-API to be used from C services 
>> requiring to be functional in every memory management mode (load or 
>> protected)
>> * Add support for datetime parameter for jobs filtering as defined in OGC 
>> API - Processes.
>> * Add support for type parameter for jobs filtering as defined in OGC API - 
>> Processes.
>> * Add support for minDuration and maxDuration parameters for jobs filtering 
>> as defined in OGC API - Processes.
>> * Change the table structure for storing ongoing execution status 
>> informations to add required field for outputing correct statusInfo.
>> * Addition in the C-API: function addToMapA, in case there is already a 
>> value, then the value is appended to the string and values are coma 
>> separated (reason of the change: support for filtering using processId and 
>> status in OGC API - Processes).
>> * Add support for filtering using array of string the jobs list from OGC API 
>> - Processes using processId or status parameter
>> * Change docker-compose to use binary docker image published from GitHub 
>> action.
>> * Minor updates in docker-compose to target the right arch and potentially 
>> cross compile in case you run from another arch
>> * Get back the MapServer automatic publication of outputs/results through 
>> OGC Web Services (WMS, WFS, and WCS)
>> * Update the Basic HTML UI to use the Prefer header in case the execution 
>> scenario requires to run the execute request asyncrhonously
>> * Support the Prefer header for choosing between execution mode scenarios 
>> which can be sync/async and raw/document
>> * Add support for multiple output requested as Raw for OGC API - Processes 
>> (why not backport this in WPS?)
>> * Automatically add the old format of metadata informations to the inputs 
>> and outputs to not require a single modification within your existing 
>> services
>> * Update the Basic HTML UI to try to conform to version 1.0-draft.6
>> * Modify both the request parser and response printer functions from the 
>> C-API to conform to version 1.0-draft.6
>> * Support both the old array of inputs / outputs syntax and the one defined 
>> in the draft 1.0-draft.6 (array of inputs for the new syntax may not work as 
>> expected)
>> * Move jobs to

[Zoo-discuss] ZOO-Project 1.9.0-rc1 release candidate 1

2022-01-25 Thread Gérald Fenoy 
Dear community,
As Release Manager, I am glad to announce the publication of the ZOO-Project 
1.9.0 release candidate 1.

It can be downloaded from here [1].

This new ZOO-Project release contains new features but also fixes.

In November 2021, the Open Geospatial Consortium approved the OGC API - 
Processes (Part 1: Core) standard. The new ZOO-Project release supports this 
newly approved version. The MapServer support was integrated with this new 
standard, even if the output data are only available through WMS, WFS and WCS 
OGC standards, by now (see 
[#1](https://github.com/ZOO-Project/ZOO-Project/issues/1)).

=-= New Features and Fixes =-=

* Update ZOO-Kernel internal messages natural languages po files
* Fix issue with synchronous execution from the HTML UI when requesting 
something else than raw data output.
* Add support for natural languages to be available within the docker-compose 
setup.
* Add support for automatic natural languages support.
* Add getValueFromMaps function the C-API to be used from C services requiring 
to be functional in every memory management mode (load or protected)
* Add support for datetime parameter for jobs filtering as defined in OGC API - 
Processes.
* Add support for type parameter for jobs filtering as defined in OGC API - 
Processes.
* Add support for minDuration and maxDuration parameters for jobs filtering as 
defined in OGC API - Processes.
* Change the table structure for storing ongoing execution status informations 
to add required field for outputing correct statusInfo.
* Addition in the C-API: function addToMapA, in case there is already a value, 
then the value is appended to the string and values are coma separated (reason 
of the change: support for filtering using processId and status in OGC API - 
Processes).
* Add support for filtering using array of string the jobs list from OGC API - 
Processes using processId or status parameter
* Change docker-compose to use binary docker image published from GitHub action.
* Minor updates in docker-compose to target the right arch and potentially 
cross compile in case you run from another arch
* Get back the MapServer automatic publication of outputs/results through OGC 
Web Services (WMS, WFS, and WCS)
* Update the Basic HTML UI to use the Prefer header in case the execution 
scenario requires to run the execute request asyncrhonously
* Support the Prefer header for choosing between execution mode scenarios which 
can be sync/async and raw/document
* Add support for multiple output requested as Raw for OGC API - Processes (why 
not backport this in WPS?)
* Automatically add the old format of metadata informations to the inputs and 
outputs to not require a single modification within your existing services
* Update the Basic HTML UI to try to conform to version 1.0-draft.6
* Modify both the request parser and response printer functions from the C-API 
to conform to version 1.0-draft.6
* Support both the old array of inputs / outputs syntax and the one defined in 
the draft 1.0-draft.6 (array of inputs for the new syntax may not work as 
expected)
* Move jobs to root and use /processes/{processID} as execute endpopint
* Make all demos running within docker (including SAGA and OTB)
* Deploy demo HTML UI from github from the Dockerfile
* Add demo ZOO-Services build in the Dockerfile

Please report any issue you may have using this version.

In case no issue is reported in the 7 upcoming days, we will approve this 
release candidate.

Have great time with it!

Best regards,

[1] http://zoo-project.org/new/Code/Download

Gerald Fenoy
Chair, ZOO-Project PSC

___
Zoo-discuss mailing list
Zoo-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

[Zoo-discuss] ZOO-Project 1.9.0 release candidate 1

2022-01-25 Thread Gérald Fenoy 
Dear community,
As Release Manager, I am glad to announce the publication of the ZOO-Project 
1.9.0 release candidate 1.

It can be downloaded from here [1].

This new ZOO-Project release contains new features but also fixes.

In November 2021, the Open Geospatial Consortium approved the OGC API - 
Processes (Part 1: Core) standard. The new ZOO-Project release supports this 
newly approved version. The MapServer support was integrated with this new 
standard, even if the output data are only available through WMS, WFS and WCS 
OGC standards, by now (see issue #1 [2]).

=-= New Features and Fixes =-=

* Update ZOO-Kernel internal messages natural languages po files
* Fix issue with synchronous execution from the HTML UI when requesting 
something else than raw data output.
* Add support for natural languages to be available within the docker-compose 
setup.
* Add support for automatic natural languages support.
* Add getValueFromMaps function the C-API to be used from C services requiring 
to be functional in every memory management mode (load or protected)
* Add support for datetime parameter for jobs filtering as defined in OGC API - 
Processes.
* Add support for type parameter for jobs filtering as defined in OGC API - 
Processes.
* Add support for minDuration and maxDuration parameters for jobs filtering as 
defined in OGC API - Processes.
* Change the table structure for storing ongoing execution status informations 
to add required field for outputing correct statusInfo.
* Addition in the C-API: function addToMapA, in case there is already a value, 
then the value is appended to the string and values are coma separated (reason 
of the change: support for filtering using processId and status in OGC API - 
Processes).
* Add support for filtering using array of string the jobs list from OGC API - 
Processes using processId or status parameter
* Change docker-compose to use binary docker image published from GitHub action.
* Minor updates in docker-compose to target the right arch and potentially 
cross compile in case you run from another arch
* Get back the MapServer automatic publication of outputs/results through OGC 
Web Services (WMS, WFS, and WCS)
* Update the Basic HTML UI to use the Prefer header in case the execution 
scenario requires to run the execute request asyncrhonously
* Support the Prefer header for choosing between execution mode scenarios which 
can be sync/async and raw/document
* Add support for multiple output requested as Raw for OGC API - Processes (why 
not backport this in WPS?)
* Automatically add the old format of metadata informations to the inputs and 
outputs to not require a single modification within your existing services
* Update the Basic HTML UI to try to conform to version 1.0-draft.6
* Modify both the request parser and response printer functions from the C-API 
to conform to version 1.0-draft.6
* Support both the old array of inputs / outputs syntax and the one defined in 
the draft 1.0-draft.6 (array of inputs for the new syntax may not work as 
expected)
* Move jobs to root and use /processes/{processID} as execute endpopint
* Make all demos running within docker (including SAGA and OTB)
* Deploy demo HTML UI from github from the Dockerfile
* Add demo ZOO-Services build in the Dockerfile

Please report any issue you may have using this version.

In case no issue is reported in the 7 upcoming days, we will approve this 
release candidate.

Best regards,

[1] http://zoo-project.org/new/Code/Download 

[2] https://github.com/ZOO-Project/ZOO-Project/issues/1 


Gerald Fenoy
Chair, ZOO-Project PSC

___
Zoo-discuss mailing list
Zoo-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

[Zoo-discuss] ZOO-Project's Christmass gifts

2021-12-08 Thread Gérald Fenoy 
Dear ZOO-Project community,
As a PSC chair I come here today to call for volunteers to make a Christmas 
gift to the ZOO-Project development team.

During the development years, the number of ZOO-Kernel internal messages 
increased and some existing message were modified. 

So, we would need help from you, the volunteers, to translate the ZOO-Kernel 
internal messages in your language.

Please refer to this section of the documentation [1] on how to contribute 
translation.

Best regards,


[1] https://zoo-project.github.io/docs/contribute/translate.html

 
___
Zoo-discuss mailing list
Zoo-discuss@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/zoo-discuss

[OSGeo-Discuss] RE : Re: OSGEO4W future

2013-09-20 Thread Gérald Fenoy 
Dear all, 
Despite I agree with you that providing the OSGeo softwares in a binary 
distribution is a good idea, what do you think of providing something, which 
may be IMO even better to the end users / developpers, let's call it a build 
kit or a build environment already correctly setup for integration of new 
versions of software or even the integration of this or that new software. I 
really think that it make lot of sense to provide such a thing. 

This way, any new projects become able to provide a windows version (x64 or 
i386, I'm not sure we should provide only x64 versions even it will be the most 
used, but this is another question) of their software without having to do all 
the work on their own as so many of us did /do already.

Let suppose that you find a bug in this or that software but you get a patch 
provided by the OSGeo community (whatever is the project name!), then this 
patch can be easilly applied on the current build environment and user / devs 
are able to try the result directly.

Nevertheless, I understand that it is huge work, but cannot we plan to get thz 
work done in a similar manner than the OSGeoLiveDVD was built. Let say by 
asking for volonteers to handle a specific project.

It was something I spoke about here and there (conferences mainly) as a key 
missing thing, so I thought that as you put this discussion on table it was 
perfect timming to share my thoughts on this.

Waiting for your input and comments.

If this sounds totally irrealisitic please let me say that it is not.

Best regards.

Gėrald Fenoy
http://www.osgeo.org



 Message d'origine 
De : Alex Mandel tech_...@wildintellect.com 
Date : 20/09/2013  22:52  (GMT+00:00) 
A : Tamas Szekeres szeker...@gmail.com,Paolo Cavallini 
cavall...@faunalia.it 
Cc : OSGeo Discussions discuss@lists.osgeo.org,OSGeo-Board 
bo...@lists.osgeo.org 
Objet : Re: [OSGeo-Discuss] OSGEO4W future 
 
On 09/20/2013 02:45 PM, Tamas Szekeres wrote:
 2013/9/20 Paolo Cavallini cavall...@faunalia.it
 
 I suggest to make a Steering Committee
 for OSGEO4W, so to have a clear roadmap, and give Windows (urgh!)
 users a predictable environment. I think some of our million users
 would be happy to support this effort, if they would know they
 contribute actively to something they need.

 
 
 Hi Paolo,
 
 I agree with you entrirely, as we've already been talking about this today.
 Being committed to provide usable binaries on Windows, you can count me in.
 Setting up a build environment (probably a version of a Windows Server x64
 edition with MSVC2010 for instance) providing to compile all the stuff at
 the same place would be a prerequisite.
 
 
 Best regards,
 
 Tamas
 

I'm actually already providing such an instance and was planning to
clone it to several instances as well as a testing instance.
Frank has the keys to drive it and has been using it for several months
already.

It's part of my lab's participation in the ICA-OSGeo initiative.
http://geospatial.ucdavis.edu/resources/open-source

Thanks,
Alex

___
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] points of interest database

2013-01-23 Thread Gérald Fenoy 
Dear Dimitris, dear Raj,
is there any way to share this dump publicly and get a link ?

Waiting for your answer,
Best regards,

Gérald Fenoy
gerald.fe...@geolabs.fr


Le 23 janv. 2013 à 12:06, Dimitris Kotzinos kotz...@csd.uoc.gr a écrit :

 if you can send me a postgres/postgis dump, this would be extremely useful! 
 (thanks!).

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

Re: [OSGeo-Discuss] NEWS: Venkatesh Raghavan Receives 2012 Sol Katz Award

2012-10-25 Thread Gérald Fenoy 
Congratulations Venka for getting the Soltz Katz Award !

Congratulations to OSGeo for making this choice, choosing the place and an 
event which fit just perfectly i feel.

Gérald Fenoy
gerald.fe...@geolabs.fr

Le 25 oct. 2012 à 19:00, Jeff McKenna jmcke...@gatewaygeomatics.com a écrit :

 --
 
 Prof. Venkatesh Raghavan was honored today with the 2012 Sol Katz Award
 for Geospatial Free and Open Source Software during the inaugural
 session of the FOSS4G-India 2012 (http://lsi.iiit.ac.in/foss4gindia/)
 conference in Hyderabad, India. The
 award was presented by Ravi Kumar and Vundavallu Aruna Kumar, Member of
 Parliament.  Venka received a memento on behalf of the OSGeo-India Chapter.
 Venka's dedication to FOSS4G and his community work around the world,
 promoting open source geospatial, is second to none.  He has been
 involved in OSGeo since the foundation was formed in 2006, and we are
 lucky to have such a strong global voice in him.  The OSGeo foundation
 wishes to thank Venka for his wonderful dedication.
 
 Background
 
 The Sol Katz Award for Geospatial Free and Open Source Software is
 awarded annually by OSGeo to individuals who have demonstrated
 leadership in the GFOSS community. Recipients of the award will have
 contributed significantly through their activities to advance open
 source ideals in the geospatial realm. The hope is that the award will
 both acknowledge the work of community members, and pay tribute to one
 of its founders, for years to come.
 Sol Katz was an early pioneer of GFOSS and left behind a large body of
 work in the form of applications, format specifications, and utilities.
 In the early 80's, Sol assisted in the development of a public domain
 GIS package called MOSS (Map Overlay and Statistical System). This
 software was arguably the first open source GIS software in the world.
 Sol would later go on to release and maintain PC MOSS. He was also one
 of the first involved in public data translator utilities. Utilities
 that he developed for converting DEMs and reading SDTS files were
 contributed back to the geospatial community, and are still available
 today. Sol was also a frequent contributor to many geospatial list
 servers, providing much guidance to the geospatial community at large.
 Sol Katz's collection of GIS utilities at the BLM is still available at
 ftp://ftp.blm.gov/pub/gis/. Sadly, after fighting Non-Hodgkin's Lymphoma
 for almost a decade, Sol died April 23, 1999 in bed. His legacy will
 always live on in the GFOSS world.
 
 --
 
 
 ___
 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] [Zoo-discuss] Zoo in OSgeo

2012-08-06 Thread Gérald Fenoy 
Dear Frans,
we didi the migration of the old members to the new mailing list.

In fact in the mailing list system OSGeo put in place for us (and in all the 
mailing list system I know) there is no way to subscribe people, we only 
subscribe mail addresses. So this means that you're not subscribed as Frans 
Thamura but with only one email address. Which means also that if you are using 
another email address to write to the mailing list then you will receive an 
email  informing you that you're not subscribed which is totally normal.

I hope this make things more clear,
Best regards

Gérald Fenoy
gerald.fe...@geolabs.fr

Le 1 août 2012 à 22:08, Frans Thamura a écrit :

 just subscribe to Zoo Project , wow, now under osgeo.org;)
 
 congrat venka and team :0
 
 i cc the mailing list...
 
 NB: why dont migrate the old member to the mailing list, i must subscribe 
 again :)
 
 
 --
 Frans Thamura (曽志胜)
 Shadow Master and Lead Investor
 Meruvian.
 Integrated Hypermedia Java Solution Provider.
 
 Mobile: +628557888699
 Blog: http://blogs.mervpolis.com/roller/flatburger (id)
 
 FB: http://www.facebook.com/meruvian
 TW: http://www.twitter.com/meruvian / @meruvian
 Website: http://www.meruvian.org
 
 We grow because we share the same belief.
 ___
 Zoo-discuss mailing list
 zoo-disc...@lists.osgeo.org
 http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss

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

Re: [OSGeo-Discuss] Redirection to OSGeo Local Chapter web sites

2011-11-19 Thread Gérald Fenoy 
Dear all,
I think the same that SAC is not responsible for this domain
administration.

I think that some peoples remember that during the FOSS4G in Syndney
I amongst other already pointed out this situation. Indeed, during the FOSS4G 
2009 the situation was exactly the same. I also took advantage to be in Japan
with Arnulf in 2009 to mention one more time that the situation was this one.
Hopefully, some months after the link was corrected. At this moment, I thought
that it cannot be acceptable that a single company can take advantage of the 
OSGeo name this way.

Note that now, IMO it is perfectly acceptable to be represented by a company 
like the one which is currently accessible via the osgeo.eu link. As this 
company 
did, do and will do a lot for funding / promoting / being involved into OSGeo. 
This company is representative of OSGeo.

Nevertheless, I think that the page on which user arrive should not be a 
general 
presentation of the company but maybe the description of their involvement in 
OSGeo. I mean, a page more dedicated / specific to OSGeo. Honestly, if we look 
at the osgeo.eu page, the OSGeo logo looks lost amongst all the other logos 
(yes, it is here, the small one on your left).

I would like to insist on something here. As the osgeo.eu never got any web 
site,
I think that there was nothing done volontary here. I mean that I think that 
this is
only an error made by the guy which setup the new dns entries and that's it. Or
maybe I prefer to think that is the case ... I don't know :)

Anyway, I like a lot the Arnulf sentence published in 2009, I think it is good 
to 
keep it in mind and which say a lot : 

  OSGeo is nothing without you doing it.

Making OSGeo a redirection to a company can be one way, I don't know.
Nevertheless, it should imply some checking by OSGeo members to make sure 
that the pages pointed by osgeo.* are really dedicated to OSGeo. 

How to deal with other european companies which should appreciate to 
participate 
in the effort to promote OSGeo in €urope ... Things can become difficult if a 
single
company get the full access to the osgeo.eu domain and don't want to share it.
I'm sure that, in this case, this is not the subject, but if we are thinking in 
a general
level, we should notify this also. 

What about making all osgeo.* domains the OSGeo's property ? Then OSGeo SAC 
will be responsible to setup DNS for all the dedicated OSGeo sites ... Adding 
more 
work but provide more control over *our OSGeo name*. Community taking control
on its own name make sense to me.

Best regards,


Le 19 nov. 2011 à 02:23, Frank Warmerdam a écrit :

 Venka,
 
 If local chapters open a ticket with SAC, then I
 or others can setup a redirect from X.osgeo.org
 to another site.  I do not believe that OSGeo SAC
 controls the osgeo.eu site.  In fact our domain admin
 cannot generally do anything except the major
 domains (.com, .org, .net).
 
 Best regards,
 
 
 On Fri, Nov 18, 2011 at 5:19 PM, Venkatesh Raghavan
 ragha...@media.osaka-cu.ac.jp wrote:
 Dear All,
 
 Nice to see the OSGeo Local Chapter pages growing.
 We now have osgeo.jp, osgeo.kr, osgeo.cn, osgeo.in, osgeo.id,
 osgeo.eu and perhaps several more that I am not
 aware off.
 
 jp.osgeo.org redirects to Japan Local Chapter page
 (osgeo.jp) and it would be nice to see cn.osgeo.org,
 in.osgeo.org etc. redirecting to respective
 Local Chapter pages.
 
 Strangely, osgeo.eu redirects to camptocamp.com.
 I think osgeo.eu should redirect to a page showing
 a list of the very active Local Chapters that we have
 in the EU zone.
 
 Best
 
 Venka
 ___
 Discuss mailing list
 Discuss@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/discuss
 
 
 
 
 -- 
 ---+--
 I set the clouds in motion - turn up   | Frank Warmerdam, warmer...@pobox.com
 light and sound - activate the windows | http://pobox.com/~warmerdam
 and watch the world go round - Rush| Geospatial Software Developer
 ___
 Discuss mailing list
 Discuss@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/discuss

Gérald Fenoy
gerald.fe...@geolabs.fr

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

Re: [OSGeo-Discuss] Charter Member Nomination: Maning Sambale

2011-11-09 Thread Gérald Fenoy 
Dear Arnulf,
one more time I would like to thank you for this really good choice.

I get the honor to met Maning and listen his presentation in Tokyo this year,
during the talk I was impressed by his huge knowledge in many OSGeo technologies
and the way he used it.

I also think that he is really representative of OSGeo, indeed it is really a 
nice guy 
to speak with which is open to new ideas and get many interesting ideas he is 
open to 
share with other. I would like to say Open Mind :)

It is also really nice to see how he use OSGeo technologies in different way 
that 
lot of us are using it as he work in Philippines where network is not always 
available.

So I strongly recommend Maning Sambale to be elected as an OSGeo Charter Member
as he deserves to be not only for promoting but also using massively OSGeo 
software
to provide solutions for his country.

Best regards,

Le 9 nov. 2011 à 17:03, Seven (aka Arnulf) a écrit :

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Folks,
 I have the honor of nominating Maning Sambale [0] from the Phillippines
 as new OSGeo Charter Member.
 
 Maning works in a research institution [1] in the Philippines and is
 involved with environmental research with local marginalized
 communities. He uses all kinds of FOSS4G technologies in his day to day
 work and also promotes the use of Open Source geospatial tools among
 their local partners. Maning is active user of QGIS and GRASS and also
 an active community member of OSM.
 
 He is a founding member of the emerging OSGeo Philippines Local Chapter
 [2] hoping to become communities as vibrant as Japan and Korea among the
 Asian chapters. He will be a great addition to the Charter Membership
 bringing new perspectives to the community.
 
 Best regards,
 Arnulf
 
 [0] http://wiki.openstreetmap.org/wiki/User:Maning
 [1] http://www.essc.org.ph
 [2] http://wiki.osgeo.org/wiki/Philippines
 
 - -- 
 Exploring Space, Time and Mind
 http://arnulf.us
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
 iEYEARECAAYFAk66pEoACgkQXmFKW+BJ1b2magCfcamH0AB/w3MJk0l4FBeG9gZz
 jv4An0qWRg3GUSPCjvKxw8IPZWM9OThi
 =0q1S
 -END PGP SIGNATURE-
 ___
 Discuss mailing list
 Discuss@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/discuss

Gérald Fenoy
gerald.fe...@geolabs.fr

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

Re: [OSGeo-Discuss] Charter Member Nomination: Sanghee Shin

2011-11-08 Thread Gérald Fenoy 
Arnulf,
this is really good idea !

Thanks a lot for this nomination.

I had the pleasure to meet Sanghee Shin this week at FOSS4G Japan in Tokyo
and to listen his talk. Now, I know more about his massive contribution to 
promote 
OSGeo in Korea.

Hence, I am pleased to second this nomination.

Best regards,

Le 8 nov. 2011 à 09:19, Seven (aka Arnulf) a écrit :

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Folks,
 I have the pleasure of nominating Mr. Sanghee Shin [1] [2] from Korea as
 new OSGeo Charter Member.
 
 Sanghee has come a long way with Open Source, first using GRASS during
 his studies, later coming back to image processing and now using,
 promoting and developing it in his own company. He is founding member of
 the OSGeo Korean Local Chapter [3] [4] a  prominent organization with
 180 registered members (10-2011) and a lively community [5]. This year
 the Local Chapter presentes OSGeo with a booth at SmartKorea 2011 [6],
 the  Korean trade fair for geospatial software, data and surveying.
 Booth space and equipment was kindly provided by Mr. Shin's company
 GRIDA [7].
 
 This fall the OSGeo Local Chapter of Korea organized their first FOSS4G
 Local Chapter event [2] in Seoul, again under the lead of Sanghee.
 Mori-san, Yoshida-san from the FOSS4G Japan Local Chapter Chapter and
 myself were invited to give keynote presentations at the event with
 about 60 attendees and a dozen presentations about software, business
 models and use cases.
 
 Mr. Shin will be a great addition to the Charter Membership, invigorate
 our Asian connection and help to spread word and raise interest in our
 next FOSS4G in Beijing which is more or less just around the corner (at
 least seen from here...).
 
 
 Best regards,
 Arnulf
 
 [1] https://twitter.com/#!/endofcap
 [2] http://wiki.osgeo.org/wiki/User:Endofcap
 [3] Korean: http://www.osgeo.kr/
 [4] English: http://wiki.osgeo.org/wiki/Korea
 [5] http://groups.google.com/group/osgeo-kr/topics
 [6] http://grida.kr/en/business/business.html
 
 - -- 
 Exploring Space, Time and Mind
 http://arnulf.us
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
 iEYEARECAAYFAk645iUACgkQXmFKW+BJ1b23BgCdF1MezoNJXCe7pQTWvONFvLRD
 HAAAn0DTVRhmjngg0vNbiT6OZiFwWmHH
 =lDgo
 -END PGP SIGNATURE-
 ___
 Discuss mailing list
 Discuss@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/discuss

Gérald Fenoy
gerald.fe...@geolabs.fr

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

Re: [OSGeo-Discuss] Re: Board Nomination - Gérald Fenoy

2011-08-10 Thread Gérald Fenoy 
Dear all,
Sorry for so late reply get some painful hollidays issue ... 

First, I want to thank Jeff for this nomination to OSGeo board of directors.

Working for 7 years in web GIS development, OSGeo shown me the way to go. 
Indeed, I've always find, through OSGeo, an answer to my questions. Sometimes 
it was about searching for a solution to a specific problem, sometimes it was 
about the way to use specific software, sometimes it was about problem occuring 
using software. Anytime I had to ask, I can find quickly a solution by asking 
people from OSGeo all over the world using various kind of communication media. 
There is always somebody wake up at OSGeo, you can reach us. This is an 
impressive help for everybody which is using the software or just want to know 
about software solution for the problem they face off. 

In 2006 I got the chance to join the event where most of the people involved 
from all over the world in Free and Open Source Software four GIS was present. 
Then, I always join the event thinking that it is key event to learn about GIS 
innovative solutions and meet people which make this solutions possible.

OSGeo is spreading knowledge by providing more and more hight quality material 
to learn on your own how to use solutions. You came to OSGeo with questions and 
you find your answer but also more questions with answers... new ideas.
 
As OSGeo help me so much by providing solutions and materials, it sounds 
obvious to me to promote it everywhere I go. Promotion, including translation, 
training sessions, workshops, talks or simple discussion. I think that even if 
it is good to put a bottle containing a message in the water, it is also needed 
to go there with your bottle to give and discuss what you wrote on the paper.

Sincerly yours,

Gérald Fenoy
gerald.fe...@geolabs.fr

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

[OSGeo-Discuss] Question about MacOS X packages

2011-04-06 Thread Gérald Fenoy 
Hi,
I'm now wondering what is the correct way to add a MacOS X Package to the 
OSGeoLive DVD ?

Indeed as presented here [1] we get a simple MacOS X installer to easily deploy 
ZOO-Kernel and
OGR base vector operations services. Si I would like to add the package to the 
list of available 
software for MacOS X but I don't know the way to go.

Hope to hear from you,
best regards,

[1] 
http://zoo-project.org/trac/wiki/ZooDocumentation/ZOOKernel/MacOSX_installation

Gérald Fenoy
gerald.fe...@geolabs.fr

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

Re: [OSGeo-Discuss] Japan chapter receives “J apanese OSS Encouragement Award” by IPA

2010-10-23 Thread Gérald Fenoy 
Hi,
congratulation for this award you fully deserve as you make a really great job 
in OSGeo Japan chapter, promoting OSGeo and Open Source software in general. It 
is really impressive and huge work from my point of view.

I'm that this award will encourage you to continue on your way. I hope that the 
mola mola will continue  to be protected against fishing :)

Long life to OSGeo Japan !


Le 18 oct. 2010 .AN` 04:27, Toru Mori$B!J?9N!K(B a Nicrit :

 Hi OSGeo friends,
 
 I am really happy to receive many emails from our community.
 It really is our milestone in promoting FOSS4G into the Japanese geospatial 
 field.
 We will continue to invest effort in doing it, especially in eliminating 
 technical and usability barriers including localization issue.
 
 Here are examples of our recent achievements. 
 http://www.osgeo.jp/foss4g-mext/
 - you can translate it into your local language using google translate 
 feature on up right of the window.
 http://trac.osgeo.org/osgeo4w/wiki/OSGeo4W_jp
 
 And again, please join our local FOSS4G conference. No fee needed to register.
 Tokyo  http://www.osgeo.jp/foss4g2010tokyo/
 Osaka  http://www.osgeo.jp/foss4g2010-in-osaka/
 
 I hope to see you all and work together.
 
 Mori
 
 On 2010/10/16, at 0:09, Toru Mori$B!J?9N!K(B wrote:
 
 Hi OSGeo community,
 
 Today IPA (IT promotion agency Japan), a government agency, announced that 
 OSGeo Japan Chapter will be awarded $B!H(BJapanese OSS Encouragement 
 Award$B!I(B prize on 28th October 2010.
 I , as representative of the chapter, am very pleased and honored to receive 
 the prize!
 
 The Japan chapter was established in late 2006 and the local community has 
 been growing steadily and dedicating effort to promoting FOSS4G.
 Please join our local conference, FOSS4G 2010 Tokyo/Osaka, held in this 
 November to celebrate it with us over bottles of beer!
 http://www.osgeo.jp/
 
 
 -- Press release by IPA (in Japanese) --
 http://www.ipa.go.jp/about/press/20101015_2.html
 
 -- About the award --
 IPA grants $B!H(BJapanese OSS Contributor Award$B!I(B to a developer who 
 has established and has been managing the development project which has the 
 influence, to a superior developer who takes an active role in the global 
 projects and to a contributor to spread the OSS. Also IPA grants 
 $B!H(BJapanese OSS Encouragement Award$B!I(B to the individual or the 
 group which has a remarkable activity to develop and/or spread OSS.
 
 -- About IPA --
 http://www.ipa.go.jp/english/about/index.html
 
 Toru Mori
 Yokohama Japan
 
 ___
 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

G.ANirald Fenoy
gerald.fe...@geolabs.fr

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

[OSGeo-Discuss] ZOO-Project WPS Validity report

2010-09-20 Thread Gérald Fenoy 
Hi All,

Several WPS related presentation at FOSS4G2010 including the one entitled 
Compliance testing of Open Source Software for Web Processing Services took 
place this year [1].

The presentation above reported about some incorrect results about the ZOO-WPS 
implementation. So the ZOO-Tribe decided to provide a report based on the same 
techniques than the one used in above presentation and clarify of the ZOO 
Kernel valid XML responses using only Open Source software to run the tests.

The results of our tests are available on wiki page on the official ZOO Project 
Trac system [2] where you can read the results we got when running the validity 
tests for each requests discussed during the conference. As we are in an Open 
Source community we also provided a tool [3] to run the tests on your own using 
a simple bash script (working also on GNU/Linux and MacOS X). This way you can 
ensure that tests made were appropriate. Based on this tool we created another 
script which provides periodically a web report available on the ZOO-Project 
web site [4].

Contrary to what was said during in [1], all the tests made was successfully 
validated. Nevertheless, on the OGC external wiki [5], we noticed that the URLs 
used to run tests on the ZOO Kernel response validity was wrong so we have 
corrected it on this wiki page also.

Finally the conclusion to this test are the following :

a) ZOO Kernel provide XML document in responses to WPS request which are all 
valid,
b) ZOO Kernel support all the Execute request type

I hope you can take few minutes of your busy time to read the report and check 
by yourself that everything is working fine with the ZOO Kernel and maybe even 
more in the form of a a generic way to test our WPS implementation responses 
validity which will be useful for future testing.

Best regards,

[1] http://2010.foss4g.org/presentations_show.php?id=3604
[2] http://www.zoo-project.org/trac/wiki/ZOOWPSImplementationReport
[3] 
http://www.zoo-project.org/trac/attachment/wiki/ZOOWPSImplementationReport/testXmlValidation.sh
[4] http://zoo-project.org/ZOODEMOREP/demoReport1.html
[5] 
http://external.opengeospatial.org/twiki_public/bin/view/WPS/ComplianceTestingResults2010

Gérald Fenoy 
ZOO PSC Chair
gerald.fe...@geolabs.fr

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

Re: [OSGeo-Discuss] ZOO-Project WPS Validity report

2010-09-20 Thread Gérald Fenoy 
Hi Jody, 
thanks for your answer.

Indeed we wish to get blog posts about this specifically, I'm hopping than some 
of this mailing list readers will post on their own blog. Somebody from the 
ZOO-Discuss mailing list already post the content of the previous mail [1].

Hope to see more blog posts about this,
best regards,

[1] 
http://3liz.com/blog/rldhont/index.php/2010/09/20/344-zoo-project-wps-validity-report

Le 20 sept. 2010 à 11:09, Jody Garnett a écrit :

 With respect to your testing of zoo - you may wish to pass this information 
 on as a blog post so it shows up on osgeo planet along with the other foss4g 
 summaries.
 

Gérald Fenoy
ZOO PSC Chair
gerald.fe...@geolabs.fr

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

Re: [OSGeo-Discuss] Supporting new projects

2007-10-01 Thread Gérald Fenoy 

Paul Spencer [EMAIL PROTECTED]:

 I'd like to open a discussion on how OSGeo is (or is not) supporting
 brand new projects.

 While at the FOSS4G 2007 conference (awesome job Paul R. and gang), a
 number of new people (new to the conference and/or to me) approached
 me to demonstrate their particular projects and ask how to make them
 Open Source.  This got me thinking about OSGeo's role in fostering
 innovation and giving new projects a chance to get off the ground.

 Our current incubation process favours established projects, ones
 that have an established code base, established community, etc.  It
 does not, and arguably should not, be a place to start new projects.

 For folks already established in OS and OSGeo, we have established
 communities around ourselves that can be used to attract people to
 new projects that we are spawning - Fusion, for instance.  For
 others, though, there is no such place to launch a new project and to
 try to build the community of users and developers required to build
 a project.  They have no clue where to start.  And I don't feel that
 comfortable telling someone their project is a good idea or not - my
 view of the world is usually quite limited to the things I'm
 interested in and I have no clue if the rest of the community would
 be interested or not.

 The FOSS4G conference can be a good place to publicize new projects,
 but I would argue that it is not generally convenient to get to for
 most people in the world and perhaps more difficult for new projects
 to get on the agenda if the presenters are relatively unknown.

 It seems to me that there could be a role for OSGeo in providing a
 breeding ground for new projects by providing advice on how to create
 a brand new open source geospatial project, including a home, a
 presence, and some initial marketing to the existing OSGeo  
communities.


 What do others think about this?  Should OSGeo be in the business of
 helping new OSGeo projects get off the ground?

Hi,
IMHO this is really a good idea. Indeed, right now new projects have  
to create
their own infrastructures to manage their projects (using a trac  
system or
something similar) but it could be a better solution to purpose an  
allready

existing (ready-to-use, up-to-date, secure and so on) infrastructure to
store/start new projects. Even if it's not really a big work to make  
this kind
of infrastructure running, it could be easier to use an allready  
ready-to-use
platform for deploying the source code and make some documentation  
for a new

project.

This way, some projects should be able to start quicker, as they  
don't have to
manage their own infrastructure. Furthermore, all new projects could  
get a
standard and central way to start and present their own work (new  
projects)
without bothering with presentation (for example) or something like  
that which
could be really frustrating if they only want to share their source  
code and
create some documentation on how to use and also defining the  
functionalities

of their project(s).

So IMHO in some sense OSGeo should became something like sourceforge  
but only
for gis-oriented free software. But maybe I'm wrong so correct me if  
it's the

case.

Furthermore, OSGeo should became the starting point to search for gis- 
oriented

free software, this sounds good to me.

Hope to hear more about this topic soon.


Regards,


Gérald Fenoy
Official mail : gerald [_ dot _] fenoy [_ at _] geolabs [_ dot _] fr
Open source mail : djay [_ at _] gentoo [_ dot _] org,
sci-geosciences herd listen on sci-geosciences [_ at _] gentoo [_ dot  
_] org

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