nabble.com/template/NamlServlet.jtp?macro=reply&node=12347
--
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-tp14026.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
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
y difference between GPL and MIT?
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-tp14026p14029.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
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 the license could be c
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)
e SDK?
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-tp14026p14040.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
lso drawbacks.
>
> What do others think?
> Is anyone interested in a Material Design component set that is shipped with
> the SDK?
>
> Thanks,
> Olaf
>
>
>
> --
> View this message in context:
> http://apache-flex-users.246.n4.nabble.com/Donating-Spark-
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 interested in a Material Design
on here.
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-tp14026p14050.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
ask.
--
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-tp14026p14051.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
eased apps that
>are
>used everyday by thousands of costumers (no complaints so far..) :)
>
>Whatever you need, just ask.
>
>
>
>--
>View this message in context:
>http://apache-flex-users.2333346.n4.nabble.com/Donating-Spark-Material-to-
>Apache-Flex-was-Spark-c
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
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
-
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-flex-users.2333346.n4.nabble.com/Donating-Spark-Material-to-
> Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14065.html
> To unsubscribe from Donati
Hi,
> So if I understood that changes will be made later right?
IMO intent is clear so we can sort out the details for you.
> Also, when I first mention donating, someone asked me some papers signed
It depends on the size of what donated, it’s would be best if you if you
submitted an ICLA [1].
is message in context:
http://apache-flex-users.2333346.n4.nabble.com/Donating-Spark-Material-to-Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14068.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
@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
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 an
www.apache.org/licenses/cla-corporate.txt
> >3. http://apache.org/licenses/#clas
>
>
>
> ------
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-flex-users.246.n4.nabble.com/Donating-Spark-M
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: I started this as a side-
committers to donate the missing pieces by
> re-creating them after donation. You might be able to do the re-creating
> yourself, but again that depends on whether the corporation would care or
> could care that they own the knowledge that is used to write those lines
> of code.
>
> HT
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
>legal problems here. And al
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 NO
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
t
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?
Than
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 license. That way Apache F
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 licen
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 OK with that then the owners
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 who
ine with changing the license then who owns what lines
> of code is moot as both (potential) owners agree it’s Apache licensed.
>
> Thanks,
> Justin
>
> ----------
> If you reply to this email, your message will be added to the discussion
> below:
> http:
as I said we need something from his company.
>>
>> If the company is fine with changing the license then who owns what
>>lines
>> of code is moot as both (potential) owners agree it’s Apache licensed.
>>
>> Thanks,
>> Justin
>>
>> --
> >
> >> 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 e
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 f
---
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-flex-users.2333346.n4.nabble.com/Donating-Spark-Material-to-
> Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14092.html
> To unsubscribe from Donating Spark-Material to A
tion because it would be great to leverage your existing (great)
> > codebase.
> >
> > This should not be that hard to figure out. We are here to help.
> >
> > Thanks,
> > Om
> >
> >
> > --------------
> > If you reply to t
e to Apache Flex. If it comes to that the
> > > community
> > > can get together and build this from scratch. This should be the last
> > > option because it would be great to leverage your existing (great)
> > > codebase.
> > >
> > > This should
e any objections. Record their response for future in case
>> > > someone
>> > > raises the issue.
>> > >
>> > > The worst case scenario is that the company owns the code and they
>> dont
>> > > agree to donate the code to Apache Flex
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 build scripts.
Thanks,
essage will be added to the discussion
> below:
> http://apache-flex-users.246.n4.nabble.com/Donating-Spark-Material-to-
> Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14103.html
> To unsubscribe from Donating Spark-Material to Apache Flex (was "Spark
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. You can spend some time
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
is message in context:
>http://apache-flex-users.2333346.n4.nabble.com/Donating-Spark-Material-to-
>Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14114.html
>Sent from the Apache Flex Users mailing list archive at Nabble.com.
i=0>> wrote:
>
> >Hi,
> >
> >I got a reply from Foundation saying what ICLA was filed, whats next?
> >
> >
> >Regards,
> >Rui
> >
> >
> >
> >
> >--
> >View this message in context:
> >http:
33346.n4.nabble.com/
>> Donating-Spark-Material-to-
>>> Apache-Flex-was-Spark-components-with-Material-Design-tp14026p14114.html
>>> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>>
>>
>>
>> --
>
Fantastic links btw.
-Mark
-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: Thursday, November 03, 2016 5:30 PM
To: users@flex.apache.org
Subject: [Non-DoD Source] Re: Donating Spark-Material to Apache Flex (was
"Spark components with Material Design&
45 matches
Mail list logo
