[MetaCRS] FW: Open Source Requirements
Norm Olsen
norm.olsen at autodesk.com
Tue May 6 15:10:49 EDT 2008
Hello All . . .
Frank has suggested that the following discussion be carried out on the list. I'll use this address for all similar messages in the future. Of course, I would appreciate any additional comments.
In response to Frank's question:
The code actually being Open Sourced is a combination of Mentor's version (maintained in Perforce) and Autodesk's version (also maintained in Perforce). I suspect that trying to maintain that convoluted history may be more confusing than helpful.
Norm
-----Original Message-----
From: Frank Warmerdam (External)
Sent: Tuesday, May 06, 2008 12:58 PM
To: Norm Olsen
Cc: Hugues Wisniewski
Subject: Re: Open Source Requirements
Norm Olsen wrote:
> Hello Frank . . .
>
> Things are beginning to roll now. Need to allocate resources and schedule
> completion of deliverable product.
>
> All I need now is enough information to determine the resources necessary
> and a rough estimate on completion date.
>
> Of course, we'll need a tar/gzip file with source code, headers, and
> makefiles. Can you _very_ _briefly_ comment on:
Norm,
What source control system was used in the past? I'm wondering if it makes
sense to try and preserve any of the history? I suppose if the code cleanup
involved removing any unreleasable material, it wouldn't make sense to
include it in the history.
> 1> Documentation requirements. Should this be "in code" Doxygen?
I don't forsee end user CS-MAP docs being generated from Doxygen, though
I think it is desirable to provide developer docs this way. This is
something that we can move towards over a bit of time.
> 2> The platform makefiles you would consider a minimum.
We need practical ways to build on linux/unix and windows. I'm not
sure what is available now. Many projects provide visual studio
projects for windows and automake/autoconf based makefiles for linux
and other unix platforms. I'd be willing to help on the linux/unix side.
> 3> Will I need to establish a repository?
SAC (OSGeo) will create this. Either they (likely me in this case) or
you can do the initial import of the source.
> 4> Will I need to establish a Trac database?
SAC (me in this case) will initially prepare the Trac instance. But
you should administer it - adding versions, components, and stuff like
that to improve the management of bug reports.
PS. I think this discussion should be on the metacrs list! Feel free
to pass this email on there if you don't mind.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org
More information about the MetaCRS
mailing list