Re: [DISCUSS} Fork FlexJS from Apache Flex

[Lee29]

Now I can open that link,
Thanks very much for your help!



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Alex Harui]

I just fixed the SWF version.  Working on the JS version now.

-Alex

On 9/26/17, 6:55 AM, "yishayw"  wrote:

>The address is ok but tags.json isn't found...
>
>
>
>
>
>--
>Sent from: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2F=02%7C01%7C%7C3d7199659a8e42626
>c5508d504e63dad%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364203092854
>80637=w8lzMqte0%2Bz1fUNI9ZRx0qCnxZSHljVekabpRnuKwmg%3D=0

Re: [DISCUSS} Fork FlexJS from Apache Flex

[yishayw]

The address is ok but tags.json isn't found...





--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Lee29]

Thanks for your reply!
But there is a problem, I can not open the two links in:
http://people.apache.org/~pent/asdoc-flexjs/index.html
Are these docs moved to another new place, so it can not be opend now?
Or is it just my network problem?
If the address has been updated, please tell me where it is now.
Thanks very much.



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS} Fork FlexJS from Apache Flex

[yishayw]

Yes and No. See this [1].

[1]
http://apache-flex-users.246.n4.nabble.com/How-To-Start-Converting-A-Browser-Project-to-FlexJS-td15946.html#a15950



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Lee29]

Hi,
I just want to look for some introduction of FlexJs.
Is there any document to show the construction of FlexJs? Like which package
contains which class, label or method,
'cause I am a new, and want to know more about this.
If there are some documents, please tell me, thanks very much.




--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Jose Barragan]

Sorry

Thanks Erik

> On 4 Sep 2017, at 09:49, Erik de Bruin  wrote:
> 
> Remember to vote in the [VOTE] thread.
> 
> EdB
> 
> 
> 
> 2017-09-04 9:29 GMT+02:00 Jose Barragan  >:
> 
>> I think is the best option.
>> Hope I could be part of this.
>> 
>> +1
>> __
>> *Jose Barragan*
>> *Senior Software Engineer*
>> Codeoscopic
>> +34 912 94 80 80 <+34%20912%2094%2080%2080>
>> http://www.codeoscopic.com 
>> 
>> Este mensaje se dirige exclusivamente a su destinatario y puede contener
>> información privilegiada o confidencial. Si ha recibido este mensaje por
>> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>> proceda a su destrucción.
>> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>> comunicamos que sus datos forman parte de un fichero cuyo responsable es
>> CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la
>> prestación del servicio o información solicitados, teniendo usted derecho
>> de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose
>> a nuestras oficinas Avda. Manoteras, nº 30, B109, 28050 de Madrid (Madrid)
>> con la documentación necesaria.
>> 
>> On 1 Sep 2017, at 01:56, Carlos Rovira > >
>> wrote:
>> 
>> I think this is a very good idea, thanks for proposing a fork
>> 
>> I'l be voting +1 to this
>> 
>> C.
>> 
>> 2017-08-31 23:43 GMT+02:00 Piotr Zarzycki > >:
>> 
>> Let's wait for the VOTE thread and focus on Fork.
>> 
>> Agree with Michael that talking about the name should be in a separate
>> thread.
>> 
>> Piotr
>> 
>> 2017-08-31 23:39 GMT+02:00 Michael Schmalle > >:
>> 
>> I think the name thing should be in a separate thread.
>> 
>> Mike
>> 
>> On Thu, Aug 31, 2017 at 5:35 PM, Dave Fisher > >
>> wrote:
>> 
>> That's a conflict. We would want a nonconflicting name that will not
>> confuse our users.
>> 
>> Sent from my iPhone
>> 
>> On Aug 31, 2017, at 2:25 PM, Harbs > > wrote:
>> 
>> Well, Phoenix is already a thing:
>> http://phoenixframework.org/  
>> >
>> 
>> Not sure about trademark issues…
>> 
>> On Aug 31, 2017, at 11:55 PM, OmPrakash Muppirala <
>> 
>> bigosma...@gmail.com >
>> 
>> wrote:
>> 
>> 
>> I want to throw in the name FenixJS for the fork.
>> Its a play on the words Flex + Phoenix.  You know what that means
>> 
>> :-)
>> 
>> 
>> Thanks,
>> Om
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> --
>> 
>> Piotr Zarzycki
>> 
>> mobile: +48 880 859 557 <+48%20880%20859%20557>
>> skype: zarzycki10
>> 
>> LinkedIn: http://www.linkedin.com/piotrzarzycki 
>> 
>> > >
>> 
>> 
>> 
>> 
>> --
>> 
>> >
>> 
>> Carlos Rovira
>> 
>> Director General
>> 
>> M: +34 607 22 60 05 <+34%20607%2022%2060%2005>
>> 
>> http://www.codeoscopic.com
>> 
>> http://www.avant2.es
>> 
>> 
>> Conocenos en 1 minuto! 
>> 
>> 
>> Este mensaje se dirige exclusivamente a su destinatario y puede contener
>> información privilegiada o confidencial. Si ha recibido este mensaje por
>> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>> proceda a su destrucción.
>> 
>> De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
>> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>> servicio o información solicitados, teniendo usted derecho de acceso,
>> rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
>> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>> necesaria.
>> 
>> 
>> 
> 
> 
> --
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl 


signature.asc
Description: Message signed with OpenPGP

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Erik de Bruin]

Remember to vote in the [VOTE] thread.

EdB



2017-09-04 9:29 GMT+02:00 Jose Barragan :

> I think is the best option.
> Hope I could be part of this.
>
> +1
> __
> *Jose Barragan*
> *Senior Software Engineer*
> Codeoscopic
> +34 912 94 80 80 <+34%20912%2094%2080%2080>
> http://www.codeoscopic.com
>
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
> comunicamos que sus datos forman parte de un fichero cuyo responsable es
> CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la
> prestación del servicio o información solicitados, teniendo usted derecho
> de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose
> a nuestras oficinas Avda. Manoteras, nº 30, B109, 28050 de Madrid (Madrid)
> con la documentación necesaria.
>
> On 1 Sep 2017, at 01:56, Carlos Rovira 
> wrote:
>
> I think this is a very good idea, thanks for proposing a fork
>
> I'l be voting +1 to this
>
> C.
>
> 2017-08-31 23:43 GMT+02:00 Piotr Zarzycki :
>
> Let's wait for the VOTE thread and focus on Fork.
>
> Agree with Michael that talking about the name should be in a separate
> thread.
>
> Piotr
>
> 2017-08-31 23:39 GMT+02:00 Michael Schmalle :
>
> I think the name thing should be in a separate thread.
>
> Mike
>
> On Thu, Aug 31, 2017 at 5:35 PM, Dave Fisher 
> wrote:
>
> That's a conflict. We would want a nonconflicting name that will not
> confuse our users.
>
> Sent from my iPhone
>
> On Aug 31, 2017, at 2:25 PM, Harbs  wrote:
>
> Well, Phoenix is already a thing:
> http://phoenixframework.org/ 
>
> Not sure about trademark issues…
>
> On Aug 31, 2017, at 11:55 PM, OmPrakash Muppirala <
>
> bigosma...@gmail.com>
>
> wrote:
>
>
> I want to throw in the name FenixJS for the fork.
> Its a play on the words Flex + Phoenix.  You know what that means
>
> :-)
>
>
> Thanks,
> Om
>
>
>
>
>
>
>
>
> --
>
> Piotr Zarzycki
>
> mobile: +48 880 859 557 <+48%20880%20859%20557>
> skype: zarzycki10
>
> LinkedIn: http://www.linkedin.com/piotrzarzycki
> 
>
>
>
>
> --
>
> 
>
> Carlos Rovira
>
> Director General
>
> M: +34 607 22 60 05 <+34%20607%2022%2060%2005>
>
> http://www.codeoscopic.com
>
> http://www.avant2.es
>
>
> Conocenos en 1 minuto! 
>
>
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
>
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> servicio o información solicitados, teniendo usted derecho de acceso,
> rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> necesaria.
>
>
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Jose Barragan]

I think is the best option.
Hope I could be part of this.

+1
__
Jose Barragan
Senior Software Engineer
Codeoscopic
+34 912 94 80 80
http://www.codeoscopic.com 

Este mensaje se dirige exclusivamente a su destinatario y puede contener 
información privilegiada o confidencial. Si ha recibido este mensaje por error, 
le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a 
su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos que 
sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC S.A. La 
finalidad de dicho tratamiento es facilitar la prestación del servicio o 
información solicitados, teniendo usted derecho de acceso, rectificación, 
cancelación y oposición de sus datos dirigiéndose a nuestras oficinas Avda. 
Manoteras, nº 30, B109, 28050 de Madrid (Madrid) con la documentación necesaria.

> On 1 Sep 2017, at 01:56, Carlos Rovira  wrote:
> 
> I think this is a very good idea, thanks for proposing a fork
> 
> I'l be voting +1 to this
> 
> C.
> 
> 2017-08-31 23:43 GMT+02:00 Piotr Zarzycki :
> 
>> Let's wait for the VOTE thread and focus on Fork.
>> 
>> Agree with Michael that talking about the name should be in a separate
>> thread.
>> 
>> Piotr
>> 
>> 2017-08-31 23:39 GMT+02:00 Michael Schmalle :
>> 
>>> I think the name thing should be in a separate thread.
>>> 
>>> Mike
>>> 
>>> On Thu, Aug 31, 2017 at 5:35 PM, Dave Fisher 
>>> wrote:
>>> 
 That's a conflict. We would want a nonconflicting name that will not
 confuse our users.
 
 Sent from my iPhone
 
> On Aug 31, 2017, at 2:25 PM, Harbs  wrote:
> 
> Well, Phoenix is already a thing:
> http://phoenixframework.org/ 
> 
> Not sure about trademark issues…
> 
>> On Aug 31, 2017, at 11:55 PM, OmPrakash Muppirala <
>>> bigosma...@gmail.com>
 wrote:
>> 
>> I want to throw in the name FenixJS for the fork.
>> Its a play on the words Flex + Phoenix.  You know what that means
>> :-)
>> 
>> Thanks,
>> Om
> 
 
 
>>> 
>> 
>> 
>> 
>> --
>> 
>> Piotr Zarzycki
>> 
>> mobile: +48 880 859 557
>> skype: zarzycki10
>> 
>> LinkedIn: http://www.linkedin.com/piotrzarzycki
>> 
>> 
> 
> 
> 
> --
> 
> 
> 
> Carlos Rovira
> 
> Director General
> 
> M: +34 607 22 60 05
> 
> http://www.codeoscopic.com
> 
> http://www.avant2.es
> 
> 
> Conocenos en 1 minuto! 
> 
> 
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
> 
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
> que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> servicio o información solicitados, teniendo usted derecho de acceso,
> rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> necesaria.



signature.asc
Description: Message signed with OpenPGP

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Carlos Rovira]

I think this is a very good idea, thanks for proposing a fork

I'l be voting +1 to this

C.

2017-08-31 23:43 GMT+02:00 Piotr Zarzycki :

> Let's wait for the VOTE thread and focus on Fork.
>
> Agree with Michael that talking about the name should be in a separate
> thread.
>
> Piotr
>
> 2017-08-31 23:39 GMT+02:00 Michael Schmalle :
>
> > I think the name thing should be in a separate thread.
> >
> > Mike
> >
> > On Thu, Aug 31, 2017 at 5:35 PM, Dave Fisher 
> > wrote:
> >
> > > That's a conflict. We would want a nonconflicting name that will not
> > > confuse our users.
> > >
> > > Sent from my iPhone
> > >
> > > > On Aug 31, 2017, at 2:25 PM, Harbs  wrote:
> > > >
> > > > Well, Phoenix is already a thing:
> > > > http://phoenixframework.org/ 
> > > >
> > > > Not sure about trademark issues…
> > > >
> > > >> On Aug 31, 2017, at 11:55 PM, OmPrakash Muppirala <
> > bigosma...@gmail.com>
> > > wrote:
> > > >>
> > > >> I want to throw in the name FenixJS for the fork.
> > > >> Its a play on the words Flex + Phoenix.  You know what that means
> :-)
> > > >>
> > > >> Thanks,
> > > >> Om
> > > >
> > >
> > >
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> mobile: +48 880 859 557
> skype: zarzycki10
>
> LinkedIn: http://www.linkedin.com/piotrzarzycki
> 
>



-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com

http://www.avant2.es


Conocenos en 1 minuto! 


Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Piotr Zarzycki]

Let's wait for the VOTE thread and focus on Fork.

Agree with Michael that talking about the name should be in a separate
thread.

Piotr

2017-08-31 23:39 GMT+02:00 Michael Schmalle :

> I think the name thing should be in a separate thread.
>
> Mike
>
> On Thu, Aug 31, 2017 at 5:35 PM, Dave Fisher 
> wrote:
>
> > That's a conflict. We would want a nonconflicting name that will not
> > confuse our users.
> >
> > Sent from my iPhone
> >
> > > On Aug 31, 2017, at 2:25 PM, Harbs  wrote:
> > >
> > > Well, Phoenix is already a thing:
> > > http://phoenixframework.org/ 
> > >
> > > Not sure about trademark issues…
> > >
> > >> On Aug 31, 2017, at 11:55 PM, OmPrakash Muppirala <
> bigosma...@gmail.com>
> > wrote:
> > >>
> > >> I want to throw in the name FenixJS for the fork.
> > >> Its a play on the words Flex + Phoenix.  You know what that means :-)
> > >>
> > >> Thanks,
> > >> Om
> > >
> >
> >
>



-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

LinkedIn: http://www.linkedin.com/piotrzarzycki

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Michael Schmalle]

I think the name thing should be in a separate thread.

Mike

On Thu, Aug 31, 2017 at 5:35 PM, Dave Fisher  wrote:

> That's a conflict. We would want a nonconflicting name that will not
> confuse our users.
>
> Sent from my iPhone
>
> > On Aug 31, 2017, at 2:25 PM, Harbs  wrote:
> >
> > Well, Phoenix is already a thing:
> > http://phoenixframework.org/ 
> >
> > Not sure about trademark issues…
> >
> >> On Aug 31, 2017, at 11:55 PM, OmPrakash Muppirala 
> wrote:
> >>
> >> I want to throw in the name FenixJS for the fork.
> >> Its a play on the words Flex + Phoenix.  You know what that means :-)
> >>
> >> Thanks,
> >> Om
> >
>
>

Re: [DISCUSS} Fork FlexJS from Apache Flex

[OmPrakash Muppirala]

Hehe looks like this is a thing already: https://phoenix.apache.org/
Oh well, never mind :-(

On Thu, Aug 31, 2017 at 2:35 PM, Dave Fisher  wrote:

> That's a conflict. We would want a nonconflicting name that will not
> confuse our users.
>
> Sent from my iPhone
>
> > On Aug 31, 2017, at 2:25 PM, Harbs  wrote:
> >
> > Well, Phoenix is already a thing:
> > http://phoenixframework.org/ 
> >
> > Not sure about trademark issues…
> >
> >> On Aug 31, 2017, at 11:55 PM, OmPrakash Muppirala 
> wrote:
> >>
> >> I want to throw in the name FenixJS for the fork.
> >> Its a play on the words Flex + Phoenix.  You know what that means :-)
> >>
> >> Thanks,
> >> Om
> >
>
>

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Dave Fisher]

That's a conflict. We would want a nonconflicting name that will not confuse 
our users.

Sent from my iPhone

> On Aug 31, 2017, at 2:25 PM, Harbs  wrote:
> 
> Well, Phoenix is already a thing:
> http://phoenixframework.org/ 
> 
> Not sure about trademark issues…
> 
>> On Aug 31, 2017, at 11:55 PM, OmPrakash Muppirala  
>> wrote:
>> 
>> I want to throw in the name FenixJS for the fork.
>> Its a play on the words Flex + Phoenix.  You know what that means :-)
>> 
>> Thanks,
>> Om
> 

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Harbs]

Well, Phoenix is already a thing:
http://phoenixframework.org/ 

Not sure about trademark issues…

> On Aug 31, 2017, at 11:55 PM, OmPrakash Muppirala  
> wrote:
> 
> I want to throw in the name FenixJS for the fork.
> Its a play on the words Flex + Phoenix.  You know what that means :-)
> 
> Thanks,
> Om

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Erik de Bruin]

OK, if we're throwing names out there, here is one:

BendJS

EdB



On Thu, Aug 31, 2017 at 10:55 PM, OmPrakash Muppirala 
wrote:

> I want to throw in the name FenixJS for the fork.
> Its a play on the words Flex + Phoenix.  You know what that means :-)
>
> Thanks,
> Om
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [DISCUSS} Fork FlexJS from Apache Flex

[chrsmrtn]

I am for this fork. I hope to maybe be added to the project after things get
settled.

Cheers and good luck!

Chris



--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Michael Schmalle]

I forgot to mention that I am all for this fork. I have a couple projects
that I want to use this with and then I can work on the compiler for my
projects.

Interestingly Web Assembly could be a target, I am naive as what it is
detail wise, not enough research but compiling to something native would be
nice. Maybe it could future proof a compiler emitter.

Mike

On Thu, Aug 31, 2017 at 5:02 PM, Michael Schmalle  wrote:

> Eh, I like the idea but you would then pretty much just use the rise from
> ashes word, because when I first read it I had no idea what it was, my
> dyslexia thought it was like Feline or Kleenex. (don't ask why I see an L)
>
> :)
>
> Mike
>
>
> On Thu, Aug 31, 2017 at 4:55 PM, OmPrakash Muppirala  > wrote:
>
>> I want to throw in the name FenixJS for the fork.
>> Its a play on the words Flex + Phoenix.  You know what that means :-)
>>
>> Thanks,
>> Om
>>
>
>

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Michael Schmalle]

Eh, I like the idea but you would then pretty much just use the rise from
ashes word, because when I first read it I had no idea what it was, my
dyslexia thought it was like Feline or Kleenex. (don't ask why I see an L)

:)

Mike

On Thu, Aug 31, 2017 at 4:55 PM, OmPrakash Muppirala 
wrote:

> I want to throw in the name FenixJS for the fork.
> Its a play on the words Flex + Phoenix.  You know what that means :-)
>
> Thanks,
> Om
>

Re: [DISCUSS} Fork FlexJS from Apache Flex

[OmPrakash Muppirala]

I want to throw in the name FenixJS for the fork.
Its a play on the words Flex + Phoenix.  You know what that means :-)

Thanks,
Om

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Tom Chiverton]

Exactly. This is not "all the Flex people walking away to do FlexJS".

There will continue to be overlap (or not) as people scratch particular 
itches.


Tom


On 29/08/17 19:24, Kessler CTR Mark J wrote:

There will still be quite a few PMC members on the Flex SDK side.  Some will be 
on both SDK and JS sides.

RE: Re: [DISCUSS} Fork FlexJS from Apache Flex

[Kessler CTR Mark J]

It is good to point this out.  There are other targets that can be compiled 
into other than flash.  Such as Air and it's captive runtimes for desktop and 
mobile.


My understanding is Adobe has a vested interesting alternatives to the Flash 
Player as targets.  They are not getting rid of ActionScript or Air, so it's 
mostly going to receive support for all things AS related.


There will still be quite a few PMC members on the Flex SDK side.  Some will be 
on both SDK and JS sides.


-Original Message-
From: Olaf Krueger [mailto:okrue...@apache.org]
Sent: Tuesday, August 29, 2017 7:14 AM
To: dev@flex.apache.org
Subject: Re: [DISCUSS} Fork FlexJS from Apache Flex

I've already replied via nabble a few hours ago but it seems that it is not 
synced with the list for whatever reason... so sorry for annoying you:

Hi Alex,
thanks for this summary, I think this is the right way to go!
+1

But for me, it sounds a little bit, that Apache Flex is labeled as discontinued.
We should take care to not scare off or unsettle Apache Flex users.
Even if FlashPlayer is dead, Flex with AIR is still an awesome platform!
Maybe the usage of AIR could save some Flex apps a for while or give users some 
more time to migrate to FlexJS.


> Most FlexJS PMC members are planning to remain on the Apache Flex PMC
I think it would be good to also list the Apache Flex PMC members


>I will be stepping down as Apache Flex chair
Probably I've overlooked something but who will be the chair of Apache Flex?


>It isn't clear how much longer Adobe will pay Peter and I to work on Flex
and/or FlexJS.

I would like to use the opportunity to mention that my company is only willing 
to invest time in FlexJS if Adobe will continue its support.
So I hope that there will be a commitment by Adobe. The fork would be a good 
opportunity for Adobe
to express oneself.

Thanks,
Olaf

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Piotr Zarzycki]

Hi,

+1

Well prepared abstract. It is definitely the time for making split. I hope
that board will understand us and this will go smoothly.
Looking forward to the voting.

Thank you!
Piotr


2017-08-29 16:29 GMT+02:00 Peter Ent :

> Hi,
>
> As an employee of Adobe and a contributor to Apache FlexJS, I think this
> new project fork is a good idea. Companies with investment in Flex
> applications that rely on the Flash Player to deliver their applications
> to their users will have to look for alternatives in the next couple of
> years.
>
> Apache FlexJS provides this opportunity. With continued support from the
> community, we can chart a path to make the transition easier in a number
> of ways. For example, wiki articles that provide guidance for migration or
> new FlexJS framework kits that help bridge the gap between Apache Flex and
> FlexJS. And many other ideas will come from this.
>
> I feel the opportunity to turn a negative into a positive is a huge one
> and doing this now is the best time.
>
> Regards,
> Peter Ent
> Adobe Systems/Apache Flex(JS) Project
>
>
> >
>
>


-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

LinkedIn: http://www.linkedin.com/piotrzarzycki

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Peter Ent]

Hi,

As an employee of Adobe and a contributor to Apache FlexJS, I think this
new project fork is a good idea. Companies with investment in Flex
applications that rely on the Flash Player to deliver their applications
to their users will have to look for alternatives in the next couple of
years. 

Apache FlexJS provides this opportunity. With continued support from the
community, we can chart a path to make the transition easier in a number
of ways. For example, wiki articles that provide guidance for migration or
new FlexJS framework kits that help bridge the gap between Apache Flex and
FlexJS. And many other ideas will come from this.

I feel the opportunity to turn a negative into a positive is a huge one
and doing this now is the best time.

Regards,
Peter Ent
Adobe Systems/Apache Flex(JS) Project


>

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Olaf Krueger]

Hi Alex,
thanks for this summary, I think this is the right way to go!
+1

But for me, it sounds a little bit, that Apache Flex is labeled as
discontinued.
We should take care to not scare off or unsettle Apache Flex users.
Even if FlashPlayer is dead, Flex with AIR is still an awesome platform!
Maybe the usage of AIR could save some Flex apps a while or give users some
more time to migrate to FlexJS.


> Most FlexJS PMC members are planning to remain on the Apache Flex PMC
I think it would be good to also list the Apache Flex PMC members


>I will be stepping down as Apache Flex chair 
Probably I've overlooked something but who will be the chair of Apache Flex?


>It isn't clear how much longer Adobe will pay Peter and I to work on Flex 
and/or FlexJS.

I would like to use the opportunity to mention that my company is only
willing to invest time in FlexJS if Adobe will continue its support.
So I hope that there will be a commitment by Adobe. The fork would be a good
opportunity for Adobe 
to express oneself.

Thanks,
Olaf






--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Fork-FlexJS-from-Apache-Flex-tp64007p64012.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Olaf Krueger]

I've already replied via nabble a few hours ago but it seems that it is not 
synced with the list for whatever reason... so sorry for annoying you:

Hi Alex, 
thanks for this summary, I think this is the right way to go! 
+1 

But for me, it sounds a little bit, that Apache Flex is labeled as 
discontinued. 
We should take care to not scare off or unsettle Apache Flex users. 
Even if FlashPlayer is dead, Flex with AIR is still an awesome platform! 
Maybe the usage of AIR could save some Flex apps a for while or give users some 
more time to migrate to FlexJS. 


> Most FlexJS PMC members are planning to remain on the Apache Flex PMC 
I think it would be good to also list the Apache Flex PMC members 


>I will be stepping down as Apache Flex chair 
Probably I've overlooked something but who will be the chair of Apache Flex? 


>It isn't clear how much longer Adobe will pay Peter and I to work on Flex 
and/or FlexJS. 

I would like to use the opportunity to mention that my company is only willing 
to invest time in FlexJS if Adobe will continue its support. 
So I hope that there will be a commitment by Adobe. The fork would be a good 
opportunity for Adobe 
to express oneself. 

Thanks, 
Olaf 

RE: [DISCUSS} Fork FlexJS from Apache Flex

[Kessler CTR Mark J]

+1 to Split to FlexJS


-Mark K

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Tom Chiverton]

I think this is a good idea. The projects and people who work on them 
are diverging, and have been for a while.


Some people clearly wish to contribute to both - but I think for most 
people it's one or the other. I don't want to get into a big list of who 
has done what; that's my impression and reason why I would vote for this.


Tom


On 29/08/17 05:37, Alex Harui wrote:

Hi Folks,

I (and many others on the PMC) believe there are sufficient reasons to ask
the Apache Board of Directors to create a new Apache Top-Level Project
called Apache FlexJS separate from Apache Flex.

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Justin Mclean]

Hi,

As a long standing Flex PMC and committer (5 1/2 years) with a large number of 
contributions in code [1] (and also elsewhere) I’d like to be added as a PMC 
and committer to this proposal.

I’ve also made a number of contributions directly to FlexJS [2], reviewed 
releases, spoken at conferences on FlexJS and more receintly created the 
website for the FlexJS summit held at the last ApacheCon [3] and have been 
working on a FlexJS application.

Thanks,
Justin

1. https://github.com/apache/flex-sdk/graphs/contributors
2. https://github.com/apache/flex-asjs/graphs/contributors
3. https://us.apacheflexjs.org

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Olaf Krüger]

> "thanks" for the "degradation"

Please don't start the new project with trouble!
I hope that there are no doubts that Chris is an important part of the PMC.

Thanks,
Olaf

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Christofer Dutz]

"thanks" for the "degradation"

-1

Chris

On 2017-08-29 06:37, Alex Harui  wrote: 
> Hi Folks,
> 
> I (and many others on the PMC) believe there are sufficient reasons to ask
> the Apache Board of Directors to create a new Apache Top-Level Project
> called Apache FlexJS separate from Apache Flex.  The Apache Board has
> approved splitting other projects in the past and the proposal below is
> based on a past proposal to split another Apache project.
> 
> The main reason is that there seems to be a set of folks who are only
> working on Apache Flex and another set who are only working on FlexJS.
> Only a few have made commits to both products in the past year and the
> contribution to one product or the other was minimal.  Second, forking
> should save time for folks only interested in Flex or FlexJS as you don't
> have to filter out emails, web site and wiki information and bugs reports
> that apply to the product you are not interested in.  Third, forking would
> give a cleaner opportunity to try out Apache's GitBox implementation that
> allows us to leverage more GitHub functionality and make GitHub more
> primary in our development pipeline.  Fourth, many folks on the PMC have
> not been active in a long time, and a new project with a smaller PMC and
> committers list might make it more clear who is involved with FlexJS.
> 
> - proposal ---
> 
> Apache FlexJS for Apache Top-Level Project
> 
> Abstract
> 
> Apache FlexJS is a new implementation of the principles of Apache Flex but
> designed for JavaScript runtimes instead of Adobe Flash/AIR runtimes.
> Apache FlexJS was created and released as part of the Apache Flex project
> and the UI framework is a full rewrite and does not leverage the code
> bases donated by Adobe.  Only the FlexJS compiler source was donated by
> Adobe.
> 
> Over time, the set of Apache Flex committers who are working on Apache
> Flex releases have become distinct from those working on FlexJS.  Add to
> that the Adobe announcement of the end-of-life for Flash in the browser,
> it makes sense to separate FlexJS from Flex so that followers of one side
> or the other don't have to filter out emails, bugs, web pages, etc, that
> they don't need.
> 
> The proposal is to form an Apache FlexJS top-level project instead of
> creating a new Incubator Podling.   That is because all of the folks being
> proposed to the new Apache FlexJS PMC below have been on the Apache Flex
> PMC for months, if not years, and understand how to participate
> productively in an Apache project.  Plus, Apache FlexJS has already been
> released by the top-level Apache Flex project.
> 
> Overview of FlexJS
> 
> Apache FlexJS is designed to improve developer productivity in creating
> applications for wherever Javascript runs, including browsers as well as
> Apache Cordova applications, Node, etc.  FlexJS already has an ecosystem
> of folks creating IDEs for FlexJS, and some folks are at various points in
> the process of migrating existing Flex applications to FlexJS.
> 
> Current Status
> 
> Meritocracy
> 
> Within Apache Flex, the FlexJS development has been conducted as a
> meritocracy.  No existing FlexJS developers came with the compiler code
> base donated by Adobe nor were they on the initial committers list for
> Apache Flex other than Alex Harui.  Everyone else has earned their way in
> by contributing and earning merit.
> 
> Community
> 
> Many FlexJS users are trying to migrate an existing Apache Flex app off of
> Adobe Flash.  As their migration progresses they will become less and less
> interested in Apache Flex releases and activity.  However, the Apache Flex
> JIRA project contains some  30,000 Flex issues migrated from Adobe's bug
> base, and the team page for Flex makes it hard to determine which
> committers are active on FlexJS, and it is frequently hard to determine if
> a user's question is about regular Flex or FlexJS.   We are seeing an
> increase in user interest with the Flash end-of-life announcement and
> having separate mailing lists, web pages, and JIRA projects will help save
> everyone time and energy.
> 
> Alignment
> 
> Apache FlexJS is already being released by Apache.
> 
> Known Risks
> 
> Code Extraction
> 
> The flex-asjs, flex-tours, flex-typedefs, and flex-falcon Git repos would
> be migrated to GitBox.  Other Apache Flex repos would be treated as
> external dependencies.  This includes flex-utilities and the Apache Flex
> Installer.
> 
> Orphaned Projects
> 
> Most FlexJS PMC members are planning to remain on the Apache Flex PMC to
> help out just-in-case, but are already mostly inactive on the Flex code
> bases. However, there are at least 3 Apache Flex PMC members who have not
> contributed at all to FlexJS and participate in regular Flex releases, so
> the expectation is that Apache Flex will remain a viable project for some
> time to come.
> 
> Inexperience with Open Source
> 
> All of the initial team has been contributing 

Re: [DISCUSS} Fork FlexJS from Apache Flex

[OmPrakash Muppirala]

+1 for the fork.

Thanks,
Om

On Aug 28, 2017 10:05 PM, "Harbs"  wrote:

> Very well  said.
>
> Let’s do this! :-)
>
> Harbs
>
> > On Aug 29, 2017, at 7:37 AM, Alex Harui 
> wrote:
> >
> > Hi Folks,
> >
> > I (and many others on the PMC) believe there are sufficient reasons to
> ask
> > the Apache Board of Directors to create a new Apache Top-Level Project
> > called Apache FlexJS separate from Apache Flex.  The Apache Board has
> > approved splitting other projects in the past and the proposal below is
> > based on a past proposal to split another Apache project.
> >
> > The main reason is that there seems to be a set of folks who are only
> > working on Apache Flex and another set who are only working on FlexJS.
> > Only a few have made commits to both products in the past year and the
> > contribution to one product or the other was minimal.  Second, forking
> > should save time for folks only interested in Flex or FlexJS as you don't
> > have to filter out emails, web site and wiki information and bugs reports
> > that apply to the product you are not interested in.  Third, forking
> would
> > give a cleaner opportunity to try out Apache's GitBox implementation that
> > allows us to leverage more GitHub functionality and make GitHub more
> > primary in our development pipeline.  Fourth, many folks on the PMC have
> > not been active in a long time, and a new project with a smaller PMC and
> > committers list might make it more clear who is involved with FlexJS.
> >
> > - proposal ---
> >
> > Apache FlexJS for Apache Top-Level Project
> >
> > Abstract
> >
> > Apache FlexJS is a new implementation of the principles of Apache Flex
> but
> > designed for JavaScript runtimes instead of Adobe Flash/AIR runtimes.
> > Apache FlexJS was created and released as part of the Apache Flex project
> > and the UI framework is a full rewrite and does not leverage the code
> > bases donated by Adobe.  Only the FlexJS compiler source was donated by
> > Adobe.
> >
> > Over time, the set of Apache Flex committers who are working on Apache
> > Flex releases have become distinct from those working on FlexJS.  Add to
> > that the Adobe announcement of the end-of-life for Flash in the browser,
> > it makes sense to separate FlexJS from Flex so that followers of one side
> > or the other don't have to filter out emails, bugs, web pages, etc, that
> > they don't need.
> >
> > The proposal is to form an Apache FlexJS top-level project instead of
> > creating a new Incubator Podling.   That is because all of the folks
> being
> > proposed to the new Apache FlexJS PMC below have been on the Apache Flex
> > PMC for months, if not years, and understand how to participate
> > productively in an Apache project.  Plus, Apache FlexJS has already been
> > released by the top-level Apache Flex project.
> >
> > Overview of FlexJS
> >
> > Apache FlexJS is designed to improve developer productivity in creating
> > applications for wherever Javascript runs, including browsers as well as
> > Apache Cordova applications, Node, etc.  FlexJS already has an ecosystem
> > of folks creating IDEs for FlexJS, and some folks are at various points
> in
> > the process of migrating existing Flex applications to FlexJS.
> >
> > Current Status
> >
> > Meritocracy
> >
> > Within Apache Flex, the FlexJS development has been conducted as a
> > meritocracy.  No existing FlexJS developers came with the compiler code
> > base donated by Adobe nor were they on the initial committers list for
> > Apache Flex other than Alex Harui.  Everyone else has earned their way in
> > by contributing and earning merit.
> >
> > Community
> >
> > Many FlexJS users are trying to migrate an existing Apache Flex app off
> of
> > Adobe Flash.  As their migration progresses they will become less and
> less
> > interested in Apache Flex releases and activity.  However, the Apache
> Flex
> > JIRA project contains some  30,000 Flex issues migrated from Adobe's bug
> > base, and the team page for Flex makes it hard to determine which
> > committers are active on FlexJS, and it is frequently hard to determine
> if
> > a user's question is about regular Flex or FlexJS.   We are seeing an
> > increase in user interest with the Flash end-of-life announcement and
> > having separate mailing lists, web pages, and JIRA projects will help
> save
> > everyone time and energy.
> >
> > Alignment
> >
> > Apache FlexJS is already being released by Apache.
> >
> > Known Risks
> >
> > Code Extraction
> >
> > The flex-asjs, flex-tours, flex-typedefs, and flex-falcon Git repos would
> > be migrated to GitBox.  Other Apache Flex repos would be treated as
> > external dependencies.  This includes flex-utilities and the Apache Flex
> > Installer.
> >
> > Orphaned Projects
> >
> > Most FlexJS PMC members are planning to remain on the Apache Flex PMC to
> > help out just-in-case, but are already mostly inactive on the Flex code
> > bases. 

Re: [DISCUSS} Fork FlexJS from Apache Flex

[Harbs]

Very well  said.

Let’s do this! :-)

Harbs

> On Aug 29, 2017, at 7:37 AM, Alex Harui  wrote:
> 
> Hi Folks,
> 
> I (and many others on the PMC) believe there are sufficient reasons to ask
> the Apache Board of Directors to create a new Apache Top-Level Project
> called Apache FlexJS separate from Apache Flex.  The Apache Board has
> approved splitting other projects in the past and the proposal below is
> based on a past proposal to split another Apache project.
> 
> The main reason is that there seems to be a set of folks who are only
> working on Apache Flex and another set who are only working on FlexJS.
> Only a few have made commits to both products in the past year and the
> contribution to one product or the other was minimal.  Second, forking
> should save time for folks only interested in Flex or FlexJS as you don't
> have to filter out emails, web site and wiki information and bugs reports
> that apply to the product you are not interested in.  Third, forking would
> give a cleaner opportunity to try out Apache's GitBox implementation that
> allows us to leverage more GitHub functionality and make GitHub more
> primary in our development pipeline.  Fourth, many folks on the PMC have
> not been active in a long time, and a new project with a smaller PMC and
> committers list might make it more clear who is involved with FlexJS.
> 
> - proposal ---
> 
> Apache FlexJS for Apache Top-Level Project
> 
> Abstract
> 
> Apache FlexJS is a new implementation of the principles of Apache Flex but
> designed for JavaScript runtimes instead of Adobe Flash/AIR runtimes.
> Apache FlexJS was created and released as part of the Apache Flex project
> and the UI framework is a full rewrite and does not leverage the code
> bases donated by Adobe.  Only the FlexJS compiler source was donated by
> Adobe.
> 
> Over time, the set of Apache Flex committers who are working on Apache
> Flex releases have become distinct from those working on FlexJS.  Add to
> that the Adobe announcement of the end-of-life for Flash in the browser,
> it makes sense to separate FlexJS from Flex so that followers of one side
> or the other don't have to filter out emails, bugs, web pages, etc, that
> they don't need.
> 
> The proposal is to form an Apache FlexJS top-level project instead of
> creating a new Incubator Podling.   That is because all of the folks being
> proposed to the new Apache FlexJS PMC below have been on the Apache Flex
> PMC for months, if not years, and understand how to participate
> productively in an Apache project.  Plus, Apache FlexJS has already been
> released by the top-level Apache Flex project.
> 
> Overview of FlexJS
> 
> Apache FlexJS is designed to improve developer productivity in creating
> applications for wherever Javascript runs, including browsers as well as
> Apache Cordova applications, Node, etc.  FlexJS already has an ecosystem
> of folks creating IDEs for FlexJS, and some folks are at various points in
> the process of migrating existing Flex applications to FlexJS.
> 
> Current Status
> 
> Meritocracy
> 
> Within Apache Flex, the FlexJS development has been conducted as a
> meritocracy.  No existing FlexJS developers came with the compiler code
> base donated by Adobe nor were they on the initial committers list for
> Apache Flex other than Alex Harui.  Everyone else has earned their way in
> by contributing and earning merit.
> 
> Community
> 
> Many FlexJS users are trying to migrate an existing Apache Flex app off of
> Adobe Flash.  As their migration progresses they will become less and less
> interested in Apache Flex releases and activity.  However, the Apache Flex
> JIRA project contains some  30,000 Flex issues migrated from Adobe's bug
> base, and the team page for Flex makes it hard to determine which
> committers are active on FlexJS, and it is frequently hard to determine if
> a user's question is about regular Flex or FlexJS.   We are seeing an
> increase in user interest with the Flash end-of-life announcement and
> having separate mailing lists, web pages, and JIRA projects will help save
> everyone time and energy.
> 
> Alignment
> 
> Apache FlexJS is already being released by Apache.
> 
> Known Risks
> 
> Code Extraction
> 
> The flex-asjs, flex-tours, flex-typedefs, and flex-falcon Git repos would
> be migrated to GitBox.  Other Apache Flex repos would be treated as
> external dependencies.  This includes flex-utilities and the Apache Flex
> Installer.
> 
> Orphaned Projects
> 
> Most FlexJS PMC members are planning to remain on the Apache Flex PMC to
> help out just-in-case, but are already mostly inactive on the Flex code
> bases. However, there are at least 3 Apache Flex PMC members who have not
> contributed at all to FlexJS and participate in regular Flex releases, so
> the expectation is that Apache Flex will remain a viable project for some
> time to come.
> 
> Inexperience with Open Source
> 
> All of the initial team has been 

[DISCUSS} Fork FlexJS from Apache Flex

[Alex Harui]

Hi Folks,

I (and many others on the PMC) believe there are sufficient reasons to ask
the Apache Board of Directors to create a new Apache Top-Level Project
called Apache FlexJS separate from Apache Flex.  The Apache Board has
approved splitting other projects in the past and the proposal below is
based on a past proposal to split another Apache project.

The main reason is that there seems to be a set of folks who are only
working on Apache Flex and another set who are only working on FlexJS.
Only a few have made commits to both products in the past year and the
contribution to one product or the other was minimal.  Second, forking
should save time for folks only interested in Flex or FlexJS as you don't
have to filter out emails, web site and wiki information and bugs reports
that apply to the product you are not interested in.  Third, forking would
give a cleaner opportunity to try out Apache's GitBox implementation that
allows us to leverage more GitHub functionality and make GitHub more
primary in our development pipeline.  Fourth, many folks on the PMC have
not been active in a long time, and a new project with a smaller PMC and
committers list might make it more clear who is involved with FlexJS.

- proposal ---

Apache FlexJS for Apache Top-Level Project

Abstract

Apache FlexJS is a new implementation of the principles of Apache Flex but
designed for JavaScript runtimes instead of Adobe Flash/AIR runtimes.
Apache FlexJS was created and released as part of the Apache Flex project
and the UI framework is a full rewrite and does not leverage the code
bases donated by Adobe.  Only the FlexJS compiler source was donated by
Adobe.

Over time, the set of Apache Flex committers who are working on Apache
Flex releases have become distinct from those working on FlexJS.  Add to
that the Adobe announcement of the end-of-life for Flash in the browser,
it makes sense to separate FlexJS from Flex so that followers of one side
or the other don't have to filter out emails, bugs, web pages, etc, that
they don't need.

The proposal is to form an Apache FlexJS top-level project instead of
creating a new Incubator Podling.   That is because all of the folks being
proposed to the new Apache FlexJS PMC below have been on the Apache Flex
PMC for months, if not years, and understand how to participate
productively in an Apache project.  Plus, Apache FlexJS has already been
released by the top-level Apache Flex project.

Overview of FlexJS

Apache FlexJS is designed to improve developer productivity in creating
applications for wherever Javascript runs, including browsers as well as
Apache Cordova applications, Node, etc.  FlexJS already has an ecosystem
of folks creating IDEs for FlexJS, and some folks are at various points in
the process of migrating existing Flex applications to FlexJS.

Current Status

Meritocracy

Within Apache Flex, the FlexJS development has been conducted as a
meritocracy.  No existing FlexJS developers came with the compiler code
base donated by Adobe nor were they on the initial committers list for
Apache Flex other than Alex Harui.  Everyone else has earned their way in
by contributing and earning merit.

Community

Many FlexJS users are trying to migrate an existing Apache Flex app off of
Adobe Flash.  As their migration progresses they will become less and less
interested in Apache Flex releases and activity.  However, the Apache Flex
JIRA project contains some  30,000 Flex issues migrated from Adobe's bug
base, and the team page for Flex makes it hard to determine which
committers are active on FlexJS, and it is frequently hard to determine if
a user's question is about regular Flex or FlexJS.   We are seeing an
increase in user interest with the Flash end-of-life announcement and
having separate mailing lists, web pages, and JIRA projects will help save
everyone time and energy.

Alignment

Apache FlexJS is already being released by Apache.

Known Risks

Code Extraction

The flex-asjs, flex-tours, flex-typedefs, and flex-falcon Git repos would
be migrated to GitBox.  Other Apache Flex repos would be treated as
external dependencies.  This includes flex-utilities and the Apache Flex
Installer.

Orphaned Projects

Most FlexJS PMC members are planning to remain on the Apache Flex PMC to
help out just-in-case, but are already mostly inactive on the Flex code
bases. However, there are at least 3 Apache Flex PMC members who have not
contributed at all to FlexJS and participate in regular Flex releases, so
the expectation is that Apache Flex will remain a viable project for some
time to come.

Inexperience with Open Source

All of the initial team has been contributing to Apache Flex for months if
not years.

Homogenous Developers

No company employs more than two of the members of the initial team.

Reliance on Salaried Developers

Until about a year ago, only 2 of the proposed PMC members were paid to
work on FlexJS.  The rest contributed in their spare time.  Two more are
now