Alright it has been a week; who is on the PSC and if they are representing the project why are they not talking to me?
Jody
Hi Jody,
Thanks for the Ping, I think I should clarify some things here to avoid you remain without responses 
Most members of the PSC are not actively involved in the GeoNetwork development process and as such no subscribers to the dev mailing list.
The members of the PSC are listed here: GeoNetwork opensource Developer website
When we created the PSC in 2006, we named it the GeoNetwork Advisory Board. The day to day project management was left to myself, building up a community of users and developers that collaborate on the basis of consensus. I have copied the people on the advisory board for info. The PSC comes together (with the rest of the GN community) during the GeoNetwork workshops (like the one next week) to discuss experiences with the software, come up with requirements and define the work plan for next year for as much as we can.
This is why, after our previous discussions on the existing management structure, I indicated I'll propose during the workshop to work towards a Technical Steering Committee (TSC) for the day-to-day developer management, release management etc... This should consist of the more active developers as opposed to those on the PSC who agree on the overall project direction.
So during next week's meeting we will take this up in more detail and see how we can streamline our processes with those more commonly used in other OSGeo projects. I understand this structure is not the same as the other OSGeo PSC's, but this is how the project operates now.
Hope this helps,
Ciao,
Jeroen
On Oct 29, 2007, at 7:40 PM, Jody Garnett wrote:
Alright it has been a week; who is on the PSC and if they are
representing the project why are they not talking to me?
Jody
Jeroen Ticheler wrote:
Hi Jody,
Thanks for the Ping, I think I should clarify some things here to avoid you remain without responsesMost members of the PSC are not actively involved in the GeoNetwork development process and as such no subscribers to the dev mailing list.
The members of the PSC are listed here: GeoNetwork opensource Developer websiteWhen we created the PSC in 2006, we named it the GeoNetwork Advisory Board. The day to day project management was left to myself, building up a community of users and developers that collaborate on the basis of consensus. I have copied the people on the advisory board for info. The PSC comes together (with the rest of the GN community) during the GeoNetwork workshops (like the one next week) to discuss experiences with the software, come up with requirements and define the work plan for next year for as much as we can.
That sounds like a fine seperation of concerns - it seems was asking for the wrong group for clarification ;-).
So does the advisory board have an email list? A record of being able to work together etc... are their some notes, minuets, etc... that I could review.
This is why, after our previous discussions on the existing management structure, I indicated I'll propose during the workshop to work towards a Technical Steering Committee (TSC) for the day-to-day developer management, release management etc... This should consist of the more active developers as opposed to those on the PSC who agree on the overall project direction.
The separation between project and day to day concerns is fine (GeoTools PMC operates in a similar manner). If the GeoNetwork Advisor Board is the group making decisions then they are who I want to talk to.
So during next week's meeting we will take this up in more detail and see how we can streamline our processes with those more commonly used in other OSGeo projects. I understand this structure is not the same as the other OSGeo PSC's, but this is how the project operates now.
There is no reason to conform; only document and show that the process is open.
Hope this helps,
Cheers,
Jody
Me again
On Oct 30, 2007, at 12:33 AM, Jody Garnett wrote:
Jeroen Ticheler wrote:
Hi Jody,
Thanks for the Ping, I think I should clarify some things here to avoid you remain without responsesMost members of the PSC are not actively involved in the GeoNetwork development process and as such no subscribers to the dev mailing list.
The members of the PSC are listed here: GeoNetwork opensource Developer websiteWhen we created the PSC in 2006, we named it the GeoNetwork Advisory Board. The day to day project management was left to myself, building up a community of users and developers that collaborate on the basis of consensus. I have copied the people on the advisory board for info. The PSC comes together (with the rest of the GN community) during the GeoNetwork workshops (like the one next week) to discuss experiences with the software, come up with requirements and define the work plan for next year for as much as we can.
That sounds like a fine seperation of concerns - it seems was asking for the wrong group for clarification ;-).
So does the advisory board have an email list? A record of being able to work together etc... are their some notes, minuets, etc... that I could review.
We don't have an email list, just 7 names with email addresses (me included). This is something we could set up if useful.
The work plan of 2006, available online on the geonetwork-opensource.org web site is what we have as minutes of the 2006 workshop.
This is why, after our previous discussions on the existing management structure, I indicated I'll propose during the workshop to work towards a Technical Steering Committee (TSC) for the day-to-day developer management, release management etc... This should consist of the more active developers as opposed to those on the PSC who agree on the overall project direction.
The separation between project and day to day concerns is fine (GeoTools PMC operates in a similar manner). If the GeoNetwork Advisor Board is the group making decisions then they are who I want to talk to.
Excellent!
So during next week's meeting we will take this up in more detail and see how we can streamline our processes with those more commonly used in other OSGeo projects. I understand this structure is not the same as the other OSGeo PSC's, but this is how the project operates now.
There is no reason to conform; only document and show that the process is open.
Hope this helps,
Cheers,
Jody
Cheers,
Jeroen
Did anyone receive my comments on the PSC ToRs ?
sean
On 10/29/07, Jeroen Ticheler <Jeroen.Ticheler@anonymised.com > wrote:
Hi Jody,
Thanks for the Ping, I think I should clarify some things here to
avoid you remain without responsesMost members of the PSC are not actively involved in the GeoNetwork
development process and as such no subscribers to the dev mailing list.
The members of the PSC are listed here: http://trac.osgeo.org/geonetworkWhen we created the PSC in 2006, we named it the GeoNetwork Advisory
Board. The day to day project management was left to myself, building
up a community of users and developers that collaborate on the basis
of consensus. I have copied the people on the advisory board for
info. The PSC comes together (with the rest of the GN community)
during the GeoNetwork workshops (like the one next week) to discuss
experiences with the software, come up with requirements and define
the work plan for next year for as much as we can.This is why, after our previous discussions on the existing
management structure, I indicated I’ll propose during the workshop to
work towards a Technical Steering Committee (TSC) for the day-to-day
developer management, release management etc… This should consist
of the more active developers as opposed to those on the PSC who
agree on the overall project direction.So during next week’s meeting we will take this up in more detail and
see how we can streamline our processes with those more commonly used
in other OSGeo projects. I understand this structure is not the same
as the other OSGeo PSC’s, but this is how the project operates now.Hope this helps,
Ciao,
JeroenOn Oct 29, 2007, at 7:40 PM, Jody Garnett wrote:
Alright it has been a week; who is on the PSC and if they are
representing the project why are they not talking to me?
Jody
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
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
–
Best Regards,
Sean Khan
UNEP/IWLEARN Project Manager
P.O.Box 30552
Nairobi
Tel: (254) [20] 762-3271
From Europe and N.America, dial via Italy +39 0831 24 3000, wait for voice
then dial 124 3271