Changes between Version 3 and Version 4 of FDORfc27
- Timestamp:
- 10/16/08 21:27:11 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FDORfc27
v3 v4 44 44 * Give Jackie commit access to the proposed subdirectory of the FDO SVN where FDO Toolbox will be migrated to 45 45 * Give Jackie access to download.osgeo.org so that he can make new releases 46 * Update the FDO/OSGeo site to reflect the status of the FDO Toolbox application as an official part of the FDO project47 46 48 47 The initial proposal is to import the subfolders of this SVN repository. … … 56 55 * Extension module sub-projects will be omitted from the migrated repository, and remain on Google Code. 57 56 * The Google Code project site will be re-purposed for the development of FDO Toolbox extension modules. 57 * Update the FDO/OSGeo site to reflect the status of the FDO Toolbox application as an official part of the FDO project 58 58 59 See implications for more information.59 With regards to extension modules, see implications for more information. 60 60 61 61 == Implications == … … 63 63 This will require that Jackie sign a contributor agreement, and certify that all of the work is owned by him ([http://wiki.osgeo.org/wiki/Contributor_Agreements_Received already done]) 64 64 65 The FDO Toolbox source tree currently references FDO binaries under its Thirdparty\FDO subdirectory . If we want FDO Toolbox to be somewhat in sync with the FDO project, some re-configuration will be required so that it can reference FDO binaries built from the FDO source tree. Alternatively, we can retain the existing source tree structure and simply have the user drop the compiled FDO binaries into this directory, and have this stated in the build instructions.65 The FDO Toolbox source tree currently references FDO binaries under its Thirdparty\FDO subdirectory (the current binary release used is 3.3.1). If we want FDO Toolbox to be somewhat in sync with the FDO project, some re-configuration will be required so that it can reference FDO binaries built from the FDO source tree. Alternatively, we can retain the existing source tree structure and simply have the user drop the compiled FDO binaries into this directory, and have this stated in the build instructions. 66 66 67 67 It would be desirable for someone to do a provenance review on the code.