You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2015/12/03 18:18:25 UTC
[DISCUSS] Adopting AS3Commons
Hi,
It has been my understanding that any existing code base that gets stored
in an Apache Flex repo must be "donated" via the Apache Software Grant
process, which essentially requires that the author of every line of code
in the code base needs to sign a legally-binding document.
I just found out that, while that is still the preferred method, if a code
base is already under the Apache License, it can also be "adopted" with
much less hassle.
Christophe Herreman, who also happens to be on our PMC, and one of the
major contributors to AS3Commons, is interested in having Apache Flex
adopt the AS3Commons code. I think this would be a good move for Apache
Flex because we use some of AS3Commons in the Installer already so it
would be good to have this code in a place we can control, especially if
we want to see how much of it will work in FlexJS.
So, first we should discuss whether we want to adopt AS3Commons and
actually vote on it, then we will try to contact by email every past
contributor to AS3Commons to see if they have any objections to having the
code base adopted by Apache Flex. The wording of the email is still being
finalized on the Apache legal-discuss mailing list, but basically, instead
of having to track down every past contributor and get their signature on
a Software Grant, we can now just gather email responses from as many of
those past contributors as we can.
After the email goes out, we'll wait 30 days or so for responses. If we
get an objection from a past contributor, then we'll look to see what
lines of code they contributed and determine what the impact would be of
not having those lines of code in our code base. It might be easily
replaceable. If we don't hear from a past contributor we will look at the
risk of what might happen if they do respond later with an objection.
So, we don't have to actually hear from every past contributor in order to
proceed with the adoption, but we might decide not to complete the
adoption if we get objections from or don't get a response from a major
contributor.
Technically and legally, we could "fork" this code without permission from
anybody since the code is under the Apache License, but socially, Apache
wants all code to come in voluntarily, which is why we want to make sure
there are no objections from past contributors as well as anyone on this
mailing list.
Thoughts?
-Alex
Re: [DISCUSS] Adopting AS3Commons
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Ah that's why the name is familiar. I used it in the Installer :-)
Thanks for the info!
Regards,
Om
On Thu, Dec 3, 2015 at 12:26 PM, Harbs <ha...@gmail.com> wrote:
> The feature I probably use most often in the zip functionality. It has the
> best zip library (formally FZip).
>
> But there’s tons of helper functions and containers as well.
>
> Take a look here: https://github.com/AS3Commons
>
> and here: https://code.google.com/p/as3-commons/source/browse/trunk
>
> On Dec 3, 2015, at 10:01 PM, OmPrakash Muppirala <bi...@gmail.com>
> wrote:
>
> > Do we have a list of features or an URL we can look at?
> >
> > Thanks,
> > Om
> >
> > On Thu, Dec 3, 2015 at 11:13 AM, Harbs <ha...@gmail.com> wrote:
> >
> >> +1.
> >>
> >> There’s lot’s useful stuff in AS3Commons.
> >>
> >> On Dec 3, 2015, at 7:18 PM, Alex Harui <ah...@adobe.com> wrote:
> >>
> >>> Hi,
> >>>
> >>> It has been my understanding that any existing code base that gets
> stored
> >>> in an Apache Flex repo must be "donated" via the Apache Software Grant
> >>> process, which essentially requires that the author of every line of
> code
> >>> in the code base needs to sign a legally-binding document.
> >>>
> >>> I just found out that, while that is still the preferred method, if a
> >> code
> >>> base is already under the Apache License, it can also be "adopted" with
> >>> much less hassle.
> >>>
> >>> Christophe Herreman, who also happens to be on our PMC, and one of the
> >>> major contributors to AS3Commons, is interested in having Apache Flex
> >>> adopt the AS3Commons code. I think this would be a good move for
> Apache
> >>> Flex because we use some of AS3Commons in the Installer already so it
> >>> would be good to have this code in a place we can control, especially
> if
> >>> we want to see how much of it will work in FlexJS.
> >>>
> >>> So, first we should discuss whether we want to adopt AS3Commons and
> >>> actually vote on it, then we will try to contact by email every past
> >>> contributor to AS3Commons to see if they have any objections to having
> >> the
> >>> code base adopted by Apache Flex. The wording of the email is still
> >> being
> >>> finalized on the Apache legal-discuss mailing list, but basically,
> >> instead
> >>> of having to track down every past contributor and get their signature
> on
> >>> a Software Grant, we can now just gather email responses from as many
> of
> >>> those past contributors as we can.
> >>>
> >>> After the email goes out, we'll wait 30 days or so for responses. If
> we
> >>> get an objection from a past contributor, then we'll look to see what
> >>> lines of code they contributed and determine what the impact would be
> of
> >>> not having those lines of code in our code base. It might be easily
> >>> replaceable. If we don't hear from a past contributor we will look at
> >> the
> >>> risk of what might happen if they do respond later with an objection.
> >>>
> >>> So, we don't have to actually hear from every past contributor in order
> >> to
> >>> proceed with the adoption, but we might decide not to complete the
> >>> adoption if we get objections from or don't get a response from a major
> >>> contributor.
> >>>
> >>> Technically and legally, we could "fork" this code without permission
> >> from
> >>> anybody since the code is under the Apache License, but socially,
> Apache
> >>> wants all code to come in voluntarily, which is why we want to make
> sure
> >>> there are no objections from past contributors as well as anyone on
> this
> >>> mailing list.
> >>>
> >>> Thoughts?
> >>> -Alex
> >>>
> >>
> >>
>
>
Re: [DISCUSS] Adopting AS3Commons
Posted by Michael Schmalle <te...@gmail.com>.
I use the async library in my feathers app right now. Some of the utilities
as well. The authors of all the librariues are top rate. :)
BTW, as3commons-asblocks, haha that was me that wrote all that! ;-)
Mike
On Thu, Dec 3, 2015 at 4:37 PM, Alex Harui <ah...@adobe.com> wrote:
> Nice find. Thanks, -Alex
>
> On 12/3/15, 1:09 PM, "Harbs" <ha...@gmail.com> wrote:
>
> >This seems to be confirmation:
> >https://twitter.com/as3commons/status/185620600272855040
> >
> >It appears to be donated by the author, so I think we’re okay there.
> >
> >On Dec 3, 2015, at 11:00 PM, Harbs <ha...@gmail.com> wrote:
> >
> >> I have heard that FZip moved to be included in AS3Commons, but I have
> >>no idea if that’s true.
> >>
> >> I assume Christophe should know the answer to that.
> >>
> >> On Dec 3, 2015, at 10:51 PM, Alex Harui <ah...@adobe.com> wrote:
> >>
> >>>
> >>>
> >>> On 12/3/15, 12:26 PM, "Harbs" <ha...@gmail.com> wrote:
> >>>
> >>>> The feature I probably use most often in the zip functionality. It has
> >>>> the best zip library (formally FZip).
> >>>
> >>> Do you know for a fact it uses Fzip? That could pose a problem since
> >>>Fzip
> >>> isn't Apache-licensed. It wouldn't block adoption of the rest of the
> >>>code
> >>> though.
> >>>
> >>> -Alex
> >>>
> >>
> >
>
>
Re: [DISCUSS] Adopting AS3Commons
Posted by Alex Harui <ah...@adobe.com>.
Nice find. Thanks, -Alex
On 12/3/15, 1:09 PM, "Harbs" <ha...@gmail.com> wrote:
>This seems to be confirmation:
>https://twitter.com/as3commons/status/185620600272855040
>
>It appears to be donated by the author, so I think we’re okay there.
>
>On Dec 3, 2015, at 11:00 PM, Harbs <ha...@gmail.com> wrote:
>
>> I have heard that FZip moved to be included in AS3Commons, but I have
>>no idea if that’s true.
>>
>> I assume Christophe should know the answer to that.
>>
>> On Dec 3, 2015, at 10:51 PM, Alex Harui <ah...@adobe.com> wrote:
>>
>>>
>>>
>>> On 12/3/15, 12:26 PM, "Harbs" <ha...@gmail.com> wrote:
>>>
>>>> The feature I probably use most often in the zip functionality. It has
>>>> the best zip library (formally FZip).
>>>
>>> Do you know for a fact it uses Fzip? That could pose a problem since
>>>Fzip
>>> isn't Apache-licensed. It wouldn't block adoption of the rest of the
>>>code
>>> though.
>>>
>>> -Alex
>>>
>>
>
Re: [DISCUSS] Adopting AS3Commons
Posted by Harbs <ha...@gmail.com>.
This seems to be confirmation:
https://twitter.com/as3commons/status/185620600272855040
It appears to be donated by the author, so I think we’re okay there.
On Dec 3, 2015, at 11:00 PM, Harbs <ha...@gmail.com> wrote:
> I have heard that FZip moved to be included in AS3Commons, but I have no idea if that’s true.
>
> I assume Christophe should know the answer to that.
>
> On Dec 3, 2015, at 10:51 PM, Alex Harui <ah...@adobe.com> wrote:
>
>>
>>
>> On 12/3/15, 12:26 PM, "Harbs" <ha...@gmail.com> wrote:
>>
>>> The feature I probably use most often in the zip functionality. It has
>>> the best zip library (formally FZip).
>>
>> Do you know for a fact it uses Fzip? That could pose a problem since Fzip
>> isn't Apache-licensed. It wouldn't block adoption of the rest of the code
>> though.
>>
>> -Alex
>>
>
Re: [DISCUSS] Adopting AS3Commons
Posted by Harbs <ha...@gmail.com>.
I have heard that FZip moved to be included in AS3Commons, but I have no idea if that’s true.
I assume Christophe should know the answer to that.
On Dec 3, 2015, at 10:51 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
> On 12/3/15, 12:26 PM, "Harbs" <ha...@gmail.com> wrote:
>
>> The feature I probably use most often in the zip functionality. It has
>> the best zip library (formally FZip).
>
> Do you know for a fact it uses Fzip? That could pose a problem since Fzip
> isn't Apache-licensed. It wouldn't block adoption of the rest of the code
> though.
>
> -Alex
>
Re: [DISCUSS] Adopting AS3Commons
Posted by Alex Harui <ah...@adobe.com>.
On 12/3/15, 12:26 PM, "Harbs" <ha...@gmail.com> wrote:
>The feature I probably use most often in the zip functionality. It has
>the best zip library (formally FZip).
Do you know for a fact it uses Fzip? That could pose a problem since Fzip
isn't Apache-licensed. It wouldn't block adoption of the rest of the code
though.
-Alex
RE: [DISCUSS] Adopting AS3Commons
Posted by Jim Norris <ji...@e-work.com>.
I use the AS3 Commons eventbus.
-----Original Message-----
From: Harbs [mailto:harbs.lists@gmail.com]
Sent: Thursday, December 03, 2015 3:26 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Adopting AS3Commons
The feature I probably use most often in the zip functionality. It has the
best zip library (formally FZip).
But there's tons of helper functions and containers as well.
Take a look here: https://github.com/AS3Commons
and here: https://code.google.com/p/as3-commons/source/browse/trunk
On Dec 3, 2015, at 10:01 PM, OmPrakash Muppirala <bi...@gmail.com>
wrote:
> Do we have a list of features or an URL we can look at?
>
> Thanks,
> Om
>
> On Thu, Dec 3, 2015 at 11:13 AM, Harbs <ha...@gmail.com> wrote:
>
>> +1.
>>
>> There's lot's useful stuff in AS3Commons.
>>
>> On Dec 3, 2015, at 7:18 PM, Alex Harui <ah...@adobe.com> wrote:
>>
>>> Hi,
>>>
>>> It has been my understanding that any existing code base that gets
>>> stored in an Apache Flex repo must be "donated" via the Apache
>>> Software Grant process, which essentially requires that the author
>>> of every line of code in the code base needs to sign a legally-binding
document.
>>>
>>> I just found out that, while that is still the preferred method, if
>>> a
>> code
>>> base is already under the Apache License, it can also be "adopted"
>>> with much less hassle.
>>>
>>> Christophe Herreman, who also happens to be on our PMC, and one of
>>> the major contributors to AS3Commons, is interested in having Apache
>>> Flex adopt the AS3Commons code. I think this would be a good move
>>> for Apache Flex because we use some of AS3Commons in the Installer
>>> already so it would be good to have this code in a place we can
>>> control, especially if we want to see how much of it will work in
FlexJS.
>>>
>>> So, first we should discuss whether we want to adopt AS3Commons and
>>> actually vote on it, then we will try to contact by email every past
>>> contributor to AS3Commons to see if they have any objections to
>>> having
>> the
>>> code base adopted by Apache Flex. The wording of the email is still
>> being
>>> finalized on the Apache legal-discuss mailing list, but basically,
>> instead
>>> of having to track down every past contributor and get their
>>> signature on a Software Grant, we can now just gather email
>>> responses from as many of those past contributors as we can.
>>>
>>> After the email goes out, we'll wait 30 days or so for responses.
>>> If we get an objection from a past contributor, then we'll look to
>>> see what lines of code they contributed and determine what the
>>> impact would be of not having those lines of code in our code base.
>>> It might be easily replaceable. If we don't hear from a past
>>> contributor we will look at
>> the
>>> risk of what might happen if they do respond later with an objection.
>>>
>>> So, we don't have to actually hear from every past contributor in
>>> order
>> to
>>> proceed with the adoption, but we might decide not to complete the
>>> adoption if we get objections from or don't get a response from a
>>> major contributor.
>>>
>>> Technically and legally, we could "fork" this code without
>>> permission
>> from
>>> anybody since the code is under the Apache License, but socially,
>>> Apache wants all code to come in voluntarily, which is why we want
>>> to make sure there are no objections from past contributors as well
>>> as anyone on this mailing list.
>>>
>>> Thoughts?
>>> -Alex
>>>
>>
>>
Re: [DISCUSS] Adopting AS3Commons
Posted by Harbs <ha...@gmail.com>.
The feature I probably use most often in the zip functionality. It has the best zip library (formally FZip).
But there’s tons of helper functions and containers as well.
Take a look here: https://github.com/AS3Commons
and here: https://code.google.com/p/as3-commons/source/browse/trunk
On Dec 3, 2015, at 10:01 PM, OmPrakash Muppirala <bi...@gmail.com> wrote:
> Do we have a list of features or an URL we can look at?
>
> Thanks,
> Om
>
> On Thu, Dec 3, 2015 at 11:13 AM, Harbs <ha...@gmail.com> wrote:
>
>> +1.
>>
>> There’s lot’s useful stuff in AS3Commons.
>>
>> On Dec 3, 2015, at 7:18 PM, Alex Harui <ah...@adobe.com> wrote:
>>
>>> Hi,
>>>
>>> It has been my understanding that any existing code base that gets stored
>>> in an Apache Flex repo must be "donated" via the Apache Software Grant
>>> process, which essentially requires that the author of every line of code
>>> in the code base needs to sign a legally-binding document.
>>>
>>> I just found out that, while that is still the preferred method, if a
>> code
>>> base is already under the Apache License, it can also be "adopted" with
>>> much less hassle.
>>>
>>> Christophe Herreman, who also happens to be on our PMC, and one of the
>>> major contributors to AS3Commons, is interested in having Apache Flex
>>> adopt the AS3Commons code. I think this would be a good move for Apache
>>> Flex because we use some of AS3Commons in the Installer already so it
>>> would be good to have this code in a place we can control, especially if
>>> we want to see how much of it will work in FlexJS.
>>>
>>> So, first we should discuss whether we want to adopt AS3Commons and
>>> actually vote on it, then we will try to contact by email every past
>>> contributor to AS3Commons to see if they have any objections to having
>> the
>>> code base adopted by Apache Flex. The wording of the email is still
>> being
>>> finalized on the Apache legal-discuss mailing list, but basically,
>> instead
>>> of having to track down every past contributor and get their signature on
>>> a Software Grant, we can now just gather email responses from as many of
>>> those past contributors as we can.
>>>
>>> After the email goes out, we'll wait 30 days or so for responses. If we
>>> get an objection from a past contributor, then we'll look to see what
>>> lines of code they contributed and determine what the impact would be of
>>> not having those lines of code in our code base. It might be easily
>>> replaceable. If we don't hear from a past contributor we will look at
>> the
>>> risk of what might happen if they do respond later with an objection.
>>>
>>> So, we don't have to actually hear from every past contributor in order
>> to
>>> proceed with the adoption, but we might decide not to complete the
>>> adoption if we get objections from or don't get a response from a major
>>> contributor.
>>>
>>> Technically and legally, we could "fork" this code without permission
>> from
>>> anybody since the code is under the Apache License, but socially, Apache
>>> wants all code to come in voluntarily, which is why we want to make sure
>>> there are no objections from past contributors as well as anyone on this
>>> mailing list.
>>>
>>> Thoughts?
>>> -Alex
>>>
>>
>>
Re: [DISCUSS] Adopting AS3Commons
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Do we have a list of features or an URL we can look at?
Thanks,
Om
On Thu, Dec 3, 2015 at 11:13 AM, Harbs <ha...@gmail.com> wrote:
> +1.
>
> There’s lot’s useful stuff in AS3Commons.
>
> On Dec 3, 2015, at 7:18 PM, Alex Harui <ah...@adobe.com> wrote:
>
> > Hi,
> >
> > It has been my understanding that any existing code base that gets stored
> > in an Apache Flex repo must be "donated" via the Apache Software Grant
> > process, which essentially requires that the author of every line of code
> > in the code base needs to sign a legally-binding document.
> >
> > I just found out that, while that is still the preferred method, if a
> code
> > base is already under the Apache License, it can also be "adopted" with
> > much less hassle.
> >
> > Christophe Herreman, who also happens to be on our PMC, and one of the
> > major contributors to AS3Commons, is interested in having Apache Flex
> > adopt the AS3Commons code. I think this would be a good move for Apache
> > Flex because we use some of AS3Commons in the Installer already so it
> > would be good to have this code in a place we can control, especially if
> > we want to see how much of it will work in FlexJS.
> >
> > So, first we should discuss whether we want to adopt AS3Commons and
> > actually vote on it, then we will try to contact by email every past
> > contributor to AS3Commons to see if they have any objections to having
> the
> > code base adopted by Apache Flex. The wording of the email is still
> being
> > finalized on the Apache legal-discuss mailing list, but basically,
> instead
> > of having to track down every past contributor and get their signature on
> > a Software Grant, we can now just gather email responses from as many of
> > those past contributors as we can.
> >
> > After the email goes out, we'll wait 30 days or so for responses. If we
> > get an objection from a past contributor, then we'll look to see what
> > lines of code they contributed and determine what the impact would be of
> > not having those lines of code in our code base. It might be easily
> > replaceable. If we don't hear from a past contributor we will look at
> the
> > risk of what might happen if they do respond later with an objection.
> >
> > So, we don't have to actually hear from every past contributor in order
> to
> > proceed with the adoption, but we might decide not to complete the
> > adoption if we get objections from or don't get a response from a major
> > contributor.
> >
> > Technically and legally, we could "fork" this code without permission
> from
> > anybody since the code is under the Apache License, but socially, Apache
> > wants all code to come in voluntarily, which is why we want to make sure
> > there are no objections from past contributors as well as anyone on this
> > mailing list.
> >
> > Thoughts?
> > -Alex
> >
>
>
Re: [DISCUSS] Adopting AS3Commons
Posted by Harbs <ha...@gmail.com>.
+1.
There’s lot’s useful stuff in AS3Commons.
On Dec 3, 2015, at 7:18 PM, Alex Harui <ah...@adobe.com> wrote:
> Hi,
>
> It has been my understanding that any existing code base that gets stored
> in an Apache Flex repo must be "donated" via the Apache Software Grant
> process, which essentially requires that the author of every line of code
> in the code base needs to sign a legally-binding document.
>
> I just found out that, while that is still the preferred method, if a code
> base is already under the Apache License, it can also be "adopted" with
> much less hassle.
>
> Christophe Herreman, who also happens to be on our PMC, and one of the
> major contributors to AS3Commons, is interested in having Apache Flex
> adopt the AS3Commons code. I think this would be a good move for Apache
> Flex because we use some of AS3Commons in the Installer already so it
> would be good to have this code in a place we can control, especially if
> we want to see how much of it will work in FlexJS.
>
> So, first we should discuss whether we want to adopt AS3Commons and
> actually vote on it, then we will try to contact by email every past
> contributor to AS3Commons to see if they have any objections to having the
> code base adopted by Apache Flex. The wording of the email is still being
> finalized on the Apache legal-discuss mailing list, but basically, instead
> of having to track down every past contributor and get their signature on
> a Software Grant, we can now just gather email responses from as many of
> those past contributors as we can.
>
> After the email goes out, we'll wait 30 days or so for responses. If we
> get an objection from a past contributor, then we'll look to see what
> lines of code they contributed and determine what the impact would be of
> not having those lines of code in our code base. It might be easily
> replaceable. If we don't hear from a past contributor we will look at the
> risk of what might happen if they do respond later with an objection.
>
> So, we don't have to actually hear from every past contributor in order to
> proceed with the adoption, but we might decide not to complete the
> adoption if we get objections from or don't get a response from a major
> contributor.
>
> Technically and legally, we could "fork" this code without permission from
> anybody since the code is under the Apache License, but socially, Apache
> wants all code to come in voluntarily, which is why we want to make sure
> there are no objections from past contributors as well as anyone on this
> mailing list.
>
> Thoughts?
> -Alex
>
Re: [DISCUSS] Adopting AS3Commons
Posted by Alex Harui <ah...@adobe.com>.
On 12/6/15, 2:43 PM, "Justin Mclean" <ju...@me.com> wrote:
>Hi,
>
>> Christophe Herreman, who also happens to be on our PMC, and one of the
>> major contributors to AS3Commons, is interested in having Apache Flex
>> adopt the AS3Commons code. I think this would be a good move for Apache
>> Flex because we use some of AS3Commons in the Installer already so it
>> would be good to have this code in a place we can control, especially if
>> we want to see how much of it will work in FlexJS.
>
>I assume an IP review would still be required, while the risk is low I
>think it’s still a concern. How do we work out if someone has for
>instanced copied some GPL or other license code in there? Looking at the
>code bases there about 50 different copyright owners in the code (some
>variations of the same) including Adobe. The Adobe stuff may be MPL
>licensed? There's also some MIT and possibly other licensed code in there.
Yes, we should run some sort of an IP review. I believe we won't be
strict about the SGA line-item.
IMO, it is good to know what there might be issues in the dependencies.
It is interesting that initial code drops in a new podling can hit the
repo with IP issues and get clean up after the fact, but after that all
other code drops need to be reviewed first. It would be easier to grab
every repo and clean it later, but since most of them are on GitHub, I
suppose we could just IP review each repo as we take it in. I don't think
we need to do it all at once.
>
>> So, first we should discuss whether we want to adopt AS3Commons
>
>Do we have anyone who is willing to be active maintainers of this code?
>(Or at least more active than it is currently). Is any existing committer
>willing to put up a friendly notice redirecting users and devs to it's
>new home? What committers are willing to clean up the code base and
>integrate it into the SDK including looking into updating license and
>notice?
Yeah, well I'd prefer that we don't integrate it into the SDK but we need
to understand the entire dependencies picture before deciding it can live
on its own. I'd like to know more about what the Maven packages are for
this code base. If it is one Maven package per repo, we might just start
with ones we are most interested in and release each repo on its own
schedule instead of one huge release. I'm mostly interested in the zip
code which is not on GitHub as we use it in the Installer.
-Alex
Re: [DISCUSS] Adopting AS3Commons
Posted by Justin Mclean <ju...@me.com>.
Hi,
> Christophe Herreman, who also happens to be on our PMC, and one of the
> major contributors to AS3Commons, is interested in having Apache Flex
> adopt the AS3Commons code. I think this would be a good move for Apache
> Flex because we use some of AS3Commons in the Installer already so it
> would be good to have this code in a place we can control, especially if
> we want to see how much of it will work in FlexJS.
I assume an IP review would still be required, while the risk is low I think it’s still a concern. How do we work out if someone has for instanced copied some GPL or other license code in there? Looking at the code bases there about 50 different copyright owners in the code (some variations of the same) including Adobe. The Adobe stuff may be MPL licensed? There's also some MIT and possibly other licensed code in there.
> So, first we should discuss whether we want to adopt AS3Commons
Do we have anyone who is willing to be active maintainers of this code? (Or at least more active than it is currently). Is any existing committer willing to put up a friendly notice redirecting users and devs to it's new home? What committers are willing to clean up the code base and integrate it into the SDK including looking into updating license and notice?
Thanks,
Justin
RE: iOS video help
Posted by Jason Taylor <ja...@dedoose.com>.
I can see the video player, and the controls, i breifly see the duration set, and then goto 0, osmf act's like it's buffering forever. It seems that http dynamic streaming just dosen't work on iOS and that we must use HLS streaming. Kinda a pita to rebox all the moof frags on the fly to accommodate iOS.
-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of OmPrakash Muppirala
Sent: Wednesday, December 09, 2015 11:25 AM
To: dev@flex.apache.org
Subject: Re: iOS video help
There might be other errors. But if you don't even see the video player, that indicates that the Application is hiding the video layer.
Thanks,
Om
On Wed, Dec 9, 2015 at 11:24 AM, Jason Taylor <ja...@dedoose.com> wrote:
> it dosen't even try to play, the player controls don't progress. I
> plugged in OSMF with logging turned on and I don't see anything that
> looks like an error.
>
>
> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
> OmPrakash Muppirala
> Sent: Tuesday, December 08, 2015 6:44 PM
> To: dev@flex.apache.org
> Subject: Re: iOS video help
>
> I don't know much about this, but have you tried setting the
> application's backgroundAlpha to 0?
>
> Thanks,
> Om
> On Dec 8, 2015 3:42 PM, "Jason Taylor" <ja...@dedoose.com> wrote:
>
> > no matter what framework / air version I use, renderMode = direct,
> > OSMFSettings.enableStageVideo = false, I cannot get the following
> > application to play video on any iOS device or simulator:
> >
> > <?xml version="1.0" encoding="utf-8"?> <s:Application
> > xmlns:fx="http://ns.adobe.com/mxml/2009"
> > xmlns:s="library://ns.adobe.com/flex/spark"
> > creationComplete="OnCreationComplete(event)">
> > <s:VGroup width="100%" height="100%">
> > <s:VideoPlayer width="100%" height="100%" source="
> > http://dev.dedoose.com/HttpVideo/ce81d033-145d-432d-99b8-cb48105ea5a
> > 8/ ResourceVideoData/11c2ccf3-765c-4381-bfd8-264a8fa5bdfa.f4m
> > "/>
> > </s:VGroup>
> > <fx:Script><![CDATA[
> > import org.osmf.utils.OSMFSettings;
> >
> > private function OnCreationComplete(event:FlexEvent):void {
> > OSMFSettings.enableStageVideo = false;
> > }
> > import mx.events.FlexEvent;
> > ]]></fx:Script>
> > </s:Application>
> >
> >
> >
>
Re: iOS video help
Posted by OmPrakash Muppirala <bi...@gmail.com>.
There might be other errors. But if you don't even see the video player,
that indicates that the Application is hiding the video layer.
Thanks,
Om
On Wed, Dec 9, 2015 at 11:24 AM, Jason Taylor <ja...@dedoose.com> wrote:
> it dosen't even try to play, the player controls don't progress. I
> plugged in OSMF with logging turned on and I don't see anything that looks
> like an error.
>
>
> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of OmPrakash
> Muppirala
> Sent: Tuesday, December 08, 2015 6:44 PM
> To: dev@flex.apache.org
> Subject: Re: iOS video help
>
> I don't know much about this, but have you tried setting the
> application's backgroundAlpha to 0?
>
> Thanks,
> Om
> On Dec 8, 2015 3:42 PM, "Jason Taylor" <ja...@dedoose.com> wrote:
>
> > no matter what framework / air version I use, renderMode = direct,
> > OSMFSettings.enableStageVideo = false, I cannot get the following
> > application to play video on any iOS device or simulator:
> >
> > <?xml version="1.0" encoding="utf-8"?> <s:Application
> > xmlns:fx="http://ns.adobe.com/mxml/2009"
> > xmlns:s="library://ns.adobe.com/flex/spark"
> > creationComplete="OnCreationComplete(event)">
> > <s:VGroup width="100%" height="100%">
> > <s:VideoPlayer width="100%" height="100%" source="
> > http://dev.dedoose.com/HttpVideo/ce81d033-145d-432d-99b8-cb48105ea5a8/
> > ResourceVideoData/11c2ccf3-765c-4381-bfd8-264a8fa5bdfa.f4m
> > "/>
> > </s:VGroup>
> > <fx:Script><![CDATA[
> > import org.osmf.utils.OSMFSettings;
> >
> > private function OnCreationComplete(event:FlexEvent):void {
> > OSMFSettings.enableStageVideo = false;
> > }
> > import mx.events.FlexEvent;
> > ]]></fx:Script>
> > </s:Application>
> >
> >
> >
>
RE: iOS video help
Posted by Jason Taylor <ja...@dedoose.com>.
it dosen't even try to play, the player controls don't progress. I plugged in OSMF with logging turned on and I don't see anything that looks like an error.
-----Original Message-----
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of OmPrakash Muppirala
Sent: Tuesday, December 08, 2015 6:44 PM
To: dev@flex.apache.org
Subject: Re: iOS video help
I don't know much about this, but have you tried setting the application's backgroundAlpha to 0?
Thanks,
Om
On Dec 8, 2015 3:42 PM, "Jason Taylor" <ja...@dedoose.com> wrote:
> no matter what framework / air version I use, renderMode = direct,
> OSMFSettings.enableStageVideo = false, I cannot get the following
> application to play video on any iOS device or simulator:
>
> <?xml version="1.0" encoding="utf-8"?> <s:Application
> xmlns:fx="http://ns.adobe.com/mxml/2009"
> xmlns:s="library://ns.adobe.com/flex/spark"
> creationComplete="OnCreationComplete(event)">
> <s:VGroup width="100%" height="100%">
> <s:VideoPlayer width="100%" height="100%" source="
> http://dev.dedoose.com/HttpVideo/ce81d033-145d-432d-99b8-cb48105ea5a8/
> ResourceVideoData/11c2ccf3-765c-4381-bfd8-264a8fa5bdfa.f4m
> "/>
> </s:VGroup>
> <fx:Script><![CDATA[
> import org.osmf.utils.OSMFSettings;
>
> private function OnCreationComplete(event:FlexEvent):void {
> OSMFSettings.enableStageVideo = false;
> }
> import mx.events.FlexEvent;
> ]]></fx:Script>
> </s:Application>
>
>
>
Re: iOS video help
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I don't know much about this, but have you tried setting the application's
backgroundAlpha to 0?
Thanks,
Om
On Dec 8, 2015 3:42 PM, "Jason Taylor" <ja...@dedoose.com> wrote:
> no matter what framework / air version I use, renderMode = direct,
> OSMFSettings.enableStageVideo = false, I cannot get the following
> application to play video on any iOS device or simulator:
>
> <?xml version="1.0" encoding="utf-8"?>
> <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
> xmlns:s="library://ns.adobe.com/flex/spark"
> creationComplete="OnCreationComplete(event)">
> <s:VGroup width="100%" height="100%">
> <s:VideoPlayer width="100%" height="100%" source="
> http://dev.dedoose.com/HttpVideo/ce81d033-145d-432d-99b8-cb48105ea5a8/ResourceVideoData/11c2ccf3-765c-4381-bfd8-264a8fa5bdfa.f4m
> "/>
> </s:VGroup>
> <fx:Script><![CDATA[
> import org.osmf.utils.OSMFSettings;
>
> private function OnCreationComplete(event:FlexEvent):void {
> OSMFSettings.enableStageVideo = false;
> }
> import mx.events.FlexEvent;
> ]]></fx:Script>
> </s:Application>
>
>
>
iOS video help
Posted by Jason Taylor <ja...@dedoose.com>.
no matter what framework / air version I use, renderMode = direct, OSMFSettings.enableStageVideo = false, I cannot get the following application to play video on any iOS device or simulator:
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" creationComplete="OnCreationComplete(event)">
<s:VGroup width="100%" height="100%">
<s:VideoPlayer width="100%" height="100%" source="http://dev.dedoose.com/HttpVideo/ce81d033-145d-432d-99b8-cb48105ea5a8/ResourceVideoData/11c2ccf3-765c-4381-bfd8-264a8fa5bdfa.f4m"/>
</s:VGroup>
<fx:Script><![CDATA[
import org.osmf.utils.OSMFSettings;
private function OnCreationComplete(event:FlexEvent):void {
OSMFSettings.enableStageVideo = false;
}
import mx.events.FlexEvent;
]]></fx:Script>
</s:Application>
AW: [DISCUSS] Adopting AS3Commons
Posted by Christofer Dutz <ch...@c-ware.de>.
+1 (I'm not officially voting in this thread, but expressing my oppinion with this ;-) )
And I did already checkout all of the projects some time ago and adopt them to Apache Flex 4.11.1 and Flexmojos 7.1.0-SNAPSHOT
So if we wanted to fire out a release, this shouldn't be too hard :)
Chris
-----Ursprüngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]
Gesendet: Donnerstag, 3. Dezember 2015 18:18
An: dev@flex.apache.org
Betreff: [DISCUSS] Adopting AS3Commons
Hi,
It has been my understanding that any existing code base that gets stored in an Apache Flex repo must be "donated" via the Apache Software Grant process, which essentially requires that the author of every line of code in the code base needs to sign a legally-binding document.
I just found out that, while that is still the preferred method, if a code base is already under the Apache License, it can also be "adopted" with much less hassle.
Christophe Herreman, who also happens to be on our PMC, and one of the major contributors to AS3Commons, is interested in having Apache Flex adopt the AS3Commons code. I think this would be a good move for Apache Flex because we use some of AS3Commons in the Installer already so it would be good to have this code in a place we can control, especially if we want to see how much of it will work in FlexJS.
So, first we should discuss whether we want to adopt AS3Commons and actually vote on it, then we will try to contact by email every past contributor to AS3Commons to see if they have any objections to having the code base adopted by Apache Flex. The wording of the email is still being finalized on the Apache legal-discuss mailing list, but basically, instead of having to track down every past contributor and get their signature on a Software Grant, we can now just gather email responses from as many of those past contributors as we can.
After the email goes out, we'll wait 30 days or so for responses. If we get an objection from a past contributor, then we'll look to see what lines of code they contributed and determine what the impact would be of not having those lines of code in our code base. It might be easily replaceable. If we don't hear from a past contributor we will look at the risk of what might happen if they do respond later with an objection.
So, we don't have to actually hear from every past contributor in order to proceed with the adoption, but we might decide not to complete the adoption if we get objections from or don't get a response from a major contributor.
Technically and legally, we could "fork" this code without permission from anybody since the code is under the Apache License, but socially, Apache wants all code to come in voluntarily, which is why we want to make sure there are no objections from past contributors as well as anyone on this mailing list.
Thoughts?
-Alex
Re: AW: [DISCUSS] Adopting AS3Commons
Posted by lizhi <sl...@qq.com>.
i thinks it is just a lib.it in the github is good.why put it to flex?
the flex should clear.
if the flex can not use the lib from github,should fixed,it is a bug.
why put some lib in flex?
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Adopting-AS3Commons-tp50473p50546.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.