You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Justin Mclean <ju...@classsoftware.com> on 2016/11/01 23:02:32 UTC
New Flex SDK release
Hi,
It’s been quite a while (10 months!) since we’ve made a new Flex SDK release, and there's a number of changes and fixes that have been made in develop.
If no-one else want to be the release manager I’ll put my hand up for the role.
Thanks,
Justin
Re: New Flex SDK release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
I created a JIRA to track the progress here [1]. If anyone want to help out please assign themselves one of the sub tasks.
Thanks,
Justin
1. https://issues.apache.org/jira/browse/FLEX-35146
Re: Icon fonts (was Re: New Flex SDK release)
Posted by Fabrice Montfort <fm...@runware.com>.
Hi guys,
Material icons (https://material.io/icons/) is available under Apache
License. It can be a serious alternative to Font Awesome.
Hope it helps.
Regards,
Fabrice Montfort
2016-11-03 11:08 GMT+04:00 Harbs <ha...@gmail.com>:
> In morre general terms:
>
> While we obviously cannot include content with incompatible licenses, I do
> think we should make it easy for users who want to use such content with
> FlexJS. For example, if a user has a license to Font Awesome Pro, it should
> be easy to do something to their config and just pull that in.
>
> Font Awesome is not the only icon font option out there. There will be
> users who will want to use others. There’s probably a way to do this kind
> of thing today but it’s something we need to at the least document.
>
> Harbs
>
> On Nov 3, 2016, at 9:01 AM, Justin Mclean <ju...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> >> There will be still a community Version... Is this also incompatible
> with Apache?
> >
> > The 4.7 community version is under a variety of license of which the
> code and font are under a compatible license [1]. Their documentation isn’t
> under a compatible license.
> >
> > Hopefully this will be the same for 5.0. The 5.0 Pro version certainly
> isn’t compatible and it seems to be getting the larger update.
> >
> > I assume we are only using the font files?
> >
> > Thanks,
> > Justin
> >
> > 1. http://fontawesome.io/license/
>
>
--
*Fabrice Montfort / CTO*
*fm@runware.com <fm...@runware.com>*
* <http://www.runware.fr/>*
Phone : +262 (0)262 28 67 30 / Mobile : +262 (0)692 93 57 10
13, rue Désiré Barquisseau • 97410 Saint-Pierre • Réunion, France •
http://www.runware.fr
*Nos applications :*
<http://pillkit.runware.fr/> <http://checkit.runware.fr/>
<http://dietekit.runware.fr/> <http://tenkit.runware.fr/>
<http://pulseekit.runware.fr/>
CONFIDENTIALITY NOTICE – This electronic message contains information which
may be confidential. The information is intended for the use of the
individual or entity identified above. If you are not the intended
recipient, please be aware that any disclosure, copying, distribution or
use of the contents of this message is strictly prohibited. If you receive
this transmission in error, please notify the sender and delete the copy
you received.
Icon fonts (was Re: New Flex SDK release)
Posted by Harbs <ha...@gmail.com>.
In morre general terms:
While we obviously cannot include content with incompatible licenses, I do think we should make it easy for users who want to use such content with FlexJS. For example, if a user has a license to Font Awesome Pro, it should be easy to do something to their config and just pull that in.
Font Awesome is not the only icon font option out there. There will be users who will want to use others. There’s probably a way to do this kind of thing today but it’s something we need to at the least document.
Harbs
On Nov 3, 2016, at 9:01 AM, Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
>> There will be still a community Version... Is this also incompatible with Apache?
>
> The 4.7 community version is under a variety of license of which the code and font are under a compatible license [1]. Their documentation isn’t under a compatible license.
>
> Hopefully this will be the same for 5.0. The 5.0 Pro version certainly isn’t compatible and it seems to be getting the larger update.
>
> I assume we are only using the font files?
>
> Thanks,
> Justin
>
> 1. http://fontawesome.io/license/
Re: New Flex SDK release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> This is the modified AwesomeUtils.as [1] which includes the update to
> FontAwesome 4.7 and the MIT licence header that replaces the Apache license
> header.
Looks good to me.
> Should I commit it to the 4.16.0 branch?
Yep when ever you have time to do so that would be great.
Thanks,
Justin
Re: New Flex SDK release
Posted by OK <po...@olafkrueger.net>.
Justin Mclean wrote
> I’m not a lawyer but looking at the file I’d use the MIT header only.
This is the modified AwesomeUtils.as [1] which includes the update to
FontAwesome 4.7 and the MIT licence header that replaces the Apache license
header.
If this is ok I'll commit it to the origin Flex repo soon (including the
FontAwesome.otf).
Should I commit it to the 4.16.0 branch?
Thanks,
Olaf
[1]
https://github.com/ok-at-github/flex-sdk/blob/develop/frameworks/projects/flatspark/src/flatspark/utils/AwesomeUtils.as
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/New-Flex-SDK-release-tp56153p56195.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: New Flex SDK release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Should I replace the Apache license header by the MIT one or should I add
> the MIT header under the Apache license header?
Generally the changes have to be extensive to change the header on a file, translation from one language to another generaly doesn’t count.
I’m not a lawyer but looking at the file I’d use the MIT header only.
Particularly in this case as the content could be considered non creative. (No offence intended :-) but it may be that you don’t have copyright on that file because of that - either way t’s not an issue.)
Thanks,
Justin
Re: New Flex SDK release
Posted by OK <po...@olafkrueger.net>.
>Yes that an option (and given as one on legal discuss).
Great! One last question:
Should I replace the Apache license header by the MIT one or should I add
the MIT header under the Apache license header?
Thanks!
Olaf
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/New-Flex-SDK-release-tp56153p56193.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: New Flex SDK release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I'm also not a layer and I don't want to trigger another license disucssion
> here but is it not enough to just add the MIT license text as additional
> header to the affected files including the required copyright info?
Yes that an option (and given as one on legal discuss).
Given the github issue has been open since 2014 (almost 2 years) and may not be resolved any time soon I think that would be an appropriate approach.
> Additionaly a license summary file that lists affected files where we can't
> place a license text (e.g. FontAwesome.otf) makes sense.
Yep no issue there and we already do that.
Thanks,
Justin
Re: New Flex SDK release
Posted by OK <po...@olafkrueger.net>.
I'm also not a layer and I don't want to trigger another license disucssion
here but is it not enough to just add the MIT license text as additional
header to the affected files including the required copyright info?
MIT license:
"The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software."
Additionaly a license summary file that lists affected files where we can't
place a license text (e.g. FontAwesome.otf) makes sense.
Thanks,
Olaf
[1] https://opensource.org/licenses/mit-license.html
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/New-Flex-SDK-release-tp56153p56191.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: New Flex SDK release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
And it turns out this is a know outstanding issue (for a while) and other people have the same issue :-( [1]
Justin
1. https://github.com/FortAwesome/Font-Awesome/issues/5281
Re: New Flex SDK release
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Justin,
Guess I would opt to work on that path, but I’m not going to put up with the build. So probably the path would be to migrate the FlexSDK to be buildable with maven and as soon as I have a stable system with good test coverage, to start cleaning this up. But at the moment I don’t know it it’s worth investing the time to do this migration.
Chris
Am 03.11.16, 09:12 schrieb "Justin Mclean" <ju...@classsoftware.com>:
Hi,
> One thing I would really be dleighted about, would be, if we could get rid of the patched libraries used in the sdk.
> However I don’t have any idea what sideeffects this would have.
Way back I did look into doing so but was going to be a lot of work for Bartik as Adobe made a large number of changes to the code base that would be hard to apply to later versions.
While I agree it would be a nice to have, IMO we just don’t have enough people to do the work or know that code well enough or enough test coverage to know if it’s broken or not even if we did get it working on a later version. :-(
Thanks,
Justin
Re: New Flex SDK release
Posted by Alex Harui <ah...@adobe.com>.
On 11/3/16, 1:12 AM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>Hi,
>
>> One thing I would really be dleighted about, would be, if we could get
>>rid of the patched libraries used in the sdk.
>> However I don’t have any idea what sideeffects this would have.
>
>Way back I did look into doing so but was going to be a lot of work for
>Bartik as Adobe made a large number of changes to the code base that
>would be hard to apply to later versions.
AIUI, changes were made to Batik to allow Flex-specific CSS properties
that do not follow the CSS standard. My understanding is that vendor or
product-specific properties are supposed to be prefixed with things like
-mozilla or -webkit and thus Flex properties probably should have started
with -flex, but the Flex team decided to just add new properties without
any prefix. I don't think we want to force existing Flex users to adopt
CSS-standard property naming, and I don't see how we could contribute
these changes back to Batik. If I were on the Batik PMC, I wouldn't want
them.
So, I'm pretty sure something will break if we try to use an official
unmodified Batik release. IMO, the question is whether there is a better
way to manage these modifications.
-Alex
Re: New Flex SDK release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> One thing I would really be dleighted about, would be, if we could get rid of the patched libraries used in the sdk.
> However I don’t have any idea what sideeffects this would have.
Way back I did look into doing so but was going to be a lot of work for Bartik as Adobe made a large number of changes to the code base that would be hard to apply to later versions.
While I agree it would be a nice to have, IMO we just don’t have enough people to do the work or know that code well enough or enough test coverage to know if it’s broken or not even if we did get it working on a later version. :-(
Thanks,
Justin
Re: New Flex SDK release
Posted by Christofer Dutz <ch...@c-ware.de>.
One thing I would really be dleighted about, would be, if we could get rid of the patched libraries used in the sdk.
However I don’t have any idea what sideeffects this would have.
Chris
Am 03.11.16, 08:53 schrieb "Justin Mclean" <ju...@classsoftware.com>:
Hi,
> Should we also take care of license issues cause we grab [2] and create a
> new file of it [3]?
[2] is MIT licensed so IMO it wouldn’t hurt it add a pointer of that MIT to our LICENSE file. That way all bases are covered.
There is an issue here (similar with certain other 3rd parties) in they don’t actualy have a MIT header or MIT license file we can copy (that I could find from a quick look).
To comply with the MIT license file you need to include the license text. There was a discussion on legal discuss about this recently the upshot being you should contact the 3rd party and ask them (nicely) to add the license test/header and/or add a header in our code for them.
Thanks,
Justin
Re: New Flex SDK release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Should we also take care of license issues cause we grab [2] and create a
> new file of it [3]?
[2] is MIT licensed so IMO it wouldn’t hurt it add a pointer of that MIT to our LICENSE file. That way all bases are covered.
There is an issue here (similar with certain other 3rd parties) in they don’t actualy have a MIT header or MIT license file we can copy (that I could find from a quick look).
To comply with the MIT license file you need to include the license text. There was a discussion on legal discuss about this recently the upshot being you should contact the 3rd party and ask them (nicely) to add the license test/header and/or add a header in our code for them.
Thanks,
Justin
Re: New Flex SDK release
Posted by OK <po...@olafkrueger.net>.
Justin Mclean wrote
> I assume we are only using the font files?
I think we use the .otf font [1] and variables.less [2]. But latter only as
template to create the AS3 constants file [3].
I understand that 4.7 font and code is compatible with Apache so we're
probably fine but just out of curiosity:
Should we also take care of license issues cause we grab [2] and create a
new file of it [3]?
Thanks,
Olaf
[1] https://github.com/FortAwesome/Font-Awesome/tree/master/fonts
[2]
https://github.com/FortAwesome/Font-Awesome/blob/master/less/variables.less
[3]
https://github.com/apache/flex-sdk/blob/develop/frameworks/projects/flatspark/src/flatspark/utils/AwesomeUtils.as
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/New-Flex-SDK-release-tp56153p56185.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: New Flex SDK release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> There will be still a community Version... Is this also incompatible with Apache?
The 4.7 community version is under a variety of license of which the code and font are under a compatible license [1]. Their documentation isn’t under a compatible license.
Hopefully this will be the same for 5.0. The 5.0 Pro version certainly isn’t compatible and it seems to be getting the larger update.
I assume we are only using the font files?
Thanks,
Justin
1. http://fontawesome.io/license/
Re: New Flex SDK release
Posted by OK <po...@olafkrueger.net>.
Justin Mclean wrote
> Hi,
>
>> I would update FontAwesome to the latest release so we have one more
>> minor
>> change…
>
> You want to take care of [1]. I also noticed this the other week [2] which
> has raised almost $500,000! Sadly the license isn’t likely to be
> compatible with Apache.
>
> Thanks,
> Justin
>
> 1. https://issues.apache.org/jira/browse/FLEX-35122
> 2. https://www.kickstarter.com/projects/232193852/font-awesome-5
Thanks for the reminder regarding the open jira.
My understanding is that the kickstarter Projekt targets 5.0 which will be
available in May 2017.
I would update to 4.7.
There will be still a community Version... Is this also incompatible with
Apache?
Anyway, unbelivable and awesome what great support the FontAwesome guys got
by its community. They got the money for the origin target in a few minutes!
Thanks,
Olaf
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/New-Flex-SDK-release-tp56153p56181.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: New Flex SDK release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> I would update FontAwesome to the latest release so we have one more minor
> change…
You want to take care of [1]. I also noticed this the other week [2] which has raised almost $500,000! Sadly the license isn’t likely to be compatible with Apache.
Thanks,
Justin
1. https://issues.apache.org/jira/browse/FLEX-35122
2. https://www.kickstarter.com/projects/232193852/font-awesome-5
Re: New Flex SDK release
Posted by OK <po...@olafkrueger.net>.
Justin Mclean wrote
> Hi,
> It’s been quite a while (10 months!) since we’ve made a new Flex SDK
> release, and there's a number of changes and fixes that have been made in
> develop.
> If no-one else want to be the release manager I’ll put my hand up for the
> role.
> Thanks,
> Justin
From my point of view it would be great to have a new release even if it'll
be shipped with just minor changes.
I would update FontAwesome to the latest release so we have one more minor
change...
Thanks for beeing the release manager!
Olaf
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/New-Flex-SDK-release-tp56153p56172.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: New Flex SDK release
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Are you thinking of this as a 4.16 or 4.15.1?
I was thinking 4.16 but it doesn't really matter.
Justin
Re: New Flex SDK release
Posted by Alex Harui <ah...@adobe.com>.
On 11/1/16, 4:02 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>Hi,
>
>It’s been quite a while (10 months!) since we’ve made a new Flex SDK
>release, and there's a number of changes and fixes that have been made in
>develop.
Are you thinking of this as a 4.16 or 4.15.1?
-Alex