Hi Rui, That's great news. Can you update the licensing in your GH repo to reflect the change to Apache License 2.0. Feel free to ask questions if you have them.
I think after that, we need to verify that there isn't 3rd-party code in your codebase, or at least identify what is 3rd party. The next question for you is whether you want to truly donate this code to Apache Flex. If you do, then after we review and import the code into an Apache repo, it would be recommended that you add some notification to your repo that all future work is being done with at Apache. If future work is done at Apache, that will give you less control over what kinds of changes are made to the code and the release process is a real process, but on the other hand, your customers will know that your code has been certified as ready to use in more ways than it is under GPL. Commercial developers can use it as well. Thanks, -Alex On 11/4/16, 12:42 PM, "Rui Cruz" <info.ruic...@gmail.com> wrote: >Hi there, > >I have no problem on changing the license. > >It would be great if more people contribute with the missing components. I >already use this set of extended spark components on released 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-components-with-Material-Design-tp14026p14051.html >Sent from the Apache Flex Users mailing list archive at Nabble.com.
