Hi James,

I’m guessing the one that Lei Pan summarized and sent to the list.
Can you check your email?

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: [email protected]
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++





-----Original Message-----
From: James Carman <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Thursday, March 17, 2016 at 4:40 PM
To: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [jira] [Commented] (CMDA-3) reorganize github repository

>What meeting?
>On Thu, Mar 17, 2016 at 7:39 PM Qihao Bao (JIRA) <[email protected]> wrote:
>
>>
>>     [
>> 
>>https://issues.apache.org/jira/browse/CMDA-3?page=com.atlassian.jira.plug
>>in.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200628#comme
>>nt-15200628
>> ]
>>
>> Qihao Bao commented on CMDA-3:
>> ------------------------------
>>
>> As discussed in the meeting this afternoon, i will take the initiative
>>of
>> setting up regular commit to Apache git.
>>
>> Qihao
>>
>> > 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?
>> > Create new git repository in Apache git. CMU will lead this effort.
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
>>

Reply via email to