[Incubator] quality and officers

[Cameron Shorter]

Quality, from military and software development standards point of view 
usually is proven by:
* Level of code testing provided. (80% code coverage? 100% code 
coverage? is every single conditional statement executed? as outlined in 
Mil-Std 178B)
* Also, the software development processes in place. Is all code peer 
reviewed? Are all issues raised and then tracked through to completion? ...

Yes, in the long term, I think we should look into providing the 
opportunity for projects to demonstrate this level of quality as part of 
the OSGeo brand, but I would approach it gradually as quality and 
testing processes are time consuming to set up.

Please don't set up a new committee. It will contain the same people, 
and covers much the same material as incubation, so I'd prefer to 
broaden the scope of the incubation committee.

Arnulf Christl (OSGeo) wrote:
> Jody Garnett wrote:
>> I have been having some interesting conversations at GeoLibre -
>> including one around the branding of OSGeo projects as an indication
>> of quality. As far as I can tell we have no specific quality
>> requirement - we tend to expect a strong user base to hold a
>> project's feet to the fire with respect to quality.
>
> Hi,
> the definition of quality from a user perspective is a lot broader 
> what I suspect you are aiming at here. One important indicator of an 
> Open Source project's quality is that it is licensed correctly (which 
> is part of the OSGeo Incubation Process), another one is the project's 
> community health, another one is documented and transparent 
> governance, etc. All issues that we do address and which make up the 
> OSGeo High Quality brand. Having said this I am very interested in 
> also looking into more technology focused issues of quality. And would 
> like to support the formation of a new committee (as it seems that 
> IncCom does not feel like taking on this job -  although - won't it be 
> the same folks spending time on this over again anyway... :-)
>
> Regards,
>
>> This conversation was a reminder that we should look at increasing
>> our scope; or setting up a new committee; interact with existing
>> projects (assuming the board is not already on this task?).
>>
>> I was also tasked with introducing the osgeo organisation; and drew a
>> blank when going through the osgeo "officers" - it seems that many of
>> these officers have a portfolio confined to a single project? How
>> does this work? Does it replace the need for a steering committee
>> representative?
>>
>> Jody_______________________________________________ Incubator mailing
>> list Incubator at lists.osgeo.org 
>> http://lists.osgeo.org/mailman/listinfo/incubator
>
>


-- 
Cameron Shorter
Geospatial Systems Architect
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com