cmda-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lei Pan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CMDA-3) reorganize github repository
Date Thu, 17 Mar 2016 21:32:33 GMT

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

Lei Pan updated CMDA-3:
-----------------------
    Description: 
reorganize github repository so root/top level sub-directories have meaningful names, and
unused items are put in backup dir for future decision.

Suggested new dir structure:
git root — CMU_provenance — frontend
                                              — backend
              — JPL_CMDA — frontend
                                      — backend
              — doc
              — backup — as_of_201602

So the current sevices subdir will fall into
JPL_CMDA — backend. The current
ApacheCMDA-Frontend will become
JPL_CMDA — frontend. The current
JPL-WebService will become JPL_CMDA.
The current climate-service will fall into
CMU_provenance — frontend, and
climate-service-backend will fall into
CMU_provenance — backend.
The existing subdirs such as web_portal
will not be removed immediately,
but will be moved to backup — as_of_201602.

This is just a suggestion to change to
avoid confusion. Please suggest better
structure or dir names if you have any.

Also, according to our mentor Mike Joyce,
the official CMDA git repository should reside here:
https://git-wip-us.apache.org/repos/asf?p=incubator-cmda.git
and a mirror of it will be created on github, so
the current github repository is a sandbox
for us to get things organized but it’ll go away
eventually. The mirror will be created under
a different root dir on github.


git root: JPL-WebService/
-- JPL_CMDA: JPL-WebService/ 
    -- frontend: ApacheCMDA-Frontend/ 
    -- backend: services/ 
    -- client: clients/ 
    -- doc: doc/ 

-- CMU_provenance: need one? yes

Question: Do we create a git repository on Apache from scratch using github as ingredients,
or do we fix the github repository and import to Apache git?






  was:
reorganize github repository so root/top level sub-directories have meaningful names, and
unused items are put in backup dir for future decision.

Suggested new dir structure:
git root — CMU_provenance — frontend
                                              — backend
              — JPL_CMDA — frontend
                                      — backend
              — doc
              — backup — as_of_201602

So the current sevices subdir will fall into
JPL_CMDA — backend. The current
ApacheCMDA-Frontend will become
JPL_CMDA — frontend. The current
JPL-WebService will become JPL_CMDA.
The current climate-service will fall into
CMU_provenance — frontend, and
climate-service-backend will fall into
CMU_provenance — backend.
The existing subdirs such as web_portal
will not be removed immediately,
but will be moved to backup — as_of_201602.

This is just a suggestion to change to
avoid confusion. Please suggest better
structure or dir names if you have any.

Also, according to our mentor Mike Joyce,
the official CMDA git repository should reside here:
https://git-wip-us.apache.org/repos/asf?p=incubator-cmda.git
and a mirror of it will be created on github, so
the current github repository is a sandbox
for us to get things organized but it’ll go away
eventually. The mirror will be created under
a different root dir on github.


git root: JPL-WebService/
-- JPL_CMDA: JPL-WebService/ 
    -- frontend: ApacheCMDA-Frontend/ 
    -- backend: services/ client: clients/ 
    -- doc: doc/ 

-- CMU_provenance: need one? 

Question: Do we create a git repository on Apache from scratch using github as ingredients,
or do we fix the github repository and import to Apache git?







> reorganize github repository
> ----------------------------
>
>                 Key: CMDA-3
>                 URL: https://issues.apache.org/jira/browse/CMDA-3
>             Project: Apache Climate Model Diagnostic Analyzer
>          Issue Type: Task
>         Environment: github
>            Reporter: Lei Pan
>            Priority: Critical
>              Labels: github-import
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> reorganize github repository so root/top level sub-directories have meaningful names,
and unused items are put in backup dir for future decision.
> Suggested new dir structure:
> git root — CMU_provenance — frontend
>                                               — backend
>               — JPL_CMDA — frontend
>                                       — backend
>               — doc
>               — backup — as_of_201602
> So the current sevices subdir will fall into
> JPL_CMDA — backend. The current
> ApacheCMDA-Frontend will become
> JPL_CMDA — frontend. The current
> JPL-WebService will become JPL_CMDA.
> The current climate-service will fall into
> CMU_provenance — frontend, and
> climate-service-backend will fall into
> CMU_provenance — backend.
> The existing subdirs such as web_portal
> will not be removed immediately,
> but will be moved to backup — as_of_201602.
> This is just a suggestion to change to
> avoid confusion. Please suggest better
> structure or dir names if you have any.
> Also, according to our mentor Mike Joyce,
> the official CMDA git repository should reside here:
> https://git-wip-us.apache.org/repos/asf?p=incubator-cmda.git
> and a mirror of it will be created on github, so
> the current github repository is a sandbox
> for us to get things organized but it’ll go away
> eventually. The mirror will be created under
> a different root dir on github.
> git root: JPL-WebService/
> -- JPL_CMDA: JPL-WebService/ 
>     -- frontend: ApacheCMDA-Frontend/ 
>     -- backend: services/ 
>     -- client: clients/ 
>     -- doc: doc/ 
> -- CMU_provenance: need one? yes
> Question: Do we create a git repository on Apache from scratch using github as ingredients,
or do we fix the github repository and import to Apache git?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message