190 likes | 325 Vues
The 2007 EGOWS Working Group focused on the benefits of cooperation among participants. Key discussions highlighted the effectiveness of sharing ideas, the evolution of communication practices, and the impact of technical challenges. Participants shared success stories and suggested improvements such as adding forums and wikis to facilitate ongoing dialogue. Challenges included resource allocation, reliance on developed software, and the need for reliable communication mechanisms. The group explored formal cooperation aspects and envisioned a creative, collaborative environment benefiting from diverse contributions for improved outcomes.
E N D
sharing of ideas • Kees: works very well • get new ideas • John: lot of differences a couple of years ago • less diff. later • sharing of ideas works
website www.knmi.nl/samenw/egows • how to organize EGOWS • add a forum ? • add a Wiki? • Heleen and Kees would like to do • ask the KNMI management for being allowed to • add a Photobook
see communication • (ECMWF as moderator for between meetings communication) • ?
why is it difficult to cooperate? • cooperation on little scale possible • in between: difficult • risk of cutting resources • reliability on SW developed in other service without contract basis? • other extreme: official internationl cooperation (contract based) • at that stage the project/coop is safe • technical problems (formats,standards)
communication • not much communication between the conferences
not much communication between the conferences • sometimes you ask by email and get answers (like Marie did for XMLobjects) • communication between the conferences • would need a moderator • ECMWF ? • needs resources for this • more meetings? • Internet communication to improve?
language • English might be a problem • people can improve
resources • you need more resources (critical mass) for starting a cooperation • but: later you will save resources • AND: you will get the much better product by using the ideas of all participants of a cooperation
Does it make sense to have only 1 system? • maybe not • failover? • in case one system fails, they could go NinJo or somewhere else • need some concurrency to improve systems • more creative • open mind for world wide thinking
develop open libraries (DB/..) • share maintenance • can you rely on a tool/db on voluntary base • need to rely on maintenance • need contracts or something • on own risc • formal cooperation • needs more