Hi,

coming back to this. I think that it would be the “right” choice to have 2 
repositories here. However, 
a) I’m not sure if “1 repository per project" is an unchangeable rules and 
b) if other people think differently about this.

What are your thoughts/opinions on this?

Thanks,
Till

> On Mar 16, 2015, at 10:56 PM, Till Westmann <[email protected]> wrote:
> 
> So far they were released separately as other projects depend on Hyracks as 
> well (Apache VXQuery, Pregelix (not Apache)). We actually briefly considered 
> to propose both projects separately, but since they are developed by the same 
> community and we’ve heard “community over code” more than once, it seemed 
> more appropriate to have 1 project for 1 community. 
> What that the “right” choice or would we have gotten different advice if we 
> had discussed this before starting incubation?
> 
> Thanks,
> Till
> 
>> On Mar 16, 2015, at 7:09 PM, Henry Saputra <[email protected]> wrote:
>> 
>> My thinking was just to have to directories under main git repo for
>> asterixdb and hyracks. The README.md then describe what each directory
>> contains.
>> 
>> The drawback is that those 2 modules now work as one for both releases
>> and branches, which I think makes sense from project perspective.
>> 
>> On Sun, Mar 15, 2015 at 4:57 PM, Till Westmann <[email protected]> wrote:
>>> Hi Henry,
>>> 
>>> not sure, never tried to work like this with git :)
>>> Do you know by any chance if it is possible to create branches for 
>>> sub-modules (not need to google for, I can do that if you haven't tried 
>>> either).
>>> 
>>> Thanks,
>>> Till
>>> 
>>> 
>>>> On Mar 15, 2015, at 4:45 PM, Henry Saputra <[email protected]> wrote:
>>>> 
>>>> HI Till,
>>>> 
>>>> I believe usually one ASF project will get one source repo.
>>>> Would it be easier to have 2 sub-modules of asterixdb and hyracks?
>>>> 
>>>> - Henry
>>>> 
>>>> On Sun, Mar 15, 2015 at 3:36 PM, Till Westmann <[email protected]> wrote:
>>>>> Hi Chris,
>>>>> 
>>>>> Thanks!
>>>>> 
>>>>> I’ve got a few questions:
>>>>> 
>>>>> 1) Should we import the code already before we are clear on the SGA?
>>>>> 2) Currently we actually have 2 repositories, one for AsterixDB and one 
>>>>> for Hyracks. And since we have other projects that depend on Hyracks that 
>>>>> actually makes some sense. Would it be possible to have 2 repositories 
>>>>> here as well? (Sorry, I should have come up with that question earlier …).
>>>>> 3) Does anybody know if there’s an easy (automated) way to migrate issues 
>>>>> from Google Code to the Apache JIRA.
>>>>> 
>>>>> Thanks,
>>>>> Till
>>>>> 
>>>>>> On Mar 15, 2015, at 2:19 PM, Mattmann, Chris A (3980) 
>>>>>> <[email protected]> wrote:
>>>>>> 
>>>>>> Hi Everyone,
>>>>>> 
>>>>>> Our Git repo is now up thanks to INFRA:
>>>>>> 
>>>>>> https://issues.apache.org/jira/browse/INFRA-9212
>>>>>> 
>>>>>> 
>>>>>> Yay!
>>>>>> 
>>>>>> I know we are working on the SGA, but if folks want to use
>>>>>> it, please feel free.
>>>>>> 
>>>>>> Also our JIRA instance is also up:
>>>>>> 
>>>>>> https://issues.apache.org/jira/browse/INFRA-9213
>>>>>> 
>>>>>> It’s accessible at:
>>>>>> 
>>>>>> https://issues.apache.org/jira/browse/ASTERIXDB
>>>>>> 
>>>>>> 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/
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> Adjunct Associate Professor, Computer Science Department
>>>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>> 
> 

Reply via email to