[ZOO-Discuss] We need a roadmap

[Daniel Kastl]

If looking for ideas maybe this news about Geoserver WPS module is an
interesting read:
http://geo-solutions.blogspot.com/2010/11/geosolutions-helps-geoserver-wps-going.html

Daniel
<http://geo-solutions.blogspot.com/2010/11/geosolutions-helps-geoserver-wps-going.html>

2010/11/15 rldhont <rldhont at gmail.com>

>  New Langages (Ruby, Perl, etc) or natural Langage is Kernel or Servcies ?
>
> The GetStatus is Kernel or API ?
>
> What is the actuel official version ?
> What is the next official version ?
> What is the trunk for ?
>
> Le 15/11/2010 11:59, nicolas bozon a écrit :
>
> Hi all,
>
> I also agree that a more detailed roadmap should be set up, as it was told
> in the last PSC meeting.
>
> I think we should start by gathering ideas on ZOO Project ( both Kernel,
> Services,  API, Docs...) on the ZooIdeas wiki page, which could be a kind of
> RCF
>
> I personnaly think that the roadmap should be strongly based on new ZOO
> Services and documentation, as well as ZOO API and examples applications
> improvements.
>
> http://zoo-project.org/trac/wiki/ZooIdeas
>
> Latter, Gerald, PSC and people who are whiling to help can organize theses
> ideas using the traditional Trac roadmap system
>
> http://zoo-project.org/trac/roadmap
>
> I Hope we can make such collaborative effort soon
>
> Best,
>
> Nick
>
>
>
> 2010/11/15 Daniel Kastl <daniel at georepublic.de>
>
>> Hi René-Luc,
>>
>>  I fully agree with what you said.
>> Btw., wasn't this also a topic of the last PSC meeting?
>>
>>  For a roadmap in my opinion it's also important to define goals. And
>> what shall be implemented in future versions (new features).
>> I think what other projects call "RFC" is what helps to define new
>> features. And these feature requests make the roadmap.
>> And then, as you said, others can step in and select a feature they want
>> to implement.
>>
>>  PSC, what was the final state of the roadmap discussion?
>>
>>  Daniel
>>
>>
>>
>> 2010/11/15 rldhont <rldhont at gmail.com>
>>
>>  Hi all,
>>>
>>> The last 2 mails :
>>> * ZOO at code sprints by Jeff
>>> * The new workshop material available by Gérald
>>> make mandatory the need for a roadmap
>>>
>>> Firstly, if we want more contributors, we must give them a direction.
>>> Secondly, if we speak about evolution, like GetStatus, we must associate
>>> it with versions.
>>>
>>> I know that Gérald is the only one contributor. I know that Gérald add
>>> evolution. I know that versioning system takes time.
>>>
>>> But If we want some people like me help us maintain, improve and develop
>>> the ZOO Project :
>>> WE NEED A ROADMAP.
>>>
>>> René-Luc D'Hont
>>> 3Liz
>>> JavaScript ZOO API editor
>>> _______________________________________________
>>> Zoo-discuss mailing list
>>> Zoo-discuss at gisws.media.osaka-cu.ac.jp
>>> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>>>
>>
>>
>>
>>
>>  --
>> Georepublic UG & Georepublic Japan
>> eMail: daniel.kastl at georepublic.de
>> Web: http://georepublic.de
>>
>>
>>
>> _______________________________________________
>> Zoo-discuss mailing list
>> Zoo-discuss at gisws.media.osaka-cu.ac.jp
>> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>>
>>
>
> _______________________________________________
> Zoo-discuss mailing listZoo-discuss at gisws.media.osaka-cu.ac.jphttp://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>
>
>
> _______________________________________________
> Zoo-discuss mailing list
> Zoo-discuss at gisws.media.osaka-cu.ac.jp
> http://gisws.media.osaka-cu.ac.jp/mailman/listinfo/zoo-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/zoo-discuss/attachments/20101116/9073e263/attachment.html>