incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bogdan DINU <flex.programm...@gmail.com>
Subject Re: New Spark components
Date Mon, 03 Dec 2012 07:20:35 GMT
Hello everyone,

as instructed, I have sent the ICLA to secretary and created JIRA issue
(improvement) - Flex - 33284<https://issues.apache.org/jira/browse/FLEX-33284>
.

Best regards,
Bogdan

On Tue, Nov 27, 2012 at 3:58 PM, Frédéric THOMAS <webdoublefx@hotmail.com>wrote:

> Hi Bogdan,
>
> I sent you a personnal email with the entire process too, I'll be away for
> 2-3 days, I suppose Erik or someone will take care of your donation.
>
> Thank you for your contribution.
>
> - Fred.
>
> -----Message d'origine----- From: Bogdan DINU
> Sent: Tuesday, November 27, 2012 11:46 AM
>
> To: flex-dev@incubator.apache.org
> Subject: Re: New Spark components
>
> Hi,
>
> I own the components - even if I have used them in a commercial project,
> the owners of it know that they are open source (aside with a Robotlegs
> alike framework which they wanted to support being opened).
>
> I have no idea what the acronyms like IIRC or ICLA means, but I'm
> definitely interested in donating those components - since I've brought
> them to the community attention in the first place.
>
> Looking forward to know about the necessary steps.
>
> Best regards,
> Bogdan
>
>
> On Tue, Nov 27, 2012 at 2:17 AM, Frédéric THOMAS <webdoublefx@hotmail.com>
> **wrote:
>
>  Ok, I just sent him an email with the all process, waitting now for its
>> feedback.
>>
>> Thank's guys.
>>
>>
>> -----Message d'origine----- From: Alex Harui
>> Sent: Tuesday, November 27, 2012 1:13 AM
>>
>> To: flex-dev@incubator.apache.org
>> Subject: Re: New Spark components
>>
>>
>>
>>
>> On 11/26/12 4:00 PM, "Frédéric THOMAS" <webdoublefx@hotmail.com> wrote:
>>
>>  Hi,
>>
>>>
>>>  Either way, we do have to verify the ownership of all of this work
>>>
>>>>
>>>>
>>> How does it happen ?
>>>
>>>  There used to be a checkbox on each JIRA issue where the patch submitter
>> had
>> to indicate that they owned their contribution.  I think that went away,
>> so
>> if it isn't there anymore, then I guess we just have to ask them.
>>
>> You should also review the code before committing to the code base and
>> handle any copyright notices according to Apache Legal.  And, of course,
>> in
>> your review, if you notice any obvious IP violation, you should stop and
>> address it before committing it.
>>
>>
>>  - Fred.
>>>
>>> -----Message d'origine-----
>>> From: Alex Harui
>>> Sent: Tuesday, November 27, 2012 12:53 AM
>>> To: flex-dev@incubator.apache.org
>>> Subject: Re: New Spark components
>>>
>>>
>>>
>>>
>>> On 11/26/12 3:01 PM, "Justin Mclean" <justin@classsoftware.com> wrote:
>>>
>>>  Hi,
>>>
>>>>
>>>>  8 months ago, Bogdan presented missing spark components[1] he did but
>>>> at
>>>>
>>>>> this
>>>>> time there was so much excitement on the ML, it has not been so
>>>>> noticed,
>>>>> I
>>>>> wanted to bring to your attention he wanted to contribute them, what¹s
>>>>> the
>>>>> process to integrate them into the SDK ?
>>>>>
>>>>>
>>>> Has he signed a ICLA? [1] Do we know that it's his own work or was it
>>>> work
>>>> done for someone else/a company?
>>>>
>>>>  IIRC, an ICLA is not mandatory for patches, but is a good idea for
>>> significant contributions.  Either way, we do have to verify the
>>> ownership
>>> of all of this work.
>>>
>>>
>>>> From a quick glance at the code I wouldn't see an issue with these been
>>>> added
>>>> to the experimental namespace and then moved into one of the other
>>>> namespaces
>>>> once they be in use for a while / have full tests.
>>>>
>>>> Thanks,
>>>> Justin
>>>>
>>>> 1. http://www.apache.org/****licenses/icla.txt<http://www.apache.org/**licenses/icla.txt>
>>>> <http://www.**apache.org/licenses/icla.txt<http://www.apache.org/licenses/icla.txt>
>>>> >
>>>>
>>>>
>>>  --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>>
>
> --
> http://www.badu.ro
>



-- 
http://www.badu.ro

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message