You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@asterixdb.apache.org by Ate Douma <at...@douma.nu> on 2015/03/26 22:02:23 UTC
infra next steps?
Gavin just asked on https://issues.apache.org/jira/browse/INFRA-9306 if there is
anything else pending for infra to setup?
I think the next step would be the initial code import, right?
For which the SGA first needs to be provided.
If there is anything else to setup which infra can pick up, we should create
tickets for them.
Ate
Re: infra next steps?
Posted by Till Westmann <ti...@apache.org>.
I’ve created an issue to ask the question: https://issues.apache.org/jira/browse/INFRA-9352 <https://issues.apache.org/jira/browse/INFRA-9352>
For the actual import we should probably wait until we’ve got the code in place as well.
Cheers,
Till
> On Mar 28, 2015, at 3:58 PM, Till Westmann <ti...@apache.org> wrote:
>
> Hi,
>
>> On Mar 27, 2015, at 8:55 PM, Mattmann, Chris A (3980) <chris.a.mattmann@jpl.nasa.gov <ma...@jpl.nasa.gov>> wrote:
>>
>> There is a Google Doc - can Till send a link around if anyone
>> hasn’t done an ICLA yet?
>
> Here’s to doc: http://goo.gl/XAuNOZ <http://goo.gl/XAuNOZ>
> But to save the trip to the doc: everybody on the list has filed the ICLA, but Inci doesn’t have an account yet.
>
>> As for importing JIRA issues - it can be done - but is difficult
>> depending on the JIRA versions etc.
>
> It seems that we don’t have to much variance regarding the JIRA version (probably infra is only running 1 version).
> But I’m wondering if anybody has experience mapping Goole Code issue fields to JIRA fields ...
>
>> I would recommend to work with
>> infra and then to please copy the list as steps are progressed. First
>> step may be to create a ticket to do the import.
>
> Sounds good. Will do that.
>
> Cheers,
> Till
>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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: chris.a.mattmann@nasa.gov <ma...@nasa.gov>
>> WWW: http://sunset.usc.edu/~mattmann/ <http://sunset.usc.edu/~mattmann/>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Associate Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Henry Saputra <henry.saputra@gmail.com <ma...@gmail.com>>
>> Reply-To: "dev@asterixdb.incubator.apache.org <ma...@asterixdb.incubator.apache.org>"
>> <dev@asterixdb.incubator.apache.org <ma...@asterixdb.incubator.apache.org>>
>> Date: Thursday, March 26, 2015 at 4:43 PM
>> To: "dev@asterixdb.incubator.apache.org <ma...@asterixdb.incubator.apache.org>"
>> <dev@asterixdb.incubator.apache.org <ma...@asterixdb.incubator.apache.org>>
>> Subject: Re: infra next steps?
>>
>>> Hmm never try it before. Maybe Google code could help if we send email to
>>> them?
>>>
>>> Hopefully they have escape plan before shutting down.
>>>
>>> Till, have all initial committers signed the ICLA and got account?
>>>
>>> - Henry
>>>
>>> On Thu, Mar 26, 2015 at 4:01 PM, Till Westmann <tillw@apache.org <ma...@apache.org>> wrote:
>>>> We've got the mailing list, the JIRA project and now 2 git repos.
>>>> We didn't ask for anything more so far.
>>>> Is there something else that's usually needed?
>>>>
>>>> An interesting question could be, if there's a way to import existing
>>>> bugs
>>>> from the current issue trackers (AsterixDB and Hyracks) on Google Code.
>>>> Do you know of if somebody has automated that process before?
>>>>
>>>> Thanks,
>>>> Till
>>>>
>>>>
>>>> On 26 Mar 2015, at 14:02, Ate Douma wrote:
>>>>
>>>>> Gavin just asked on https://issues.apache.org/jira/browse/INFRA-9306 <https://issues.apache.org/jira/browse/INFRA-9306> if
>>>>> there is anything else pending for infra to setup?
>>>>>
>>>>> I think the next step would be the initial code import, right?
>>>>> For which the SGA first needs to be provided.
>>>>>
>>>>> If there is anything else to setup which infra can pick up, we should
>>>>> create tickets for them.
>>>>>
>>>>> Ate
>>
>
Re: infra next steps?
Posted by Till Westmann <ti...@apache.org>.
Hi,
> On Mar 27, 2015, at 8:55 PM, Mattmann, Chris A (3980) <ch...@jpl.nasa.gov> wrote:
>
> There is a Google Doc - can Till send a link around if anyone
> hasn’t done an ICLA yet?
Here’s to doc: http://goo.gl/XAuNOZ <http://goo.gl/XAuNOZ>
But to save the trip to the doc: everybody on the list has filed the ICLA, but Inci doesn’t have an account yet.
> As for importing JIRA issues - it can be done - but is difficult
> depending on the JIRA versions etc.
It seems that we don’t have to much variance regarding the JIRA version (probably infra is only running 1 version).
But I’m wondering if anybody has experience mapping Goole Code issue fields to JIRA fields ...
> I would recommend to work with
> infra and then to please copy the list as steps are progressed. First
> step may be to create a ticket to do the import.
Sounds good. Will do that.
Cheers,
Till
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
>
> -----Original Message-----
> From: Henry Saputra <he...@gmail.com>
> Reply-To: "dev@asterixdb.incubator.apache.org"
> <de...@asterixdb.incubator.apache.org>
> Date: Thursday, March 26, 2015 at 4:43 PM
> To: "dev@asterixdb.incubator.apache.org"
> <de...@asterixdb.incubator.apache.org>
> Subject: Re: infra next steps?
>
>> Hmm never try it before. Maybe Google code could help if we send email to
>> them?
>>
>> Hopefully they have escape plan before shutting down.
>>
>> Till, have all initial committers signed the ICLA and got account?
>>
>> - Henry
>>
>> On Thu, Mar 26, 2015 at 4:01 PM, Till Westmann <ti...@apache.org> wrote:
>>> We've got the mailing list, the JIRA project and now 2 git repos.
>>> We didn't ask for anything more so far.
>>> Is there something else that's usually needed?
>>>
>>> An interesting question could be, if there's a way to import existing
>>> bugs
>>> from the current issue trackers (AsterixDB and Hyracks) on Google Code.
>>> Do you know of if somebody has automated that process before?
>>>
>>> Thanks,
>>> Till
>>>
>>>
>>> On 26 Mar 2015, at 14:02, Ate Douma wrote:
>>>
>>>> Gavin just asked on https://issues.apache.org/jira/browse/INFRA-9306 if
>>>> there is anything else pending for infra to setup?
>>>>
>>>> I think the next step would be the initial code import, right?
>>>> For which the SGA first needs to be provided.
>>>>
>>>> If there is anything else to setup which infra can pick up, we should
>>>> create tickets for them.
>>>>
>>>> Ate
>
Re: infra next steps?
Posted by "Mattmann, Chris A (3980)" <ch...@jpl.nasa.gov>.
Hi Everyone,
There is a Google Doc - can Till send a link around if anyone
hasn’t done an ICLA yet?
As for importing JIRA issues - it can be done - but is difficult
depending on the JIRA versions etc. I would recommend to work with
infra and then to please copy the list as steps are progressed. First
step may be to create a ticket to do the import.
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: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message-----
From: Henry Saputra <he...@gmail.com>
Reply-To: "dev@asterixdb.incubator.apache.org"
<de...@asterixdb.incubator.apache.org>
Date: Thursday, March 26, 2015 at 4:43 PM
To: "dev@asterixdb.incubator.apache.org"
<de...@asterixdb.incubator.apache.org>
Subject: Re: infra next steps?
>Hmm never try it before. Maybe Google code could help if we send email to
>them?
>
>Hopefully they have escape plan before shutting down.
>
>Till, have all initial committers signed the ICLA and got account?
>
>- Henry
>
>On Thu, Mar 26, 2015 at 4:01 PM, Till Westmann <ti...@apache.org> wrote:
>> We've got the mailing list, the JIRA project and now 2 git repos.
>> We didn't ask for anything more so far.
>> Is there something else that's usually needed?
>>
>> An interesting question could be, if there's a way to import existing
>>bugs
>> from the current issue trackers (AsterixDB and Hyracks) on Google Code.
>> Do you know of if somebody has automated that process before?
>>
>> Thanks,
>> Till
>>
>>
>> On 26 Mar 2015, at 14:02, Ate Douma wrote:
>>
>>> Gavin just asked on https://issues.apache.org/jira/browse/INFRA-9306 if
>>> there is anything else pending for infra to setup?
>>>
>>> I think the next step would be the initial code import, right?
>>> For which the SGA first needs to be provided.
>>>
>>> If there is anything else to setup which infra can pick up, we should
>>> create tickets for them.
>>>
>>> Ate
Re: infra next steps?
Posted by Ate Douma <at...@douma.nu>.
On 2015-03-27 03:29, Till Westmann wrote:
>
>> On Mar 26, 2015, at 4:43 PM, Henry Saputra <he...@gmail.com> wrote:
>>
>> Hmm never try it before. Maybe Google code could help if we send email to them?
>>
>> Hopefully they have escape plan before shutting down.
>
> I have looked around a bit and it seems that there’s a way from Google Code to GitHub and a way from GitHub to JIRA, but that doesn’t sound right. Google used to have an API for the issues, but that was shut down some time ago …
>
> Maybe somebody else on this list has a better idea than going through GitHub ...
I don't know if other incubator projects/infra did this before, but I suggest
raising this question on general@incubator, cc infrastructure-dev@
>
>> Till, have all initial committers signed the ICLA and got account?
>
> All ICLAs should be filed, but I think that Inci doesn’t have an account yet.
>
> Till
>
>> On Thu, Mar 26, 2015 at 4:01 PM, Till Westmann <ti...@apache.org> wrote:
>>> We've got the mailing list, the JIRA project and now 2 git repos.
>>> We didn't ask for anything more so far.
>>> Is there something else that's usually needed?
>>>
>>> An interesting question could be, if there's a way to import existing bugs
>>> from the current issue trackers (AsterixDB and Hyracks) on Google Code.
>>> Do you know of if somebody has automated that process before?
>>>
>>> Thanks,
>>> Till
>>>
>>>
>>> On 26 Mar 2015, at 14:02, Ate Douma wrote:
>>>
>>>> Gavin just asked on https://issues.apache.org/jira/browse/INFRA-9306 if
>>>> there is anything else pending for infra to setup?
>>>>
>>>> I think the next step would be the initial code import, right?
>>>> For which the SGA first needs to be provided.
>>>>
>>>> If there is anything else to setup which infra can pick up, we should
>>>> create tickets for them.
>>>>
>>>> Ate
>
Re: infra next steps?
Posted by Till Westmann <ti...@apache.org>.
> On Mar 26, 2015, at 4:43 PM, Henry Saputra <he...@gmail.com> wrote:
>
> Hmm never try it before. Maybe Google code could help if we send email to them?
>
> Hopefully they have escape plan before shutting down.
I have looked around a bit and it seems that there’s a way from Google Code to GitHub and a way from GitHub to JIRA, but that doesn’t sound right. Google used to have an API for the issues, but that was shut down some time ago …
Maybe somebody else on this list has a better idea than going through GitHub ...
> Till, have all initial committers signed the ICLA and got account?
All ICLAs should be filed, but I think that Inci doesn’t have an account yet.
Till
> On Thu, Mar 26, 2015 at 4:01 PM, Till Westmann <ti...@apache.org> wrote:
>> We've got the mailing list, the JIRA project and now 2 git repos.
>> We didn't ask for anything more so far.
>> Is there something else that's usually needed?
>>
>> An interesting question could be, if there's a way to import existing bugs
>> from the current issue trackers (AsterixDB and Hyracks) on Google Code.
>> Do you know of if somebody has automated that process before?
>>
>> Thanks,
>> Till
>>
>>
>> On 26 Mar 2015, at 14:02, Ate Douma wrote:
>>
>>> Gavin just asked on https://issues.apache.org/jira/browse/INFRA-9306 if
>>> there is anything else pending for infra to setup?
>>>
>>> I think the next step would be the initial code import, right?
>>> For which the SGA first needs to be provided.
>>>
>>> If there is anything else to setup which infra can pick up, we should
>>> create tickets for them.
>>>
>>> Ate
Re: infra next steps?
Posted by Henry Saputra <he...@gmail.com>.
Hmm never try it before. Maybe Google code could help if we send email to them?
Hopefully they have escape plan before shutting down.
Till, have all initial committers signed the ICLA and got account?
- Henry
On Thu, Mar 26, 2015 at 4:01 PM, Till Westmann <ti...@apache.org> wrote:
> We've got the mailing list, the JIRA project and now 2 git repos.
> We didn't ask for anything more so far.
> Is there something else that's usually needed?
>
> An interesting question could be, if there's a way to import existing bugs
> from the current issue trackers (AsterixDB and Hyracks) on Google Code.
> Do you know of if somebody has automated that process before?
>
> Thanks,
> Till
>
>
> On 26 Mar 2015, at 14:02, Ate Douma wrote:
>
>> Gavin just asked on https://issues.apache.org/jira/browse/INFRA-9306 if
>> there is anything else pending for infra to setup?
>>
>> I think the next step would be the initial code import, right?
>> For which the SGA first needs to be provided.
>>
>> If there is anything else to setup which infra can pick up, we should
>> create tickets for them.
>>
>> Ate
Re: infra next steps?
Posted by Till Westmann <ti...@apache.org>.
We've got the mailing list, the JIRA project and now 2 git repos.
We didn't ask for anything more so far.
Is there something else that's usually needed?
An interesting question could be, if there's a way to import existing
bugs from the current issue trackers (AsterixDB and Hyracks) on Google
Code.
Do you know of if somebody has automated that process before?
Thanks,
Till
On 26 Mar 2015, at 14:02, Ate Douma wrote:
> Gavin just asked on https://issues.apache.org/jira/browse/INFRA-9306
> if there is anything else pending for infra to setup?
>
> I think the next step would be the initial code import, right?
> For which the SGA first needs to be provided.
>
> If there is anything else to setup which infra can pick up, we should
> create tickets for them.
>
> Ate