[Incubator] Functionality breakdown of OSGEO

[Daniel Brookshier]

There is a guide for using it with the collabnet platform. It is  
supported, but not a service.
Daniel Brookshier
Community Manager
Office: 972-422-5261
Cell: 214-207-6614


On Mar 15, 2006, at 12:18 PM, Chris Holmes wrote:

>
>
> Daniel Brookshier wrote:
>> Forgot to add, we support CruiseControl, an automated build/test   
>> tool. You have to run it on your end. http://  
>> cruisecontrol.sourceforge.net/
> What does it mean you support it if we have to run it?  We use it  
> for our java geo projects...
>
>> Maven is used on many of our sites. Hard to say what that means   
>> because I am not a maven expert.
>> Daniel Brookshier
>> Community Manager
>> Office: 972-422-5261
>> Cell: 214-207-6614
>> On Mar 15, 2006, at 8:27 AM, Jody Garnett wrote:
>>> Thanks Mr. Lucas - let me try my hand for geotools:
>>>
>>> What needs more (any) work:
>>> - user support
>>> - marketing
>>> - intro documentation (users guide)
>>> - build: maven2
>>> - release cycle (we are too slow, users end up on trunk w/ the   
>>> developers)-
>>> - interaction with propitiatory systems & formats
>>> - standards compliance and interoperability (WFS1.1,GML3,CSW)
>>>
>>> As for what works:
>>> - confluence (wiki)
>>> - jira (bug tracking)
>>> - subversion (version control)
>>> - build: maven 1
>>> - standards compliance and interoperability (GML2, WMS, SLD, etc...)
>>> - project documentation (developers guide)
>>> - testing: automated builds, unit testing
>>> - cross collaboration with other projects
>>> - branch/merge rnd cycle
>>> - IRC meetings
>>>
>>> I suppose for geotools we are looking to OSGEO for helping on  
>>> the  communication side, and less on the technical side.
>>> Jody
>>>
>>> Mark Lucas wrote:
>>>
>>>> Perhaps we should consolidation efforts on new areas where we  
>>>> can  focus our already taxed resources vs. trying to move  
>>>> something  that is already functioning well.  I suspect that  
>>>> most of the  projects are similar in their focus and  
>>>> shortcomings, but I'll  focus on ossim in case I'm wrong.
>>>>
>>>> What works as it is:
>>>>
>>>> mailing lists:
>>>> wiki - though I'd like to move to plone - I wouldn't mind  
>>>> moving  towards a standardized look and feel
>>>> doxygen
>>>> cvs - though I'd like to move to svn if I can keep all of the  
>>>> history
>>>> bugzilla
>>>>
>>>> what needs more work:
>>>> user support
>>>> quick start examples for developers and users
>>>> more bandwidth more storage for data sets and tutorials
>>>> more effective cross collaboration with other projects
>>>> automated builds
>>>> automated unit testing, regression testing
>>>> more formalized freeze, testing and release process
>>>> marketing
>>>>
>>>> I've identified some external resources for high bandwidth,   
>>>> storage, and computational power that have offered to host if  
>>>> we  need the resources.  I think we should focus on expanding  
>>>> with an  external plone site, storage, bandwidth, and processing  
>>>> resources  (will be good for the data consolidation efforts) and  
>>>> process  where we can use help.  As we have done with the wiki,  
>>>> we should  use collabnet as a portal where the internal  
>>>> resources are not  available or there is no compelling reason to  
>>>> change.
>>>>
>>>> Mark
>>>
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: incubator-unsubscribe at incubator.osgeo.org
>>> For additional commands, e-mail: incubator-help at incubator.osgeo.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: incubator-unsubscribe at incubator.osgeo.org
>> For additional commands, e-mail: incubator-help at incubator.osgeo.org
>
> -- 
> Chris Holmes
> The Open Planning Project
> thoughts at: http://cholmes.wordpress.com
> <cholmes.vcf>
> <mime-attachment.txt>