You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@climate.apache.org by "Michael Joyce (JIRA)" <ji...@apache.org> on 2013/05/16 04:49:16 UTC

[jira] [Updated] (CLIMATE-3) Purge Unnecessary JPL Internal Development Files/Folders

     [ https://issues.apache.org/jira/browse/CLIMATE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Joyce updated CLIMATE-3:
--------------------------------

    Affects Version/s: 0.1-incubating
    
> Purge Unnecessary JPL Internal Development Files/Folders
> --------------------------------------------------------
>
>                 Key: CLIMATE-3
>                 URL: https://issues.apache.org/jira/browse/CLIMATE-3
>             Project: Apache Open Climate Workbench
>          Issue Type: Task
>          Components: general
>    Affects Versions: 0.1-incubating
>         Environment: ASF svn repo
>            Reporter: Cameron Goodale
>            Assignee: Chris A. Mattmann
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Folks,
> After checking out a copy of the repo I realized there is a LOT of code in there that is actually internal JPL website stuff and some OODT components were also part of the svn dump.
> Here is a list of top level folders I think we can delete:
> /api   -   This has some php files that are used on the JPL website rcmes.jpl.nasa.gov to interact with our local Regional Climate Model Eval. Database
> /crawler   -   OODT CAS Crawler v2.2.1
> /curator   -   ???
> /filemgr   -   OODT CAS FileManager used to populate the RCMED internally at JPL
> /metextraction   -   Collection of metadata extractors to feed into the OODT CAS FileManager (JPL Only)
> /model   -   SQL table creation file.  Deprecated since we have moved onto Postgres.  Also JPL Internal
> /prodserver   -   ???
> /scripts   -   Collection of internal JPL scripts used for the RCMED
> /site   -   All of the source code for http://rcmes.jpl.nasa.gov

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira