Re: [VOTE] Fork FlexJS from Apache Flex

[Alex Harui]

+1 from me.

On 8/31/17, 11:28 PM, "Alex Harui"  wrote:

>Hi folks,
>
>Here is the vote thread.  Please vote on whether to submit the proposal
>below to the board.  Please use +1 for yes, -1 for no, and if you want,
>any number in-between per [1].  Only PMC member votes will be used to
>determine the results, but we are more than happy to hear from non-PMC
>members as well.
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apach
>e.org%2Ffoundation%2Fvoting.html%23expressing-votes-1-0-1-and-fr=02%7
>C01%7C%7C5a9a9e3e6a99464b30ab08d4f102a66a%7Cfa7b1b5a7b34438794aed2c178dece
>e1%7C0%7C0%7C636398441064819782=NIXiUWgnEkLRP%2BQSbG1dLC1YjEvRKOGxdE
>er%2BSE1QPA%3D=0
>actions
>
>Thanks,
>-Alex
>
> 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 but one 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 paid to migrate an existing application and thus contribute to add
>missing features and fix bugs.  By creating a separate project, we hope to
>attract more folks who may not want to be involved with the legacy Apache
>Flex code.
>
>Relationship with Existing Apache Projects
>
>Apache FlexJS might use some releases from Apache Flex for some features
>or for an Installer 

Re: [VOTE] Fork FlexJS from Apache Flex

[Tom Chiverton]

+1

People being on/not on the project board can be resolved after the split.

Tom


On 01/09/17 09:43, Yishay Weiss wrote:

+1

From: Alex Harui
Sent: Friday, September 1, 2017 9:28 AM
To: dev@flex.apache.org
Subject: [VOTE] Fork FlexJS from Apache Flex

Hi folks,

Here is the vote thread.  Please vote on whether to submit the proposal
below to the board.  Please use +1 for yes, -1 for no, and if you want,
any number in-between per [1].  Only PMC member votes will be used to
determine the results, but we are more than happy to hear from non-PMC
members as well.

[1]
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr
actions

Thanks,
-Alex

 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 but one 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 paid to migrate an existing application and thus contribute to add
missing features and fix bugs.  By creating a separate project, we hope to
attract more folks who may not want to be involved with the legacy Apache
Flex code.

Relationship with Existing Apache Projects

Apache FlexJS might use some releases from Apache Flex for some features
or for an Installer app.  FlexJS can be used to create Apache Cordova
applications and we hope to find time to make the Cordova community 

Re: [VOTE] Fork FlexJS from Apache Flex

[Jose Barragan]

+1

> On 1 Sep 2017, at 20:44, Frédéric THOMAS  wrote:
> 
> +1 binding
> 
> Fred.
> 
> Sent from Samsung tablet.
> 
> 
>  Original message 
> From: Alex Harui 
> Date: 01/09/2017 07:28 (GMT+00:00)
> To: dev@flex.apache.org
> Subject: [VOTE] Fork FlexJS from Apache Flex
> 
> Hi folks,
> 
> Here is the vote thread.  Please vote on whether to submit the proposal
> below to the board.  Please use +1 for yes, -1 for no, and if you want,
> any number in-between per [1].  Only PMC member votes will be used to
> determine the results, but we are more than happy to hear from non-PMC
> members as well.
> 
> [1]
> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr
> actions
> 
> Thanks,
> -Alex
> 
>  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 but one 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 paid to migrate an existing application and thus contribute to add
> missing features and fix bugs.  By creating a separate project, we hope to
> attract more folks who may not want to be involved with the legacy Apache
> Flex code.
> 
> 

Re: [VOTE] Fork FlexJS from Apache Flex

[Frédéric THOMAS]

+1 binding

Fred.

Sent from Samsung tablet.


 Original message 
From: Alex Harui 
Date: 01/09/2017 07:28 (GMT+00:00)
To: dev@flex.apache.org
Subject: [VOTE] Fork FlexJS from Apache Flex

Hi folks,

Here is the vote thread.  Please vote on whether to submit the proposal
below to the board.  Please use +1 for yes, -1 for no, and if you want,
any number in-between per [1].  Only PMC member votes will be used to
determine the results, but we are more than happy to hear from non-PMC
members as well.

[1]
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr
actions

Thanks,
-Alex

 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 but one 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 paid to migrate an existing application and thus contribute to add
missing features and fix bugs.  By creating a separate project, we hope to
attract more folks who may not want to be involved with the legacy Apache
Flex code.

Relationship with Existing Apache Projects

Apache FlexJS might use some releases from Apache Flex for some features
or for an Installer app.  FlexJS can be used to create Apache Cordova
applications and we hope to find time to make the Cordova community aware
of this capability.  The Apache FlexJS Compiler has dependencies on Apache

RE: [VOTE] Fork FlexJS from Apache Flex

[OmPrakash Muppirala]

+1 binding

On Sep 1, 2017 8:59 AM, "Chris Martin"  wrote:

> +1 (binding)
>
> Chris
>
> From: Alex Harui
> Sent: Thursday, August 31, 2017 11:28 PM
> To: dev@flex.apache.org
> Subject: [VOTE] Fork FlexJS from Apache Flex
>
> Hi folks,
>
> Here is the vote thread.  Please vote on whether to submit the proposal
> below to the board.  Please use +1 for yes, -1 for no, and if you want,
> any number in-between per [1].  Only PMC member votes will be used to
> determine the results, but we are more than happy to hear from non-PMC
> members as well.
>
> [1]
> https://www.apache.org/foundation/voting.html#
> expressing-votes-1-0-1-and-fr
> actions
>
> Thanks,
> -Alex
>
>  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 but one 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 paid to migrate an existing application and thus contribute to add
> missing features and fix bugs.  By creating a separate project, we hope to
> attract more folks who may not want to be involved with the legacy Apache
> Flex code.
>
> Relationship with Existing Apache Projects
>
> Apache FlexJS 

RE: [VOTE] Fork FlexJS from Apache Flex

[Chris Martin]

+1 (binding)

Chris

From: Alex Harui
Sent: Thursday, August 31, 2017 11:28 PM
To: dev@flex.apache.org
Subject: [VOTE] Fork FlexJS from Apache Flex

Hi folks,

Here is the vote thread.  Please vote on whether to submit the proposal
below to the board.  Please use +1 for yes, -1 for no, and if you want,
any number in-between per [1].  Only PMC member votes will be used to
determine the results, but we are more than happy to hear from non-PMC
members as well.

[1]
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr
actions

Thanks,
-Alex

 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 but one 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 paid to migrate an existing application and thus contribute to add
missing features and fix bugs.  By creating a separate project, we hope to
attract more folks who may not want to be involved with the legacy Apache
Flex code.

Relationship with Existing Apache Projects

Apache FlexJS might use some releases from Apache Flex for some features
or for an Installer app.  FlexJS can be used to create Apache Cordova
applications and we hope to find time to make the Cordova community aware
of this capability.  The Apache FlexJS Compiler has dependencies on Apache
Commons, and we use Apache 

Re: [VOTE] Fork FlexJS from Apache Flex

[Jeffry Houser]

+0


On 9/1/2017 11:36 AM, Michael Schmalle wrote:

+1

On Fri, Sep 1, 2017 at 2:28 AM, Alex Harui  wrote:


Hi folks,

Here is the vote thread.  Please vote on whether to submit the proposal
below to the board.  Please use +1 for yes, -1 for no, and if you want,
any number in-between per [1].  Only PMC member votes will be used to
determine the results, but we are more than happy to hear from non-PMC
members as well.

[1]
https://www.apache.org/foundation/voting.html#
expressing-votes-1-0-1-and-fr
actions

Thanks,
-Alex

 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 but one 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 paid to migrate an existing application and thus contribute to add
missing features and fix bugs.  By creating a separate project, we hope to
attract more folks who may not want to be involved with the legacy Apache
Flex code.

Relationship with Existing Apache Projects

Apache FlexJS might use some releases from Apache Flex for some features
or for an Installer app.  FlexJS can be used to create Apache Cordova
applications and we hope to find time to make the Cordova community aware
of this capability.  The Apache FlexJS Compiler has dependencies on Apache
Commons, and we use Apache Ant and Apache Maven for building the various
release artifacts.

Re: [VOTE] Fork FlexJS from Apache Flex

[Michael Schmalle]

+1

On Fri, Sep 1, 2017 at 2:28 AM, Alex Harui  wrote:

> Hi folks,
>
> Here is the vote thread.  Please vote on whether to submit the proposal
> below to the board.  Please use +1 for yes, -1 for no, and if you want,
> any number in-between per [1].  Only PMC member votes will be used to
> determine the results, but we are more than happy to hear from non-PMC
> members as well.
>
> [1]
> https://www.apache.org/foundation/voting.html#
> expressing-votes-1-0-1-and-fr
> actions
>
> Thanks,
> -Alex
>
>  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 but one 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 paid to migrate an existing application and thus contribute to add
> missing features and fix bugs.  By creating a separate project, we hope to
> attract more folks who may not want to be involved with the legacy Apache
> Flex code.
>
> Relationship with Existing Apache Projects
>
> Apache FlexJS might use some releases from Apache Flex for some features
> or for an Installer app.  FlexJS can be used to create Apache Cordova
> applications and we hope to find time to make the Cordova community aware
> of this capability.  

Re: [VOTE] Fork FlexJS from Apache Flex

[Josh Tynjala]

+1

- Josh

On Aug 31, 2017 11:28 PM, "Alex Harui"  wrote:

> Hi folks,
>
> Here is the vote thread.  Please vote on whether to submit the proposal
> below to the board.  Please use +1 for yes, -1 for no, and if you want,
> any number in-between per [1].  Only PMC member votes will be used to
> determine the results, but we are more than happy to hear from non-PMC
> members as well.
>
> [1]
> https://www.apache.org/foundation/voting.html#
> expressing-votes-1-0-1-and-fr
> actions
>
> Thanks,
> -Alex
>
>  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 but one 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 paid to migrate an existing application and thus contribute to add
> missing features and fix bugs.  By creating a separate project, we hope to
> attract more folks who may not want to be involved with the legacy Apache
> Flex code.
>
> Relationship with Existing Apache Projects
>
> Apache FlexJS might use some releases from Apache Flex for some features
> or for an Installer app.  FlexJS can be used to create Apache Cordova
> applications and we hope to find time to make the Cordova community aware
> of this 

Re: [VOTE] Fork FlexJS from Apache Flex

[Peter Ent]

+1 (Binding)

Peter Ent
Adobe Systems

On 9/1/17, 6:08 AM, "Christofer Dutz"  wrote:

>-1 (Binding)
>
>As I mentioned, I cannot support this proposal as is as I was excluded
>from the PMC of the Fork.
>
>Chris
>
>On 2017-09-01 08:28, Alex Harui  wrote:
>> Hi folks,
>> 
>> Here is the vote thread.  Please vote on whether to submit the proposal
>> below to the board.  Please use +1 for yes, -1 for no, and if you want,
>> any number in-between per [1].  Only PMC member votes will be used to
>> determine the results, but we are more than happy to hear from non-PMC
>> members as well.
>> 
>> [1] 
>> 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apac
>>he.org%2Ffoundation%2Fvoting.html%23expressing-votes-1-0-1-and-fr=02
>>%7C01%7C%7C5dd4777434ed403611ee08d4f1216a59%7Cfa7b1b5a7b34438794aed2c178d
>>ecee1%7C0%7C0%7C636398573211692953=mXv73ODe8jVAjKrcVT6n%2FVgBBJWUcx
>>%2F%2FVSMpia%2B5DUw%3D=0
>> actions
>> 
>> Thanks,
>> -Alex
>> 
>>  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 but one 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 

Re: [VOTE] Fork FlexJS from Apache Flex

[Christofer Dutz]

-1 (Binding)

As I mentioned, I cannot support this proposal as is as I was excluded from the 
PMC of the Fork.

Chris

On 2017-09-01 08:28, Alex Harui  wrote: 
> Hi folks,
> 
> Here is the vote thread.  Please vote on whether to submit the proposal
> below to the board.  Please use +1 for yes, -1 for no, and if you want,
> any number in-between per [1].  Only PMC member votes will be used to
> determine the results, but we are more than happy to hear from non-PMC
> members as well.
> 
> [1] 
> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr
> actions
> 
> Thanks,
> -Alex
> 
>  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 but one 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 paid to migrate an existing application and thus contribute to add
> missing features and fix bugs.  By creating a separate project, we hope to
> attract more folks who may not want to be involved with the legacy Apache
> Flex code.
> 
> Relationship with Existing Apache Projects
> 
> Apache FlexJS might use some releases from Apache Flex for some features
> or for an Installer app.  FlexJS 

RE: [VOTE] Fork FlexJS from Apache Flex

[Kessler CTR Mark J]

+1 (binding)


-Mark K

-Original Message-
From: Alex Harui [mailto:aha...@adobe.com.INVALID]
Sent: Friday, September 01, 2017 2:28 AM
To: dev@flex.apache.org
Subject: [Non-DoD Source] [VOTE] Fork FlexJS from Apache Flex

Hi folks,

Here is the vote thread.  Please vote on whether to submit the proposal
below to the board.  Please use +1 for yes, -1 for no, and if you want,
any number in-between per [1].  Only PMC member votes will be used to
determine the results, but we are more than happy to hear from non-PMC
members as well.

[1]
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr
actions

Thanks,
-Alex

Re: [VOTE] Fork FlexJS from Apache Flex

[Justin Mclean]

Hi,

-1 binding as there are still outstanding questions in the discussion thread 
and the committer/PMC lists have not been amended.

While I’m not against a FlexJS becoming it’s own project seperate from the Flex 
SDK and there’s probably good reasons from a marketing point of view there 
seem's to be no real technical reason to do so. There also hasn’t been any real 
discussion on the list about about the pros and cons about this other that what 
in the proposal. It seems a little rushed to me.

The proposal currently omits several people that IMO should be on the PMC and 
committer list - myself included. The usual process is to ask existing PMC and 
committers if they want to be on the new PMC and AFAIK this hasn’t been done. 
It also includes 1/2 dozen people who have not made any contributions for 1+ 
year which on it’s own is not an issue (as they are already committers/PMC 
members) but seems odd when combined with the obvious omissions.

Thanks,
Justin

PS I’m just about to board a 24 flight and spend 2 week travelling so will only 
have limited access and time to respond to anything on this list.

RE: [VOTE] Fork FlexJS from Apache Flex

[Yishay Weiss]

+1

From: Alex Harui
Sent: Friday, September 1, 2017 9:28 AM
To: dev@flex.apache.org
Subject: [VOTE] Fork FlexJS from Apache Flex

Hi folks,

Here is the vote thread.  Please vote on whether to submit the proposal
below to the board.  Please use +1 for yes, -1 for no, and if you want,
any number in-between per [1].  Only PMC member votes will be used to
determine the results, but we are more than happy to hear from non-PMC
members as well.

[1]
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr
actions

Thanks,
-Alex

 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 but one 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 paid to migrate an existing application and thus contribute to add
missing features and fix bugs.  By creating a separate project, we hope to
attract more folks who may not want to be involved with the legacy Apache
Flex code.

Relationship with Existing Apache Projects

Apache FlexJS might use some releases from Apache Flex for some features
or for an Installer app.  FlexJS can be used to create Apache Cordova
applications and we hope to find time to make the Cordova community aware
of this capability.  The Apache FlexJS Compiler has dependencies on Apache
Commons, and we use Apache Ant and Apache 

Re: [VOTE] Fork FlexJS from Apache Flex

[Olaf Krueger]

+1

Olaf



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

Re: [VOTE] Fork FlexJS from Apache Flex

[Erik de Bruin]

+1

EdB



On Fri, Sep 1, 2017 at 8:28 AM, Alex Harui  wrote:

> Hi folks,
>
> Here is the vote thread.  Please vote on whether to submit the proposal
> below to the board.  Please use +1 for yes, -1 for no, and if you want,
> any number in-between per [1].  Only PMC member votes will be used to
> determine the results, but we are more than happy to hear from non-PMC
> members as well.
>
> [1]
> https://www.apache.org/foundation/voting.html#
> expressing-votes-1-0-1-and-fr
> actions
>
> Thanks,
> -Alex
>
>  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 but one 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 paid to migrate an existing application and thus contribute to add
> missing features and fix bugs.  By creating a separate project, we hope to
> attract more folks who may not want to be involved with the legacy Apache
> Flex code.
>
> Relationship with Existing Apache Projects
>
> Apache FlexJS might use some releases from Apache Flex for some features
> or for an Installer app.  FlexJS can be used to create Apache Cordova
> applications and we hope to find time to make the Cordova community aware
> of this 

Re: [VOTE] Fork FlexJS from Apache Flex

[Piotr Zarzycki]

+1

On Fri, Sep 1, 2017, 09:00 Harbs  wrote:

> +1
>
> Harbs
>
> > On Sep 1, 2017, at 9:28 AM, Alex Harui  wrote:
> >
> > Hi folks,
> >
> > Here is the vote thread.  Please vote on whether to submit the proposal
> > below to the board.  Please use +1 for yes, -1 for no, and if you want,
> > any number in-between per [1].  Only PMC member votes will be used to
> > determine the results, but we are more than happy to hear from non-PMC
> > members as well.
> >
> > [1]
> >
> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr
> > actions
> >
> > Thanks,
> > -Alex
> >
> >  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 but one 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 paid to migrate an existing application and thus contribute to add
> > missing features and fix bugs.  By creating a separate project, we hope
> to
> > attract more folks who may not want to be involved with 

Re: [VOTE] Fork FlexJS from Apache Flex

[Harbs]

+1

Harbs

> On Sep 1, 2017, at 9:28 AM, Alex Harui  wrote:
> 
> Hi folks,
> 
> Here is the vote thread.  Please vote on whether to submit the proposal
> below to the board.  Please use +1 for yes, -1 for no, and if you want,
> any number in-between per [1].  Only PMC member votes will be used to
> determine the results, but we are more than happy to hear from non-PMC
> members as well.
> 
> [1] 
> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr
> actions
> 
> Thanks,
> -Alex
> 
>  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 but one 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 paid to migrate an existing application and thus contribute to add
> missing features and fix bugs.  By creating a separate project, we hope to
> attract more folks who may not want to be involved with the legacy Apache
> Flex code.
> 
> Relationship with Existing Apache Projects
> 
> Apache FlexJS might use some releases from Apache Flex for some features
> or for an Installer app.  FlexJS can be used to create Apache Cordova
> applications and we hope to find time to make the Cordova