Thanks for stepping up on this!
> To make this happen, I'd ask everyone with a task that requires JavaScript > coding to check in with me. By doing so, it should be much easier to avoid > duplicate efforts and share resources. > David and I have been talking a lot about team process and how we can make DVCS work for us. One topic that came up was the idea of having topical repositories which are maintained by domain experts. So, for example, Andreas could maintain the GeoNode repository or branch that all major JS changes had to go through. Then we would pull from that repo/branch to the development or release branches. Just an idea. What are your thoughts on this? > Also, as it has previously happend e.g. at the NY sprint, please involve me > in discussions on server side development that affect the way the web client > consumes or transmits information. > > To document and spread the knowledge collected this way, I would like to > maintain http://projects.opengeo.org/CAPRA/wiki/JavaScript. This page is > currently rather empty, but should involve into a dashboard for JavaScript > hints, goals, decisions etc. > > One more idea to make sure that we are all in sync: would it be possible > for the NY team to send a short report of problems or observations that come > up during the weekly live site update to the list? > I'll take that responsibility. Great idea! -- Sebastian Benthall OpenGeo - http://opengeo.org
