Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Yes. There’s a ColorUtil class. On Nov 15, 2016, at 12:14 PM, Rui Cruz wrote: > Ok, I'll create a new branch and check where I can find some ColorUtils > (Doesn't the FlexSDK already haves one?). > > > Thank you > > > > 2016-11-14 17:03 GMT+00:00 Alex Harui [via

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Ok, I'll create a new branch and check where I can find some ColorUtils (Doesn't the FlexSDK already haves one?). Thank you 2016-11-14 17:03 GMT+00:00 Alex Harui [via Apache Flex Users] < ml-node+s246n14116...@n4.nabble.com>: > Hi Rui, > > I saw that it got recorded as well. Next step

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi Rui, I saw that it got recorded as well. Next step is for you decide exactly what to donate. If there are files you think may have too much stuff borrowed from the internet, please chase down where you got it from, or make a branch in your repo and remove it. The goal is for you to say in

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, I got a reply from Foundation saying what ICLA was filed, whats next? Regards, Rui -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Donating-Spark-Material-to-Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14114.html Sent from the Apache

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

On 11/11/16, 10:37 AM, "Rui Cruz" wrote: >I must say that the last addition of the ColorPicker, I toke the HSV/RGB >stuff somewhere from the net and don't remember where :s maybe it's better >replace by something already done inside Flex SDK.. I guess it is up to you.

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

I must say that the last addition of the ColorPicker, I toke the HSV/RGB stuff somewhere from the net and don't remember where :s maybe it's better replace by something already done inside Flex SDK.. 2016-11-11 18:27 GMT+00:00 Alex Harui [via Apache Flex Users] <

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

On 11/11/16, 9:07 AM, "Rui Cruz" wrote: > >Ok I've sent an empty email with signed icla. Now I wait? Well, yes, there is some waiting involved. If any committers have time they can start reviewing code more closely. Also, we can discuss where this goes in the repo and

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

I'm sorry.. I read it now.. Please send only one document per email. Ok I've sent an empty email with signed icla. Now I wait? 2016-11-11 17:05 GMT+00:00 Rui Cruz : > Hi, > > Is there some email template to send the icla to secret...@apache.org? > > Do I need to

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, Is there some email template to send the icla to secret...@apache.org? Do I need to identify the project? my repo? Thank you, Rui 2016-11-10 3:10 GMT+00:00 OmPrakash Muppirala [via Apache Flex Users] < ml-node+s246n14094...@n4.nabble.com>: > On Wed, Nov 9, 2016 at 6:35 PM, Rui Cruz

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

On Wed, Nov 9, 2016 at 6:35 PM, Rui Cruz wrote: > Hi Om, > > The code is mine, but I may added some features/fixed some stuff during > working time (anyway the company was fine with that and they know this was > a side project of mine that I "donate" to the company for

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Rui, First of all, fantastic work in this project and thanks for willing to donate it to Apache Flex. The issue here is very simple. Either you own this code or your company owns it. If you say that you own it, you can just simply donate it. If your company owns the code, you need permission

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi Alex, So, in my company we are 3 developers and I'm the only one using Flex and the two are backing up server/cms/etc.., this is mid-size company with a very lithe TI team, and the apps we make is for help selling company products.. so the company doesn't care what tech or framework is used,

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi Rui, Unfortunately, donating code to Apache can be really painful. Apache's main goal is to make sure that the source code it releases is the easiest to consume, so we have to scrub all donations, to eliminate the possibility that if some customer builds a mission-critical application based

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, > I thought that the repo was originally licensed under GPL or something other > than ALv2. Correct it was GPL. > Rui can't just relicense it to ALv2 unless he owns every line. Correct as I said we need something from his company. If the company is fine with changing the license then

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

On 11/9/16, 2:40 PM, "Justin Mclean" wrote: >Hi, > >> Fundamentally, the question here is which lines of code are truly owned >>by >> Rui and which are owned by his company. > >If it’s Apache 2.0 licensed and we have something from that company >saying that they are

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, > Even the software grant does not change ownership. Yep sorry about that, you’re correct It just gives the ASF a license to use it how they want. > Fundamentally, the question here is which lines of code are truly owned by > Rui and which are owned by his company. If it’s Apache 2.0

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

On 11/9/16, 1:55 PM, "Justin Mclean" wrote: >Hi, > >> @Justin >> I don't understand the NOTICE thing... what is the PRODUCT_NAME? >> ("Apache Flex", "Spark material", "Apache Flex Spark Material", ...) > >You have two options. >1, Relicense the project under an Apache

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, > @Justin Do you think there's a chance to include "Spark-Material" with 4.16.0? If we can sort out the licensing/ownership issues sure. What need to be done to include it into the SDK other than adding the files? I assume it would need to be added as a module and compiled into a swf?

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, > My contract is a simple general contract (like any other employee here > being a developer or not). This is not a "software" company, and all > developments made are for own company use / company customers use. If you relicense the code under an Apache license and your company is fine by

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, > @Justin > I don't understand the NOTICE thing... what is the PRODUCT_NAME? > ("Apache Flex", "Spark material", "Apache Flex Spark Material", ...) You have two options. 1, Relicense the project under an Apache license. That way Apache Flex can use it, for this is would be helpful to adda

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

On 11/9/16, 9:52 AM, "Rui Cruz" wrote: >Hi Alex, > >My contract is a simple general contract (like any other employee here >being a developer or not). This is not a "software" company, and all >developments made are for own company use / company customers use. So no

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

On 11/9/16, 8:53 AM, "Rui Cruz" wrote: >I have one doubt, I will not make contributions on behalf the corporation >that I'm working on (I'll make on my own).. But.. If the corporation let's >me upgrade/change/use the code of my repo, that makes corporation code? >case:

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

I have one doubt, I will not make contributions on behalf the corporation that I'm working on (I'll make on my own).. But.. If the corporation let's me upgrade/change/use the code of my repo, that makes corporation code? case: I started this as a side-project, the company liked and I let the

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

If Justin is ok with not using a Software Grant, that's fine with me. So, AIUI, the "paperwork" involved is: 1) send an email to dev@ (instead of users@) indicating your intent to donate your code and give consent to allow other Apache Flex committers to help you fix your file headers. 2) file

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

@Justin Do you think there's a chance to include "Spark-Material" with 4.16.0? Thanks, Olaf -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Donating-Spark-Material-to-Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14069.html Sent from the Apache

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Rui Cruz wrote > So if I understood that changes will be made later right? Or for easiest > process and no mistakes, can someone make a pullrequest with the necessary > changes? @Rui I would try to add the Apache license header to each particular file tonight, seems that's sort of a monkey work

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi Justin, So if I understood that changes will be made later right? Or for easiest process and no mistakes, can someone make a pullrequest with the necessary changes? Also, when I first mention donating, someone asked me some papers signed.. Aren't that need anymore? Thanks, Rui 2016-11-09

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, > I've changed the LICENSE, pls check if its ok. Minor issues, you don’t have the full Apache license text [1] or a NOTICE file [2] and files don’t have an Apache license headers [3]. You might want actually want a NOTICE file as that means you get added to our NOTICE file. [4] But no big

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi Alex, I've changed the LICENSE, pls check if its ok. Regards -- View this message in context: http://apache-flex-users.246.n4.nabble.com/Donating-Spark-Material-to-Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14064.html Sent from the Apache Flex Users mailing list

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

On 11/4/16, 1:56 AM, "OK" wrote: >Thank you Justin! > >Reading Alex hints I'm not sure what would be the right way: >Keeping the material lib external or as part of Apache Flex. >Probably both have benefits and also drawbacks. > >What do others think? >Is anyone

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

would be nice to have material set in the SDK > On 4 Nov 2016, at 09:56, OK wrote: > > Thank you Justin! > > Reading Alex hints I'm not sure what would be the right way: > Keeping the material lib external or as part of Apache Flex. > Probably both have benefits and also

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Thank you Justin! Reading Alex hints I'm not sure what would be the right way: Keeping the material lib external or as part of Apache Flex. Probably both have benefits and also drawbacks. What do others think? Is anyone interested in a Material Design component set that is shipped with the SDK?

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, > Do you know the key difference between GPL and MIT? This probably explains it better than I can [1][2][3] Thanks, Justin 1. http://choosealicense.com 2. https://tldrlegal.com/license/apache-license-2.0-(apache-2.0) 3. https://tldrlegal.com/license/gnu-general-public-license-v3-(gpl-3)

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

On 11/3/16, 7:56 AM, "OK" wrote: >jmclean wrote >> Yes one very large one [1], the GPL license is not compatible with >>Apache >> [2]. >> But if Rui Cruz was willing to donate it under another (compatible) >> license that is likely to be fine. > >Thanks Justin. >Hopefully

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

jmclean wrote > Yes one very large one [1], the GPL license is not compatible with Apache > [2]. > But if Rui Cruz was willing to donate it under another (compatible) > license that is likely to be fine. Thanks Justin. Hopefully the license could be changed to MIT. Do you know the key difference

Re: Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, > Are there any concerns? Yes one very large one [1], the GPL license is not compatible with Apache [2]. But if Rui Cruz was willing to donate it under another (compatible) license that is likely to be fine. Thanks, Justin 1. https://github.com/rui-cruz/Spark-Material/blob/master/LICENSE

Donating Spark-Material to Apache Flex (was "Spark components with Material Design")

Hi, I just would like to revive the idea of donating Rui Cruz spark material lib [1] to Apache Flex. This is the origin thread [2]. Maybe we could achive this within the 4.16.0 release, that would be great. I've already contact Rui and he said that he's fine with it. I think we have to clean up