<br><font size=2 face="sans-serif">IMO:</font>
<br>
<br>
<br><font size=2 face="sans-serif">This is from a private email thread
that Jeroen has kindly agreed to making public.</font>
<br>
<br><font size=2 face="sans-serif">Thanks again for your help on this Jeroen.
There are some good ideas here. </font>
<br>
<br><font size=2 face="sans-serif"><br>
Bruce<br>
</font>
<br>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Bruce
Bannerman/DPI/VICGOV1 on 16/07/2008 10:45 AM -----</font>
<br>
<br><font size=2><tt><br>
> -------- Forwarded Message --------<br>
> From: Jeroen Ticheler <><br>
> To: Bruce Bannerman <><br>
> Subject: Re: GeoNetwork and ANZLIC Profile work<br>
> Date: Wed, 25 Jun 2008 10:49:01 +0200<br>
> <br>
> Hi Bruce,<br>
> This is way overdue :-( I'm in my last days of working for the FAO-UN
<br>
> and trying to get two GeoNetwork implementations operational before
<br>
> leaving and moving from Italy to The Netherlands. In short, problem
<br>
> life is pretty hectic these weeks :-)<br>
> <br>
> Some comments inline:<br>
> <br>
> On May 22, 2008, at 12:34 PM, Bruce Bannerman wrote:<br>
> <br>
> > Hi Jeroen,<br>
> ><br>
> > Thanks for initiating the proposal to get support of sandbox<br>
> > environments in GeoNetwork. I certainly appreciate your efforts
to <br>
> > help.<br>
> Very welcome!<br>
> ><br>
> > I thought that I'd contact you privately to see if you have any
other<br>
> > thoughts on how we could better work with the GeoNetwork community,
<br>
> > but<br>
> > at the same time coordinate and try to prioritise ANZLIC<br>
> > requirements.<br>
> ><br>
> > Please note, I'm not trying to set something up that undermines
the <br>
> > role<br>
> > of your PSC, but hopefully will work as an ANZLIC Profile coordinating<br>
> > and QA body. We have too much duplicated and wasted effort at
the<br>
> > moment. The pace of development is also too slow.<br>
> ><br>
> > Hopefully in time we will get more GeoNetwork developers and
the<br>
> > community will become more comfortable with their abilities.<br>
> <br>
> We last week had a meeting in Bolsena (OSGeo hacking event Bolsena)
<br>
> where we were with some 10 GeoNetwork developers. We did a great deal
<br>
> of proposal writing on issues that require discussion and decisions.
<br>
> I'l send an email to the developer list on these issues soon so others
<br>
> can react.<br>
> <br>
> Cameron made some good suggestions in the document he put forward.
<br>
> Some of the requirements I see that need to be solved to get a more
<br>
> solid and quick development are:<br>
> <br>
> - Set up project sponsoring for GeoNetwork that can help to fund <br>
> specific activities that help the project in the long run. Here are
<br>
> some ideas of what such a person could do (or tasks that currently
<br>
> lack the required attention)<br>
> - The project needs a developer that explicitly acts as the system
<br>
> administrator & release manager. This is something I now do in
<br>
> practice but that receives only a 2% attention of my time. The person
<br>
> would be responsible for reviewing code on compliance with coding
<br>
> standards adopted by the project, proper use of the issue tracker,
<br>
> running tests, monitoring the continuous integration process (not
in <br>
> place yet, but coming), test integration with GeoServer, make beta
and <br>
> final releases and publishing/announcing the releases on the necessary
<br>
> sites. He/she would also do the administration of sandboxes, <br>
> developers etc.<br>
> - Have a person explicitly involved in the maintenance of the <br>
> documentation for both users and developers, both on the website and
<br>
> in DocBook (the real manuals).<br>
> <br>
> There's also a need to get existing code documented better and in
a <br>
> number of cases add test processes to that existing code. Then we
have <br>
> discussed migrating code to new frameworks. That kind of work requires
<br>
> mostly rewriting and re-factoring of existing functionality. Obviously
<br>
> that is something that most of us don't find very attractive to fund
<br>
> since it doesn't provide short term benefits in new functionality.
<br>
> However, it does allow us to make the code more accessible, flexible
<br>
> and manageable. For instance, at the time the project started there
<br>
> were no frameworks ready to use that suited our needs. So the Jeeves
<br>
> API was developed as part of the project. By now, it makes sense to
<br>
> start replacing Jeeves functions with other frameworks like Spring
<br>
> MVC, Hybernate and others.<br>
> <br>
> An annual workshop has been held every year, and such an event is
the <br>
> place to discuss f2f the strategy for the coming years. Simon Pigot
<br>
> and Kate Roberts attended that last year. For this year I am still
not <br>
> sure how to organize it. I have to get some organization behind the
<br>
> project to sponsor the event. Maybe FAO will do this, maybe there
are <br>
> others.<br>
> <br>
> On getting your priorities well covered in the project, I think that
<br>
> there are no big issues. The project needs to take some steps to allow
<br>
> for (a) plugable application profiles (b) plugable translation <br>
> packages (not to much of an issue for you :-) ) and (c) plugable skins/
<br>
> themes. All of these have been discussed and are in the process of
<br>
> taking shape in a proposal. Some of the work is funded, some is <br>
> underfunded and some is not funded at all.<br>
> <br>
> <br>
> Greetings from Rome,<br>
> Jeroen<br>
> ><br>
</tt></font>
<P><FONT face=Arial size=2>Notice:</FONT><FONT
style="BACKGROUND-COLOR: #ff0000"><BR></FONT><FONT size=2><FONT face=Arial>This
email and any attachments may contain information that is personal,
confidential,<BR>legally privileged and/or copyright.</FONT> <FONT face=Arial>No
part of it should be reproduced, adapted or communicated </FONT><FONT
face=Arial>without the prior written consent of the copyright owner.
</FONT></FONT></P>
<P><FONT size=2><FONT face=Arial>It is the responsibility of the recipient to
check for and remove viruses.</FONT></FONT></P>
<P><FONT face=Arial size=2>If you have received this email in error, please
notify the sender by return email, delete it from your system and destroy any
copies. You are not authorised to use, communicate or rely on the information
contained in this email.</FONT></P>
<P><FONT face=Arial color=#008000 size=2>Please consider the environment before
printing this email.</FONT></P>
<P><FONT face=Arial size=2></FONT> </P>
<P> </P>
<P> </P>