Hi,
Just replace the copyright text in th test with machine translated text from
our README, as far as I can se eI've not broken any tests, but sorry in
advanced if I have done so. I think that's all know IP issues dealt with and we
can now close this JIRA. [1]
Thanks,
Justin
1. https://issue
Hi,
Also this file:
automation_tests/src/UnitTest/Tests/FloatTest.as
Contains text from the NY Times and need some content replaced.
Justin
Hi,
OK I gone though and fix up all of the public domain stuff, correct headers
where needed and added some text to LICENSE. The rabbit hole was a little
deeper than I first thought and there more files "infected" than a casual
glance gave.
IMO replacing all of the pubic domain content would
On 1/30/15, 1:38 AM, "Bertrand Delacretaz" wrote:
>
>LICENSE sounds good to me if you want that.
>
>NOTICE must stay minimal, i.e. contain only required notices, so for
>public domain stuff I'd go for LICENCE.
And this is why it is so complicated. See [1] (apologies that s.a.o is
down so I can
On Fri, Jan 30, 2015 at 12:46 AM, Alex Harui wrote:
> ...IMO, this stuff is always complicated because the instructions are not
> clear and it takes several emails to agree...
If you keep track of those changes in jira, next time you can just
point to that and say "do like we did in FLEX-NNN" wit
Hi,
On Thu, Jan 29, 2015 at 11:33 PM, Justin Mclean
wrote:
> Bertrand wrote:
>> You can just add a comment before that public domain text, that it's public
>> domain.
>>
> I's prefer to see in the actual files (so you know what is the public
> domain content) as above
> but I also think it's
On 1/29/15, 3:27 PM, "Harbs" wrote:
>I think it’s likely that we’re going to break some of the tests if we
>swap out the texts for something else.
>
>If someone wants to try, feel free, but it seems like a lot of work.
I thought we’d found that the provenance of some of the other texts were
in
I think it’s likely that we’re going to break some of the tests if we swap out
the texts for something else.
If someone wants to try, feel free, but it seems like a lot of work.
I really don’t understand why this is so complicated. Do we really need
explicit attribution for some text that’s onl
Hi,
> If we put the attribution in the main NOTICE, then if we don’t package the
> tests in the release artifact we have to remember to change NOTICE or use
> a different NOTICE. I would imagine other projects who composite NOTICE
> files are exposed in the same way.
The NOTICE/LICENSE that's us
On 1/29/15, 2:33 PM, "Justin Mclean" wrote:
>Hi,
>
>> You can just add a comment before that public domain text, that it's
>>public
>> domain.
>>
>> That doesn't put any more constraints on users than the Apache License
>>so
>> you're fine.
>
>I's prefer to see in the actual files (so you know
Hi,
> You can just add a comment before that public domain text, that it's public
> domain.
>
> That doesn't put any more constraints on users than the Apache License so
> you're fine.
I's prefer to see in the actual files (so you know what is the public domain
content) as above but I also thin
On Thursday, January 29, 2015, Alex Harui wrote:
> ... There is a code file with a portion of the public domain text in it
that
> would probably force a mention of this content in NOTICE
You can just add a comment before that public domain text, that it's public
domain.
That doesn't put any
On 1/29/15, 1:02 AM, "Bertrand Delacretaz" wrote:
>On Wed, Jan 28, 2015 at 7:32 PM, Alex Harui wrote:
>> ...It just seems that once you start mixing content
>> that isn’t public domain (in this case the TLF markup) if you have to
>> determine the % of IP in order to determine which header to u
On Wed, Jan 28, 2015 at 7:32 PM, Alex Harui wrote:
> ...It just seems that once you start mixing content
> that isn’t public domain (in this case the TLF markup) if you have to
> determine the % of IP in order to determine which header to use it adds
> extra overhead.
Yeah, that can complicate th
On 1/28/15, 9:45 AM, "Bertrand Delacretaz" wrote:
>Hi,
>
>On Wednesday, January 28, 2015, Alex Harui wrote:
>
>> My current thinking is that we keep the Apache Headers in the
>> source file [1] and give attribution in a NOTICE.test file...
>
>> Justin’s position is that he wants to remove the
Hi,
On Wednesday, January 28, 2015, Alex Harui wrote:
> My current thinking is that we keep the Apache Headers in the
> source file [1] and give attribution in a NOTICE.test file...
> Justin’s position is that he wants to remove the Apache header and replace
> it with a header that calls out t
e allowed to use
the text, they'd check the NOTICE file and realize the text is public domain.
Chris
> From: aha...@adobe.com
> To: dev@flex.apache.org
> Subject: Re: JAR in TLF svn/git mirror
> Date: Wed, 28 Jan 2015 07:58:48 +
>
>
>
> On 1/27/15, 4:58 PM
On 1/27/15, 4:58 PM, "Dave Fisher" wrote:
>If it is any Category A including Public Domain at
>http://www.apache.org/legal/resolved.html you may put it in an Apache
>repository.
Hi Dave, I don’t think the current debate is about whether Public Domain
content can be in the repository, it is how
Hi,
> If it is any Category A including Public Domain at
> http://www.apache.org/legal/resolved.html you may put it in an Apache
> repository.
If you'e referring to the Arial font it's not public domain / Category A [1]
and this file was removed, then added back in, and then removed again, so
If it is any Category A including Public Domain at
http://www.apache.org/legal/resolved.html you may put it in an Apache
repository.
But - I mean dude!
http://www.metrolyrics.com/go-ask-alice-lyrics-jefferson-airplane.html
On Jan 23, 2015, at 4:53 PM, Justin Mclean wrote:
> Hi,
>
> Also swfs
On 1/25/15, 10:51 AM, "piotrz" wrote:
>Alex,
>
>There are plenty of tests which are using Arial font in TLF, but removing
>these ARIAL_FONT.swf wasn't have any wrong impact on our current working
>tests. I don't know what will happen once I started to fix the rest one -
>We
>will see. :)
It di
No problem :) I will ping you once we will require this. :)
Thank you,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/JAR-in-TLF-svn-git-mirror-tp44554p44643.html
Sent from the Apache Flex Development
Okay. I already searched all those files, and there was no reference to
tanach.xml.
I think we’re okay.
If we do need extensive Hebrew texts for testing, I’ll be happy to put
something together when we do.
On Jan 25, 2015, at 9:24 PM, piotrz wrote:
> Look into the module automation_tests and
Look into the module automation_tests and folders:
automation_tests\src\UnitTest\Tests\
automation_tests\src\UnitTest\PerformanceTests\
All classes from these folders which are not in AllTestsSuite class need to
be fixed/rewritten for Flex Unit 4.
Piotr
-
Apache Flex PMC
piotrzarzyck...@g
Where are these tests that need fixing? I’ll be happy to check whether the
tanach.xml text is needed.
On Jan 25, 2015, at 9:14 PM, piotrz wrote:
> I know that this file is not used for now, but there are still more than 50
> test classes in TLF which need to be fixed. Maybe some of them will re
I know that this file is not used for now, but there are still more than 50
test classes in TLF which need to be fixed. Maybe some of them will require
these file, so I would be really carefully removing anything. :)
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message i
I searched the repo for a reference to the file and did not find one.
Are there more tests that are not in the repo?
On Jan 25, 2015, at 8:51 PM, piotrz wrote:
> Harbs,
>
> I'm not sure whether tanach.xml won't be used somewhere in the rest of the
> tests. If it was a license problem I'm ok, b
Erik,
As for the build. We need these files for TLF Flex unit:
flexunit.swc
flexunit-cilistener.swc
flexunit-uilistener.swc
They are part of Apache Flex Unit and for running through ant unit tests we
need also
flexUnitTasks.jar
But maybe I'm wrong and we can replace these jar file to something
Alex,
There are plenty of tests which are using Arial font in TLF, but removing
these ARIAL_FONT.swf wasn't have any wrong impact on our current working
tests. I don't know what will happen once I started to fix the rest one - We
will see. :)
Harbs,
I'm not sure whether tanach.xml won't be used
The only thing that concerns me from Justin’s list is the Arial font and
possibly the Adobe logo.
I’m not sure what the Arial font is used for. Piotr will have to comment on
that.
As far as I can tell, the Adobe logo is not used, so removing that should be
fine.
On Jan 25, 2015, at 12:03 AM,
I’ve reverted all the way back to before I tried fixing issues in Justin’s
list. Once everything passes, I’ll try removing a few things.
On 1/24/15, 2:02 PM, "Harbs" wrote:
>However, as far as I can tell the image was not used in any of the tests,
>so it’s probably safe to remove it if you want
However, as far as I can tell the image was not used in any of the tests, so
it’s probably safe to remove it if you want.
On Jan 25, 2015, at 12:00 AM, Harbs wrote:
> Yes. But it was obviously taken by an Adobe employee and then donated to
> Apache, so there’s no IP issues there.
>
> On Jan 2
Yes. But it was obviously taken by an Adobe employee and then donated to
Apache, so there’s no IP issues there.
On Jan 24, 2015, at 11:57 PM, Justin Mclean wrote:
> Hi,
>
>>> For instance we probably don't have permission to redistribute:
>>> https://github.com/apache/flex-tlf/blob/develop/tes
Hi,
>> For instance we probably don't have permission to redistribute:
>> https://github.com/apache/flex-tlf/blob/develop/test/testFiles/assets/image1.jpg
>>
I would be surprised if the above image was public domain.
Justin
Yes. The tests do not do image comparisons. It’s only position, structure and
metrics.
The following images appear to be used in the tests:
carrot.png
FremontBridge.jpg
fakepng.png
gremlin.jpg
leaves.jpg
RedCircles.swf
smiley.gif
smiling.png
smiling.swf.png
surprised.png
They do not look to me
On 1/24/15, 1:22 PM, "Harbs" wrote:
>
>On Jan 24, 2015, at 2:53 AM, Justin Mclean
>wrote:
>>
>> In fact several things under here:
>> https://github.com/apache/flex-tlf/tree/develop/test/testFiles/assets
>>
>> For instance we probably don't have permission to redistribute:
>>
>>https://gith
On Jan 24, 2015, at 2:53 AM, Justin Mclean wrote:
>
> In fact several things under here:
> https://github.com/apache/flex-tlf/tree/develop/test/testFiles/assets
>
> For instance we probably don't have permission to redistribute:
> https://github.com/apache/flex-tlf/blob/develop/test/testFiles/a
If you explain what needs to be build, I can get Jenkins to build it
prior to launching the tests, no problem.
EdB
On Sat, Jan 24, 2015 at 9:57 PM, piotrz wrote:
> Hi Guys,
>
> Files in /ant and /libs folders are needed for Unit tests in TLF. All these
> files should be removed also from our g
Hi Guys,
Files in /ant and /libs folders are needed for Unit tests in TLF. All these
files should be removed also from our git repository ? If yes - How Jenkins
will build everything and launch tests ? Is there any specific path where we
can point once we remove files from repository ?
Piotr
-
On 1/23/15, 11:42 PM, "Justin Mclean" wrote:
>Hi,
>
>> AIUI, the state of the repos doesn’t affect the release. BlazeDS
>>passed IP Clearance.
>
>It may of "passed" but it needs a review badly.
OK, have fun. I personally would appreciate it if you save up all your
findings for one email when
Hi,
> AIUI, the state of the repos doesn’t affect the release. BlazeDS passed IP
> Clearance.
It may of "passed" but it needs a review badly. A quick rat run on it shows it
need some work. There's even a "maven-petesucks.png" file, although I think as
that's in the in directory so that's clea
AIUI, the state of the repos doesn’t affect the release. BlazeDS passed
IP Clearance. TLF entered during incubation so different rules apply.
Rat got run on the files in the source package. I didn’t see anything in
the report.
On 1/23/15, 10:55 PM, "Justin Mclean" wrote:
>Hi,
>
>> I took care
Hi,
> I took care of the stuff Justin found. Thanks for finding it. Justin if
> you find more, you can probably just delete it yourself.
That was from a five minute look.We really need a full IP check on both Blaze
DS and TLF repos as it's seems this important step may of been skipped. I would
I took care of the stuff Justin found. Thanks for finding it. Justin if
you find more, you can probably just delete it yourself.
-Alex
On 1/23/15, 6:39 PM, "Justin Mclean" wrote:
>Hi,
>
>> You, for example?
>
>Well normally the people who put the files there should fix them and the
>PMC as a w
Hi,
> You, for example?
Well normally the people who put the files there should fix them and the PMC as
a whole is responsible for legal matter and the RM is legally responsible for
any release that make.
Justin
You, for example?
Commit, then review.
EdB
On Saturday, January 24, 2015, Justin Mclean wrote:
> Hi,
>
> We shouldn't be putting jars in version control:
> https://github.com/apache/flex-tlf/tree/develop/ant
>
> Someone mind removing that?
>
> Thanks,
> Justin
>
--
Ix Multimedia Software
Hi,
Also swfs here:
https://github.com/apache/flex-tlf/tree/develop/libs
And while we're at it. This is got good IP wise:
https://github.com/apache/flex-tlf/blob/develop/sdk/samples/flex/Logo.jpg
And this:
https://github.com/apache/flex-tlf/blob/develop/test/testFiles/assets/ARIAL_FONT.swf
In f
47 matches
Mail list logo
