[GeoNetwork-devel] OSGeo iccubation report - great now I need to check up on you :-)

GeoNetwork GeoNetwork Developer
1

Hi everyone ... it has been a couple of months and it is time for me to report back to the committee on our progress.

So far my job has as mentor has been relaxing and easy; but also not very helpful (you have not asked questions!). While it is not my roll to be an active in doing the work associated with the incubation process I would like check that all the information you require is available.

There is a couple of options:
a) OSGeo iccubation is a "nice to have" but not associated with anyones deadlines or job - this is the case for GeoTools and it has made our iccubation process long slow and difficult. Incubation is more of a marketing / community exercise and detracts from the aims of a development list (producing great software).
b) I could be using the wrong avenue for communication - this is a development list after all - am I making contact with the correct group of people? As example maybe there is an IRC meeting, Skype conference call or some other venue that I should be making myself available for?

Regardless, lets update our status pages to reflect what is going on. One thing I recommend is that you take the status page off of the OSGeo wiki (because the development community will no go through the trouble of signing up in yet another location) and make it part of your code base! Either on a GeoNetwork wiki or right into svn along side your build file.

In terms of facilitation here is the link to the existing status and providence review pages:

http://wiki.osgeo.org/index.php/GeoNetwork_Incubation_Status
http://wiki.osgeo.org/index.php?title=GeoNetwork_Provenance_Review&action=edit

In response to the page I will start up an email discussion on each topic ...
Cheers,
Jody

2

No. SourceForge.net tracker is in use by the project.

Can we provide a link to the source forge tracker please.

Cheers,
Jody

In response to the page I will start up an email discussion on each topic ...
Cheers,
Jody

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net
  

3

Is the OSGeo mailing list manager being used for the project?

    No. SourceForge.net mailing list manager is in use by the project.

Is the OSGeo SVN or CVS system being used for the project?

    No. SourceForge.net Subversion is used by the project.

Lets update these links ...

Jody Garnett wrote:

In terms of facilitation here is the link to the existing status and providence review pages:
  

http://wiki.osgeo.org/index.php/GeoNetwork_Incubation_Status
http://wiki.osgeo.org/index.php?title=GeoNetwork_Provenance_Review&action=edit
    

In response to the page I will start up an email discussion on each topic ...
Cheers,
Jody

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net
  

4

No. We don't know where that area is :slight_smile:

I agree - I don't know either ... sending an email to the incubation list and will get back to you. We should update the page with a link
to where downloads are available.

Jody

Jody Garnett wrote:

In terms of facilitation here is the link to the existing status and providence review pages:
  

http://wiki.osgeo.org/index.php/GeoNetwork_Incubation_Status
http://wiki.osgeo.org/index.php?title=GeoNetwork_Provenance_Review&action=edit
    

In response to the page I will start up an email discussion on each topic ...
Cheers,
Jody

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net
  

5

Hi Jody,

On Mar 5, 2007, at 8:43 PM, Jody Garnett wrote:

Hi everyone ... it has been a couple of months and it is time for me to
report back to the committee on our progress.

So far my job has as mentor has been relaxing and easy; but also not
very helpful (you have not asked questions!). While it is not my roll to
be an active in doing the work associated with the incubation process I
would like check that all the information you require is available.

There is a couple of options:
a) OSGeo iccubation is a "nice to have" but not associated with anyones
deadlines or job - this is the case for GeoTools and it has made our
iccubation process long slow and difficult. Incubation is more of a
marketing / community exercise and detracts from the aims of a
development list (producing great software).

I think our situation is fairly close to the GeoTools one. Nice to have sounds a bit uninterested I must say :slight_smile: But for sure, it has not been a high priority to run through the whole process. I would like to complete it fairly quickly now and think that the biggest work ahead is the code review. But maybe that is more due to not exactly knowing how involved it is rather than it being a big job :slight_smile:

b) I could be using the wrong avenue for communication - this is a
development list after all - am I making contact with the correct group
of people? As example maybe there is an IRC meeting, Skype conference
call or some other venue that I should be making myself available for?

Regardless, lets update our status pages to reflect what is going on.
One thing I recommend is that you take the status page off of the OSGeo
wiki (because the development community will no go through the trouble
of signing up in yet another location) and make it part of your code
base! Either on a GeoNetwork wiki or right into svn along side your
build file.

I updated the page recently and updated the missing links to mailing list and SVN now. We do not have a WIKI in our Community website at present. I'll make a clear link to the incubation page from the site though. I don't see the account creation on OSGEO as a major obstacle for getting other contributions to the page.

The plan is to complete incubation in the first half of this year. We are looking for a best moment to do the code review. We are currently focussing on the release of version 2.1 and it may proof most effective to go through the process once that code has stabilized.

In the mean time, we try to highlight OSGEO incubation and the connection between the GeoNetwork opensource project and the foundation any time that is appropriate.

Hope that helps a bit.
Ciao,
Jeroen

In terms of facilitation here is the link to the existing status and
providence review pages:

http://wiki.osgeo.org/index.php/GeoNetwork_Incubation_Status
http://wiki.osgeo.org/index.php?title=GeoNetwork_Provenance_Review&action=edit

In response to the page I will start up an email discussion on each
topic ...
Cheers,
Jody

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

6

Jeroen Ticheler wrote:

I think our situation is fairly close to the GeoTools one. Nice to have sounds a bit uninterested I must say :slight_smile:

Not to worry; we are proceeding :smiley: And open source is volunteer driven.

But I would be happier if more GeoNetwork developers responded (not that I don't like working with you Jeroen - but meeting the locals is part of why I am mentoring), and I got to see your development process divide up the work. Of course over in GeoTools we divided up the work and then three months later went ahead and cleaned up the parts that were not done.

But for sure, it has not been a high priority to run through the whole process. I would like to complete it fairly quickly now and think that the biggest work ahead is the code review. But maybe that is more due to not exactly knowing how involved it is rather than it being a big job :slight_smile:

It should be a manual check of each file header - not sure how many classes you got? I am for something measured in hundreds :smiley: I could check one a minuet when I did geotools, ended up taking around three weeks for the entire thing (doing 20 mins a day).

b) I could be using the wrong avenue for communication - this is a
development list after all - am I making contact with the correct group
of people? As example maybe there is an IRC meeting, Skype conference
call or some other venue that I should be making myself available for?

Regardless, lets update our status pages to reflect what is going on.
One thing I recommend is that you take the status page off of the OSGeo
wiki (because the development community will no go through the trouble
of signing up in yet another location) and make it part of your code
base! Either on a GeoNetwork wiki or right into svn along side your
build file.

I updated the page recently and updated the missing links to mailing list and SVN now. We do not have a WIKI in our Community website at present. I'll make a clear link to the incubation page from the site though. I don't see the account creation on OSGEO as a major obstacle for getting other contributions to the page.

Okay ... for my developer community it was an obstacle.

The plan is to complete incubation in the first half of this year. We are looking for a best moment to do the code review. We are currently focussing on the release of version 2.1 and it may proof most effective to go through the process once that code has stabilized.

That sounds good; a couple recommendation for you.
- Make checking the headers part of your 2.1 release process (it is something you will need to do each release anyways ...)
- Time graduation for the foss4g2007 conference; more members of the press will be around etc...

In the mean time, we try to highlight OSGEO incubation and the connection between the GeoNetwork opensource project and the foundation any time that is appropriate.

Hope that helps a bit.
Ciao,
Jeroen

Cheers,
Jody

7

Hi Jody & Jeoren,

How should look like the files header ? Do we need to update the current one
? Do we need to add the header to the xml, xsl, ... files also ? Or only
Java classes ?

Do we have to work on updating code documentation ?

Cheers
Francois - little dev asking questions :slight_smile:

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de Jody
Garnett
Envoyé : mercredi 7 mars 2007 02:20
À : Jeroen Ticheler
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] OSGeo iccubation report - great now I need to
check up on you :slight_smile:

Jeroen Ticheler wrote:

I think our situation is fairly close to the GeoTools one. Nice to
have sounds a bit uninterested I must say :slight_smile:

Not to worry; we are proceeding :smiley: And open source is volunteer driven.

But I would be happier if more GeoNetwork developers responded (not that I
don't like working with you Jeroen - but meeting the locals is part of why I
am mentoring), and I got to see your development process divide up the work.
Of course over in GeoTools we divided up the work and then three months
later went ahead and cleaned up the parts that were not done.

But for sure, it has not been a high priority to run through the whole
process. I would like to complete it fairly quickly now and think that
the biggest work ahead is the code review. But maybe that is more due
to not exactly knowing how involved it is rather than it being a big
job :slight_smile:

It should be a manual check of each file header - not sure how many classes
you got? I am for something measured in hundreds :smiley: I could check one a
minuet when I did geotools, ended up taking around three weeks for the
entire thing (doing 20 mins a day).

b) I could be using the wrong avenue for communication - this is a
development list after all - am I making contact with the correct
group of people? As example maybe there is an IRC meeting, Skype
conference call or some other venue that I should be making myself

available for?

Regardless, lets update our status pages to reflect what is going on.
One thing I recommend is that you take the status page off of the
OSGeo wiki (because the development community will no go through the
trouble of signing up in yet another location) and make it part of
your code base! Either on a GeoNetwork wiki or right into svn along
side your build file.

I updated the page recently and updated the missing links to mailing
list and SVN now. We do not have a WIKI in our Community website at
present. I'll make a clear link to the incubation page from the site
though. I don't see the account creation on OSGEO as a major obstacle
for getting other contributions to the page.

Okay ... for my developer community it was an obstacle.

The plan is to complete incubation in the first half of this year. We
are looking for a best moment to do the code review. We are currently
focussing on the release of version 2.1 and it may proof most
effective to go through the process once that code has stabilized.

That sounds good; a couple recommendation for you.
- Make checking the headers part of your 2.1 release process (it is
something you will need to do each release anyways ...)
- Time graduation for the foss4g2007 conference; more members of the press
will be around etc...

In the mean time, we try to highlight OSGEO incubation and the
connection between the GeoNetwork opensource project and the
foundation any time that is appropriate.

Hope that helps a bit.
Ciao,
Jeroen

Cheers,
Jody

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

8

François Prunayre wrote:

Hi Jody & Jeoren,

How should look like the files header ? Do we need to update the current one
? Do we need to add the header to the xml, xsl, ... files also ? Or only
Java classes ?
  

François can you supply a link to your current header file? I assume it needs copyright (who wrote it), license (how it can be used)...
Often projects just have a LICENSE.TXT file in their code repository to cover the various xml, xsl and build scripts.

Do we have to work on updating code documentation ?
  

Code documentation (like javadocs?), or code documentation in terms of developer instructions?
Your project may want to look at a free document license of some sort for documentation, so far OSGeo projects seem more focused on the code.

Yeah questions - lets look at some examples and see what (if anything?) needs to be done.

Jody

Cheers
Francois - little dev asking questions :slight_smile:

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de Jody
Garnett
Envoyé : mercredi 7 mars 2007 02:20
À : Jeroen Ticheler
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] OSGeo iccubation report - great now I need to
check up on you :slight_smile:

Jeroen Ticheler wrote:
  

I think our situation is fairly close to the GeoTools one. Nice to have sounds a bit uninterested I must say :slight_smile:
    

Not to worry; we are proceeding :smiley: And open source is volunteer driven.

But I would be happier if more GeoNetwork developers responded (not that I
don't like working with you Jeroen - but meeting the locals is part of why I
am mentoring), and I got to see your development process divide up the work.
Of course over in GeoTools we divided up the work and then three months
later went ahead and cleaned up the parts that were not done.
  

But for sure, it has not been a high priority to run through the whole process. I would like to complete it fairly quickly now and think that the biggest work ahead is the code review. But maybe that is more due to not exactly knowing how involved it is rather than it being a big job :slight_smile:
    

It should be a manual check of each file header - not sure how many classes
you got? I am for something measured in hundreds :smiley: I could check one a
minuet when I did geotools, ended up taking around three weeks for the
entire thing (doing 20 mins a day).
  

b) I could be using the wrong avenue for communication - this is a development list after all - am I making contact with the correct group of people? As example maybe there is an IRC meeting, Skype conference call or some other venue that I should be making myself
      

available for?
  

Regardless, lets update our status pages to reflect what is going on.
One thing I recommend is that you take the status page off of the OSGeo wiki (because the development community will no go through the trouble of signing up in yet another location) and make it part of your code base! Either on a GeoNetwork wiki or right into svn along side your build file.
      

I updated the page recently and updated the missing links to mailing list and SVN now. We do not have a WIKI in our Community website at present. I'll make a clear link to the incubation page from the site though. I don't see the account creation on OSGEO as a major obstacle for getting other contributions to the page.
    

Okay ... for my developer community it was an obstacle.
  

The plan is to complete incubation in the first half of this year. We are looking for a best moment to do the code review. We are currently focussing on the release of version 2.1 and it may proof most effective to go through the process once that code has stabilized.
    

That sounds good; a couple recommendation for you.
- Make checking the headers part of your 2.1 release process (it is
something you will need to do each release anyways ...)
- Time graduation for the foss4g2007 conference; more members of the press
will be around etc...
  

In the mean time, we try to highlight OSGEO incubation and the connection between the GeoNetwork opensource project and the foundation any time that is appropriate.

Hope that helps a bit.
Ciao,
Jeroen
    

Cheers,
Jody

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

9

Hi Jody,

On Mar 8, 2007, at 11:22 PM, Jody Garnett wrote:

François Prunayre wrote:

Hi Jody & Jeoren,
How should look like the files header ? Do we need to update the current one
? Do we need to add the header to the xml, xsl, ... files also ? Or only
Java classes ?

François can you supply a link to your current header file?

The general license file for GeoNetwork is here:

http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/trunk/docs/license.html?revision=2&view=markup

The header we use is added to all java code. See for instance:

http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/trunk/src/org/fao/geonet/Geonetwork.java?view=markup

We would simply change the copyright section I presume!?

Ciao,
Jeroen

I assume it needs copyright (who wrote it), license (how it can be used)...
Often projects just have a LICENSE.TXT file in their code repository to cover the various xml, xsl and build scripts.

Do we have to work on updating code documentation ?

Code documentation (like javadocs?), or code documentation in terms of developer instructions?
Your project may want to look at a free document license of some sort for documentation, so far OSGeo projects seem more focused on the code.

Yeah questions - lets look at some examples and see what (if anything?) needs to be done.

Jody

Cheers
Francois - little dev asking questions :slight_smile:

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de Jody
Garnett
Envoyé : mercredi 7 mars 2007 02:20
À : Jeroen Ticheler
Cc : geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] OSGeo iccubation report - great now I need to
check up on you :slight_smile:

Jeroen Ticheler wrote:

I think our situation is fairly close to the GeoTools one. Nice to have sounds a bit uninterested I must say :slight_smile:

Not to worry; we are proceeding :smiley: And open source is volunteer driven.

But I would be happier if more GeoNetwork developers responded (not that I
don't like working with you Jeroen - but meeting the locals is part of why I
am mentoring), and I got to see your development process divide up the work.
Of course over in GeoTools we divided up the work and then three months
later went ahead and cleaned up the parts that were not done.

But for sure, it has not been a high priority to run through the whole process. I would like to complete it fairly quickly now and think that the biggest work ahead is the code review. But maybe that is more due to not exactly knowing how involved it is rather than it being a big job :slight_smile:

It should be a manual check of each file header - not sure how many classes
you got? I am for something measured in hundreds :smiley: I could check one a
minuet when I did geotools, ended up taking around three weeks for the
entire thing (doing 20 mins a day).

b) I could be using the wrong avenue for communication - this is a development list after all - am I making contact with the correct group of people? As example maybe there is an IRC meeting, Skype conference call or some other venue that I should be making myself

available for?

Regardless, lets update our status pages to reflect what is going on.
One thing I recommend is that you take the status page off of the OSGeo wiki (because the development community will no go through the trouble of signing up in yet another location) and make it part of your code base! Either on a GeoNetwork wiki or right into svn along side your build file.

I updated the page recently and updated the missing links to mailing list and SVN now. We do not have a WIKI in our Community website at present. I'll make a clear link to the incubation page from the site though. I don't see the account creation on OSGEO as a major obstacle for getting other contributions to the page.

Okay ... for my developer community it was an obstacle.

The plan is to complete incubation in the first half of this year. We are looking for a best moment to do the code review. We are currently focussing on the release of version 2.1 and it may proof most effective to go through the process once that code has stabilized.

That sounds good; a couple recommendation for you.
- Make checking the headers part of your 2.1 release process (it is
something you will need to do each release anyways ...)
- Time graduation for the foss4g2007 conference; more members of the press
will be around etc...

In the mean time, we try to highlight OSGEO incubation and the connection between the GeoNetwork opensource project and the foundation any time that is appropriate.

Hope that helps a bit.
Ciao,
Jeroen

Cheers,
Jody

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

10

Jeroen Ticheler wrote:

The general license file for GeoNetwork is here:
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

GPL - check.

The header we use is added to all java code. See for instance:
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

Here we go:
//=============================================================================
//=== Copyright (C) 2001-2005 Food and Agriculture Organization of the
//=== United Nations (FAO-UN), United Nations World Food Programme (WFP)
//=== and United Nations Environment Programme (UNEP)
//===
//=== This program is free software; you can redistribute it and/or modify
//=== it under the terms of the GNU General Public License as published by
//=== the Free Software Foundation; either version 2 of the License, or (at
//=== your option) any later version.
//===
//=== This program is distributed in the hope that it will be useful, but
//=== WITHOUT ANY WARRANTY; without even the implied warranty of
//=== MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
//=== General Public License for more details.
//===
//=== You should have received a copy of the GNU General Public License
//=== along with this program; if not, write to the Free Software
//=== Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
//===
//=== Contact: Jeroen Ticheler - FAO - Viale delle Terme di Caracalla 2,
//=== Rome - Italy. email: GeoNetwork@anonymised.com
//==============================================================================

A couple of questions:
- is the address correct? They changed it a while ago
- do you need to track (c) of contributors? Or are you doing some kind of contributor agreement?

We would simply change the copyright section I presume!?

Nope: FAO can still hold the (c) it is a nice legal organization.

(if you hear me asking questions for the GeoTools community about OSGeo holding copyright it is because the
GeoTools PMC screwed up and does not have a legal organization holding the copyright. Rather then make up our
own foundation we are endevouring to borrow the existing open source geospatial foundation for this purpose)

Ciao,
Jeroen

Thanks for the links ..

So the next step is to review all your files and ensure that the header is there. That is most of the work for
the providence review. They would like this done by hand (and notes kept) rather then use a tool.

Cheers,
Jody