Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?

[Olaf Krueger]

No (Binding) 

On 2017-09-14 08:37, Dave Fisher <[hidden email]> wrote: 
> VOTE Should the Project Name of the Proposed Fork be FlexJS? 
> 
> [ ] Yes - The forked project should be Apache FlexJS. 
> [ ] No - The forked project should have another name which will be
> discussed. 
> [ ] Abstain - Don’t care what the forked project is called. 
> 
> The vote will be open for 72 hours until Sunday September 17, 16:00 UT. 



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

Re: [DISCUSS] Name of the FlexJS Fork

[Piotr Zarzycki]

For me it is definitly start like a plan. It would be good in the vote
mention that we may stay with FlexJS name as an Product - To be discussed -
even voted.

Thoughts?

Piotr

On Fri, Sep 15, 2017, 00:36 Harbs  wrote:

> Unless there are objections, I propose we continue the vote for the
> project name and we can have a separate discussion once the new project is
> formed on what to name the product.
>
> I don’t think we should rush into the decision on the product, but the
> project name is more time critical and has less marketing impact.
>
> Does that sound like a plan?
>
> Harbs
>
> > On Sep 15, 2017, at 12:42 AM, Piotr Zarzycki 
> wrote:
> >
> > Guys,
> >
> > Reading Justin's thoughts we should really consider all of that. We can
> > loose a lot of already gathered attention even if Carlos will put effort
> > for new brand.
> >
> > +1 for having Product Name as FlexJS. That would be the bridge which can
> > hold us.
> >
> > Piotr
> >
> > On Thu, Sep 14, 2017, 23:31 Peter Ent  wrote:
> >
> >> If the project name were to be "Apache Royale" and produced FlexJS, and
> >> the Apache Royale web page/wiki referenced FlexJS and made it available
> >> for Google searches, then anyone who was interested in or heard about
> >> FlexJS and searched for "FlexJS" (or "Flex" or "Adobe Flex" or "Apache
> >> Flex" or "ActionScript Flex" or ), they should get a link to Apache
> >> Royale in their search results. The blurb that accompanies the search
> >> result should mention FlexJS. I think that would be enough to pique
> >> interest and get a click.
> >>
> >> Substitute "Royale" for whatever name you'd like the project to be
> called.
> >>
> >> ‹peter
> >>
> >> On 9/14/17, 5:16 PM, "Harbs"  wrote:
> >>
> >>> It¹s great to have another perspective on this.
> >>>
> >>> Some of these issues can be addressed by SEO.
> >>>
> >>> It could be that we should be careful about changing names, and / or
> >>> timing of changing names.
> >>>
> >>> Alex does make a good point that the project name does not need to be
> the
> >>> same as the product name. It might make sense to keep the product as
> >>> FlexJS for now at least and just pick a different project name. The
> >>> product name is easier to change than the project name and a project
> can
> >>> have more than one product.
> >>>
> >>> If I would pick a reference to a product which did a major rebranding
> to
> >>> drop associations to old technology it would be Xojo. I¹m not sure how
> >>> many here are familiar with it, but it used to be call REALBasic. A few
> >>> years back they rebranded as Xojo. I don¹t think it made much of a
> >>> difference to the folks using it. I have no idea if it helped them or
> not.
> >>>
> >>> Harbs
> >>>
>  On Sep 14, 2017, at 11:07 PM, Justin M. Hill 
>  wrote:
> 
> 
>  Hi everyone,
> 
>  I am not someone with an official vote, but I wanted to express my
>  concern
>  about ditching the FlexJS name.
> 
>  The largest possible market for adoption of a new "javascript"
> solution
>  is
>  to go after those who have stuck with Flex.   There are FAR too many
>  javascript solutions on the market right now.
> 
>  If the vote is to change the name, this will:
> 
>  -- confuse the people who have been patiently waiting for FlexJS to
> get
>  to
>  1.0 so they can dive in.
> 
>  -- get lost in the noise of all of the other far more well popularized
>  javascript frameworks like Angular, React, etc.
> 
>  -- lose the feeling, however small it may be, that those who came from
>  the
>  Flex background can expect to have some of their knowledge recycled.
> 
> 
>  These are 3 critical aspects in terms of raising awareness and having
> a
>  potentially devoted following of one technology (Flex) star to
>  transition
>  and champion to a new one (FlexJS).
> 
>  If we lose that, then we effectively have to target against ALL
>  javascript
>  frameworks, most notably ones that are heavily entrenched already and
>  supported by giant company resources like Google and Facebook.
> 
> 
>  I am strongly opposed to a name change.  I think this would be a huge
>  mistake.
> 
>  On top of that, picking a new name and gaining awareness of it is
> HARD.
> 
>  It should be reason enough for the Apache powers-that-be to approve a
>  project change to avoid being stuck with a huge legacy Flex bugbase
> that
>  Adobe donated, and instead start fresh with our 1.0 name.
> 
>  If that cannot be achieved, then at a bare minimum we should seek to
>  keep
>  the name FlexJS.
> 
> 
>  Regarding targeting something other than Javascript -- like SWF or AIR
>  -- I
>  realize the debug aspect benefits are important, but all this is 

Re: [DISCUSS] Name of the FlexJS Fork

[Piotr Zarzycki]

I believe that's the idea which we should bring into the new project. Let's
be really specific about that on our page and we will not loose anything.

I would like to hear more whether Carlos in that shape would like to still
help with that by creating website etc.

I really don't want to put an mine energy on promoting stuff more than now.
I would like to still have some rings calling FlexJS name.

Piotr

On Fri, Sep 15, 2017, 02:05 Alex Harui  wrote:

> I agree that for getting new users who don't already know about Flex, that
> having a name without Flex in it would be best.  But I think Justin Hill
> is saying, and I share his concern, that folks who are sitting on a Flex
> app and thinking about migrating might be more attracted to a product
> named FlexJS than some name without Flex in it.
>
> Further, I think we might want to have one product for the migrating Flex
> customer and another for someone coming in without Flex background.  The
> getting started documentation might be different.  One would leverage
> existing knowledge of MXML and AS and draw comparisons between Flex and
> FlexJS.  Just about all migrating Flex customers don't need as much detail
> on what RemoteObject and AMF is, for example.  But a new person without
> Flex background may not even be interested in RemoteObject.  We could put
> RemoteObject support in its own SWC and not ship that SWC in a package
> that targets folks who don't know Flex.  The release package for folks
> without Flex background may not mention Flash Builder at all or contain
> the Flash Builder integration modules, launch configs, and  documentation.
>  It may not even support any other IDEs other than VSCode and maybe
> Moonshine.
>
> I'm still trying to finish up build scripts that create a non-Adobe
> release package.  Once I get that done, I can try creating a different
> non-Adobe release package that isn't a valid Flash Builder SDK and doesn't
> contain any Flash Builder support and make sure it works with VSCode and
> see if the Moonshine folks want to support it and what we would need to
> change to make it work.  And that package without Flash Builder support
> could have the same name as the Project, but the other package that
> supports other Flex IDEs could still be called FlexJS.
>
> This is why I proposed what I did last night:
> -Project name: Royale
> -Product name for folks who don't know Flex: Royale
> -Product name for folks who do know Flex: FlexJS
>
> Thoughts?
> -Alex
>
> On 9/14/17, 3:59 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
>  wrote:
>
> >In my view, the biggest reason for a fork is to get away from the name
> >Flex.
> >
> >In terms of familiarity, show a few lines of MXML code to current Flex
> >developers, they will immediately recognize it.
> >
> >The same way that I recognize JQuery if I see the $ symbol or AngularJS
> >when I see ng-something.
> >
> >My point is, if we can have a big snippet of MXML on our home page, SEO
> >for
> >flex, flejs, actionscript, mxml, etc, we should be able to cover existing
> >Flex users.
> >
> >For getting new users, IMHO, we must must get rid of the word Flex.  Once
> >someone comes in based on curiosity, we need to ensure that they like what
> >they see, namely ease of setup, ease of use, features support, etc.
> >
> >Thanks,
> >Om
> >
> >On Sep 14, 2017 3:36 PM, "Harbs"  wrote:
> >
> >> Unless there are objections, I propose we continue the vote for the
> >> project name and we can have a separate discussion once the new project
> >>is
> >> formed on what to name the product.
> >>
> >> I don’t think we should rush into the decision on the product, but the
> >> project name is more time critical and has less marketing impact.
> >>
> >> Does that sound like a plan?
> >>
> >> Harbs
> >>
> >> > On Sep 15, 2017, at 12:42 AM, Piotr Zarzycki
> >>
> >> wrote:
> >> >
> >> > Guys,
> >> >
> >> > Reading Justin's thoughts we should really consider all of that. We
> >>can
> >> > loose a lot of already gathered attention even if Carlos will put
> >>effort
> >> > for new brand.
> >> >
> >> > +1 for having Product Name as FlexJS. That would be the bridge which
> >>can
> >> > hold us.
> >> >
> >> > Piotr
> >> >
> >> > On Thu, Sep 14, 2017, 23:31 Peter Ent  wrote:
> >> >
> >> >> If the project name were to be "Apache Royale" and produced FlexJS,
> >>and
> >> >> the Apache Royale web page/wiki referenced FlexJS and made it
> >>available
> >> >> for Google searches, then anyone who was interested in or heard about
> >> >> FlexJS and searched for "FlexJS" (or "Flex" or "Adobe Flex" or
> >>"Apache
> >> >> Flex" or "ActionScript Flex" or ), they should get a link to
> >>Apache
> >> >> Royale in their search results. The blurb that accompanies the search
> >> >> result should mention FlexJS. I think that would be enough to pique
> >> >> interest 

Re: [DISCUSS] Name of the FlexJS Fork

[Alex Harui]

I agree that for getting new users who don't already know about Flex, that
having a name without Flex in it would be best.  But I think Justin Hill
is saying, and I share his concern, that folks who are sitting on a Flex
app and thinking about migrating might be more attracted to a product
named FlexJS than some name without Flex in it.

Further, I think we might want to have one product for the migrating Flex
customer and another for someone coming in without Flex background.  The
getting started documentation might be different.  One would leverage
existing knowledge of MXML and AS and draw comparisons between Flex and
FlexJS.  Just about all migrating Flex customers don't need as much detail
on what RemoteObject and AMF is, for example.  But a new person without
Flex background may not even be interested in RemoteObject.  We could put
RemoteObject support in its own SWC and not ship that SWC in a package
that targets folks who don't know Flex.  The release package for folks
without Flex background may not mention Flash Builder at all or contain
the Flash Builder integration modules, launch configs, and  documentation.
 It may not even support any other IDEs other than VSCode and maybe
Moonshine.

I'm still trying to finish up build scripts that create a non-Adobe
release package.  Once I get that done, I can try creating a different
non-Adobe release package that isn't a valid Flash Builder SDK and doesn't
contain any Flash Builder support and make sure it works with VSCode and
see if the Moonshine folks want to support it and what we would need to
change to make it work.  And that package without Flash Builder support
could have the same name as the Project, but the other package that
supports other Flex IDEs could still be called FlexJS.

This is why I proposed what I did last night:
-Project name: Royale
-Product name for folks who don't know Flex: Royale
-Product name for folks who do know Flex: FlexJS

Thoughts?
-Alex

On 9/14/17, 3:59 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:

>In my view, the biggest reason for a fork is to get away from the name
>Flex.
>
>In terms of familiarity, show a few lines of MXML code to current Flex
>developers, they will immediately recognize it.
>
>The same way that I recognize JQuery if I see the $ symbol or AngularJS
>when I see ng-something.
>
>My point is, if we can have a big snippet of MXML on our home page, SEO
>for
>flex, flejs, actionscript, mxml, etc, we should be able to cover existing
>Flex users.
>
>For getting new users, IMHO, we must must get rid of the word Flex.  Once
>someone comes in based on curiosity, we need to ensure that they like what
>they see, namely ease of setup, ease of use, features support, etc.
>
>Thanks,
>Om
>
>On Sep 14, 2017 3:36 PM, "Harbs"  wrote:
>
>> Unless there are objections, I propose we continue the vote for the
>> project name and we can have a separate discussion once the new project
>>is
>> formed on what to name the product.
>>
>> I don’t think we should rush into the decision on the product, but the
>> project name is more time critical and has less marketing impact.
>>
>> Does that sound like a plan?
>>
>> Harbs
>>
>> > On Sep 15, 2017, at 12:42 AM, Piotr Zarzycki
>>
>> wrote:
>> >
>> > Guys,
>> >
>> > Reading Justin's thoughts we should really consider all of that. We
>>can
>> > loose a lot of already gathered attention even if Carlos will put
>>effort
>> > for new brand.
>> >
>> > +1 for having Product Name as FlexJS. That would be the bridge which
>>can
>> > hold us.
>> >
>> > Piotr
>> >
>> > On Thu, Sep 14, 2017, 23:31 Peter Ent  wrote:
>> >
>> >> If the project name were to be "Apache Royale" and produced FlexJS,
>>and
>> >> the Apache Royale web page/wiki referenced FlexJS and made it
>>available
>> >> for Google searches, then anyone who was interested in or heard about
>> >> FlexJS and searched for "FlexJS" (or "Flex" or "Adobe Flex" or
>>"Apache
>> >> Flex" or "ActionScript Flex" or ), they should get a link to
>>Apache
>> >> Royale in their search results. The blurb that accompanies the search
>> >> result should mention FlexJS. I think that would be enough to pique
>> >> interest and get a click.
>> >>
>> >> Substitute "Royale" for whatever name you'd like the project to be
>> called.
>> >>
>> >> ‹peter
>> >>
>> >> On 9/14/17, 5:16 PM, "Harbs"  wrote:
>> >>
>> >>> It¹s great to have another perspective on this.
>> >>>
>> >>> Some of these issues can be addressed by SEO.
>> >>>
>> >>> It could be that we should be careful about changing names, and / or
>> >>> timing of changing names.
>> >>>
>> >>> Alex does make a good point that the project name does not need to
>>be
>> the
>> >>> same as the product name. It might make sense to keep the product as
>> >>> FlexJS for now at least and just pick a different project name. The
>> >>> 

Re: [DISCUSS] Name of the FlexJS Fork

[Harbs]

Unless there are objections, I propose we continue the vote for the project 
name and we can have a separate discussion once the new project is formed on 
what to name the product.

I don’t think we should rush into the decision on the product, but the project 
name is more time critical and has less marketing impact.

Does that sound like a plan?

Harbs

> On Sep 15, 2017, at 12:42 AM, Piotr Zarzycki  
> wrote:
> 
> Guys,
> 
> Reading Justin's thoughts we should really consider all of that. We can
> loose a lot of already gathered attention even if Carlos will put effort
> for new brand.
> 
> +1 for having Product Name as FlexJS. That would be the bridge which can
> hold us.
> 
> Piotr
> 
> On Thu, Sep 14, 2017, 23:31 Peter Ent  wrote:
> 
>> If the project name were to be "Apache Royale" and produced FlexJS, and
>> the Apache Royale web page/wiki referenced FlexJS and made it available
>> for Google searches, then anyone who was interested in or heard about
>> FlexJS and searched for "FlexJS" (or "Flex" or "Adobe Flex" or "Apache
>> Flex" or "ActionScript Flex" or ), they should get a link to Apache
>> Royale in their search results. The blurb that accompanies the search
>> result should mention FlexJS. I think that would be enough to pique
>> interest and get a click.
>> 
>> Substitute "Royale" for whatever name you'd like the project to be called.
>> 
>> ‹peter
>> 
>> On 9/14/17, 5:16 PM, "Harbs"  wrote:
>> 
>>> It¹s great to have another perspective on this.
>>> 
>>> Some of these issues can be addressed by SEO.
>>> 
>>> It could be that we should be careful about changing names, and / or
>>> timing of changing names.
>>> 
>>> Alex does make a good point that the project name does not need to be the
>>> same as the product name. It might make sense to keep the product as
>>> FlexJS for now at least and just pick a different project name. The
>>> product name is easier to change than the project name and a project can
>>> have more than one product.
>>> 
>>> If I would pick a reference to a product which did a major rebranding to
>>> drop associations to old technology it would be Xojo. I¹m not sure how
>>> many here are familiar with it, but it used to be call REALBasic. A few
>>> years back they rebranded as Xojo. I don¹t think it made much of a
>>> difference to the folks using it. I have no idea if it helped them or not.
>>> 
>>> Harbs
>>> 
 On Sep 14, 2017, at 11:07 PM, Justin M. Hill 
 wrote:
 
 
 Hi everyone,
 
 I am not someone with an official vote, but I wanted to express my
 concern
 about ditching the FlexJS name.
 
 The largest possible market for adoption of a new "javascript" solution
 is
 to go after those who have stuck with Flex.   There are FAR too many
 javascript solutions on the market right now.
 
 If the vote is to change the name, this will:
 
 -- confuse the people who have been patiently waiting for FlexJS to get
 to
 1.0 so they can dive in.
 
 -- get lost in the noise of all of the other far more well popularized
 javascript frameworks like Angular, React, etc.
 
 -- lose the feeling, however small it may be, that those who came from
 the
 Flex background can expect to have some of their knowledge recycled.
 
 
 These are 3 critical aspects in terms of raising awareness and having a
 potentially devoted following of one technology (Flex) star to
 transition
 and champion to a new one (FlexJS).
 
 If we lose that, then we effectively have to target against ALL
 javascript
 frameworks, most notably ones that are heavily entrenched already and
 supported by giant company resources like Google and Facebook.
 
 
 I am strongly opposed to a name change.  I think this would be a huge
 mistake.
 
 On top of that, picking a new name and gaining awareness of it is HARD.
 
 It should be reason enough for the Apache powers-that-be to approve a
 project change to avoid being stuck with a huge legacy Flex bugbase that
 Adobe donated, and instead start fresh with our 1.0 name.
 
 If that cannot be achieved, then at a bare minimum we should seek to
 keep
 the name FlexJS.
 
 
 Regarding targeting something other than Javascript -- like SWF or AIR
 -- I
 realize the debug aspect benefits are important, but all this is going
 to
 do is confuse people.
 
 I have read about HaXe a dozen times, and I never understand what it
 does
 because apparently it does too much.   A swiss army knife is a lot more
 confusing to use then a fixed head screwdriver.
 
 Please, we have spent SO much time trying to get to 1.0 -- lets get
 FOCUSED
 on delivering what everyone outside of the community of active
 participants
 here has been 

Re: [DISCUSS] Name of the FlexJS Fork

[OmPrakash Muppirala]

In my view, the biggest reason for a fork is to get away from the name Flex.

In terms of familiarity, show a few lines of MXML code to current Flex
developers, they will immediately recognize it.

The same way that I recognize JQuery if I see the $ symbol or AngularJS
when I see ng-something.

My point is, if we can have a big snippet of MXML on our home page, SEO for
flex, flejs, actionscript, mxml, etc, we should be able to cover existing
Flex users.

For getting new users, IMHO, we must must get rid of the word Flex.  Once
someone comes in based on curiosity, we need to ensure that they like what
they see, namely ease of setup, ease of use, features support, etc.

Thanks,
Om

On Sep 14, 2017 3:36 PM, "Harbs"  wrote:

> Unless there are objections, I propose we continue the vote for the
> project name and we can have a separate discussion once the new project is
> formed on what to name the product.
>
> I don’t think we should rush into the decision on the product, but the
> project name is more time critical and has less marketing impact.
>
> Does that sound like a plan?
>
> Harbs
>
> > On Sep 15, 2017, at 12:42 AM, Piotr Zarzycki 
> wrote:
> >
> > Guys,
> >
> > Reading Justin's thoughts we should really consider all of that. We can
> > loose a lot of already gathered attention even if Carlos will put effort
> > for new brand.
> >
> > +1 for having Product Name as FlexJS. That would be the bridge which can
> > hold us.
> >
> > Piotr
> >
> > On Thu, Sep 14, 2017, 23:31 Peter Ent  wrote:
> >
> >> If the project name were to be "Apache Royale" and produced FlexJS, and
> >> the Apache Royale web page/wiki referenced FlexJS and made it available
> >> for Google searches, then anyone who was interested in or heard about
> >> FlexJS and searched for "FlexJS" (or "Flex" or "Adobe Flex" or "Apache
> >> Flex" or "ActionScript Flex" or ), they should get a link to Apache
> >> Royale in their search results. The blurb that accompanies the search
> >> result should mention FlexJS. I think that would be enough to pique
> >> interest and get a click.
> >>
> >> Substitute "Royale" for whatever name you'd like the project to be
> called.
> >>
> >> ‹peter
> >>
> >> On 9/14/17, 5:16 PM, "Harbs"  wrote:
> >>
> >>> It¹s great to have another perspective on this.
> >>>
> >>> Some of these issues can be addressed by SEO.
> >>>
> >>> It could be that we should be careful about changing names, and / or
> >>> timing of changing names.
> >>>
> >>> Alex does make a good point that the project name does not need to be
> the
> >>> same as the product name. It might make sense to keep the product as
> >>> FlexJS for now at least and just pick a different project name. The
> >>> product name is easier to change than the project name and a project
> can
> >>> have more than one product.
> >>>
> >>> If I would pick a reference to a product which did a major rebranding
> to
> >>> drop associations to old technology it would be Xojo. I¹m not sure how
> >>> many here are familiar with it, but it used to be call REALBasic. A few
> >>> years back they rebranded as Xojo. I don¹t think it made much of a
> >>> difference to the folks using it. I have no idea if it helped them or
> not.
> >>>
> >>> Harbs
> >>>
>  On Sep 14, 2017, at 11:07 PM, Justin M. Hill 
>  wrote:
> 
> 
>  Hi everyone,
> 
>  I am not someone with an official vote, but I wanted to express my
>  concern
>  about ditching the FlexJS name.
> 
>  The largest possible market for adoption of a new "javascript"
> solution
>  is
>  to go after those who have stuck with Flex.   There are FAR too many
>  javascript solutions on the market right now.
> 
>  If the vote is to change the name, this will:
> 
>  -- confuse the people who have been patiently waiting for FlexJS to
> get
>  to
>  1.0 so they can dive in.
> 
>  -- get lost in the noise of all of the other far more well popularized
>  javascript frameworks like Angular, React, etc.
> 
>  -- lose the feeling, however small it may be, that those who came from
>  the
>  Flex background can expect to have some of their knowledge recycled.
> 
> 
>  These are 3 critical aspects in terms of raising awareness and having
> a
>  potentially devoted following of one technology (Flex) star to
>  transition
>  and champion to a new one (FlexJS).
> 
>  If we lose that, then we effectively have to target against ALL
>  javascript
>  frameworks, most notably ones that are heavily entrenched already and
>  supported by giant company resources like Google and Facebook.
> 
> 
>  I am strongly opposed to a name change.  I think this would be a huge
>  mistake.
> 
>  On top of that, picking a new name and gaining awareness of it is
> HARD.
> 
>  It 

Re: [DISCUSS] Name of the FlexJS Fork

[Piotr Zarzycki]

Guys,

Reading Justin's thoughts we should really consider all of that. We can
loose a lot of already gathered attention even if Carlos will put effort
for new brand.

+1 for having Product Name as FlexJS. That would be the bridge which can
hold us.

Piotr

On Thu, Sep 14, 2017, 23:31 Peter Ent  wrote:

> If the project name were to be "Apache Royale" and produced FlexJS, and
> the Apache Royale web page/wiki referenced FlexJS and made it available
> for Google searches, then anyone who was interested in or heard about
> FlexJS and searched for "FlexJS" (or "Flex" or "Adobe Flex" or "Apache
> Flex" or "ActionScript Flex" or ), they should get a link to Apache
> Royale in their search results. The blurb that accompanies the search
> result should mention FlexJS. I think that would be enough to pique
> interest and get a click.
>
> Substitute "Royale" for whatever name you'd like the project to be called.
>
> ‹peter
>
> On 9/14/17, 5:16 PM, "Harbs"  wrote:
>
> >It¹s great to have another perspective on this.
> >
> >Some of these issues can be addressed by SEO.
> >
> >It could be that we should be careful about changing names, and / or
> >timing of changing names.
> >
> >Alex does make a good point that the project name does not need to be the
> >same as the product name. It might make sense to keep the product as
> >FlexJS for now at least and just pick a different project name. The
> >product name is easier to change than the project name and a project can
> >have more than one product.
> >
> >If I would pick a reference to a product which did a major rebranding to
> >drop associations to old technology it would be Xojo. I¹m not sure how
> >many here are familiar with it, but it used to be call REALBasic. A few
> >years back they rebranded as Xojo. I don¹t think it made much of a
> >difference to the folks using it. I have no idea if it helped them or not.
> >
> >Harbs
> >
> >> On Sep 14, 2017, at 11:07 PM, Justin M. Hill 
> >>wrote:
> >>
> >>
> >> Hi everyone,
> >>
> >> I am not someone with an official vote, but I wanted to express my
> >>concern
> >> about ditching the FlexJS name.
> >>
> >> The largest possible market for adoption of a new "javascript" solution
> >>is
> >> to go after those who have stuck with Flex.   There are FAR too many
> >> javascript solutions on the market right now.
> >>
> >> If the vote is to change the name, this will:
> >>
> >> -- confuse the people who have been patiently waiting for FlexJS to get
> >>to
> >> 1.0 so they can dive in.
> >>
> >> -- get lost in the noise of all of the other far more well popularized
> >> javascript frameworks like Angular, React, etc.
> >>
> >> -- lose the feeling, however small it may be, that those who came from
> >>the
> >> Flex background can expect to have some of their knowledge recycled.
> >>
> >>
> >> These are 3 critical aspects in terms of raising awareness and having a
> >> potentially devoted following of one technology (Flex) star to
> >>transition
> >> and champion to a new one (FlexJS).
> >>
> >> If we lose that, then we effectively have to target against ALL
> >>javascript
> >> frameworks, most notably ones that are heavily entrenched already and
> >> supported by giant company resources like Google and Facebook.
> >>
> >>
> >> I am strongly opposed to a name change.  I think this would be a huge
> >> mistake.
> >>
> >> On top of that, picking a new name and gaining awareness of it is HARD.
> >>
> >> It should be reason enough for the Apache powers-that-be to approve a
> >> project change to avoid being stuck with a huge legacy Flex bugbase that
> >> Adobe donated, and instead start fresh with our 1.0 name.
> >>
> >> If that cannot be achieved, then at a bare minimum we should seek to
> >>keep
> >> the name FlexJS.
> >>
> >>
> >> Regarding targeting something other than Javascript -- like SWF or AIR
> >>-- I
> >> realize the debug aspect benefits are important, but all this is going
> >>to
> >> do is confuse people.
> >>
> >> I have read about HaXe a dozen times, and I never understand what it
> >>does
> >> because apparently it does too much.   A swiss army knife is a lot more
> >> confusing to use then a fixed head screwdriver.
> >>
> >> Please, we have spent SO much time trying to get to 1.0 -- lets get
> >>FOCUSED
> >> on delivering what everyone outside of the community of active
> >>participants
> >> here has been waiting on, which is a future direction for their Flex
> >> efforts.
> >>
> >> Thank you,
> >>
> >> Justin Hill
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2FProminic
> .
> >>NET=02%7C01%7C%7Ce3d4e33b77f840be8d2b08d4fbb5d605%7Cfa7b1b5a7b344387
> >>94aed2c178decee1%7C0%7C0%7C636410205784877857=cw5LAiH6bOvULqdsdx4NL
> >>GWNUawI58dy%2F4fqTI5aCaM%3D=0 | Skype: JustinProminic
> >>
> >> My Apache Flex community contribution is working on the open
> >> source Moonshine-IDE.com for FlexJS.
> >
>
>

Re: [DISCUSS] Name of the FlexJS Fork

[Peter Ent]

If the project name were to be "Apache Royale" and produced FlexJS, and
the Apache Royale web page/wiki referenced FlexJS and made it available
for Google searches, then anyone who was interested in or heard about
FlexJS and searched for "FlexJS" (or "Flex" or "Adobe Flex" or "Apache
Flex" or "ActionScript Flex" or ), they should get a link to Apache
Royale in their search results. The blurb that accompanies the search
result should mention FlexJS. I think that would be enough to pique
interest and get a click.

Substitute "Royale" for whatever name you'd like the project to be called.

‹peter

On 9/14/17, 5:16 PM, "Harbs"  wrote:

>It¹s great to have another perspective on this.
>
>Some of these issues can be addressed by SEO.
>
>It could be that we should be careful about changing names, and / or
>timing of changing names.
>
>Alex does make a good point that the project name does not need to be the
>same as the product name. It might make sense to keep the product as
>FlexJS for now at least and just pick a different project name. The
>product name is easier to change than the project name and a project can
>have more than one product.
>
>If I would pick a reference to a product which did a major rebranding to
>drop associations to old technology it would be Xojo. I¹m not sure how
>many here are familiar with it, but it used to be call REALBasic. A few
>years back they rebranded as Xojo. I don¹t think it made much of a
>difference to the folks using it. I have no idea if it helped them or not.
>
>Harbs
>
>> On Sep 14, 2017, at 11:07 PM, Justin M. Hill 
>>wrote:
>> 
>> 
>> Hi everyone,
>> 
>> I am not someone with an official vote, but I wanted to express my
>>concern
>> about ditching the FlexJS name.
>> 
>> The largest possible market for adoption of a new "javascript" solution
>>is
>> to go after those who have stuck with Flex.   There are FAR too many
>> javascript solutions on the market right now.
>> 
>> If the vote is to change the name, this will:
>> 
>> -- confuse the people who have been patiently waiting for FlexJS to get
>>to
>> 1.0 so they can dive in.
>> 
>> -- get lost in the noise of all of the other far more well popularized
>> javascript frameworks like Angular, React, etc.
>> 
>> -- lose the feeling, however small it may be, that those who came from
>>the
>> Flex background can expect to have some of their knowledge recycled.
>> 
>> 
>> These are 3 critical aspects in terms of raising awareness and having a
>> potentially devoted following of one technology (Flex) star to
>>transition
>> and champion to a new one (FlexJS).
>> 
>> If we lose that, then we effectively have to target against ALL
>>javascript
>> frameworks, most notably ones that are heavily entrenched already and
>> supported by giant company resources like Google and Facebook.
>> 
>> 
>> I am strongly opposed to a name change.  I think this would be a huge
>> mistake.
>> 
>> On top of that, picking a new name and gaining awareness of it is HARD.
>> 
>> It should be reason enough for the Apache powers-that-be to approve a
>> project change to avoid being stuck with a huge legacy Flex bugbase that
>> Adobe donated, and instead start fresh with our 1.0 name.
>> 
>> If that cannot be achieved, then at a bare minimum we should seek to
>>keep
>> the name FlexJS.
>> 
>> 
>> Regarding targeting something other than Javascript -- like SWF or AIR
>>-- I
>> realize the debug aspect benefits are important, but all this is going
>>to
>> do is confuse people.
>> 
>> I have read about HaXe a dozen times, and I never understand what it
>>does
>> because apparently it does too much.   A swiss army knife is a lot more
>> confusing to use then a fixed head screwdriver.
>> 
>> Please, we have spent SO much time trying to get to 1.0 -- lets get
>>FOCUSED
>> on delivering what everyone outside of the community of active
>>participants
>> here has been waiting on, which is a future direction for their Flex
>> efforts.
>> 
>> Thank you,
>> 
>> Justin Hill
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2FProminic.
>>NET=02%7C01%7C%7Ce3d4e33b77f840be8d2b08d4fbb5d605%7Cfa7b1b5a7b344387
>>94aed2c178decee1%7C0%7C0%7C636410205784877857=cw5LAiH6bOvULqdsdx4NL
>>GWNUawI58dy%2F4fqTI5aCaM%3D=0 | Skype: JustinProminic
>> 
>> My Apache Flex community contribution is working on the open
>> source Moonshine-IDE.com for FlexJS.
>

Re: [DISCUSS] Name of the FlexJS Fork

[Harbs]

It’s great to have another perspective on this.

Some of these issues can be addressed by SEO.

It could be that we should be careful about changing names, and / or timing of 
changing names.

Alex does make a good point that the project name does not need to be the same 
as the product name. It might make sense to keep the product as FlexJS for now 
at least and just pick a different project name. The product name is easier to 
change than the project name and a project can have more than one product.

If I would pick a reference to a product which did a major rebranding to drop 
associations to old technology it would be Xojo. I’m not sure how many here are 
familiar with it, but it used to be call REALBasic. A few years back they 
rebranded as Xojo. I don’t think it made much of a difference to the folks 
using it. I have no idea if it helped them or not.

Harbs

> On Sep 14, 2017, at 11:07 PM, Justin M. Hill  wrote:
> 
> 
> Hi everyone,
> 
> I am not someone with an official vote, but I wanted to express my concern
> about ditching the FlexJS name.
> 
> The largest possible market for adoption of a new "javascript" solution is
> to go after those who have stuck with Flex.   There are FAR too many
> javascript solutions on the market right now.
> 
> If the vote is to change the name, this will:
> 
> -- confuse the people who have been patiently waiting for FlexJS to get to
> 1.0 so they can dive in.
> 
> -- get lost in the noise of all of the other far more well popularized
> javascript frameworks like Angular, React, etc.
> 
> -- lose the feeling, however small it may be, that those who came from the
> Flex background can expect to have some of their knowledge recycled.
> 
> 
> These are 3 critical aspects in terms of raising awareness and having a
> potentially devoted following of one technology (Flex) star to transition
> and champion to a new one (FlexJS).
> 
> If we lose that, then we effectively have to target against ALL javascript
> frameworks, most notably ones that are heavily entrenched already and
> supported by giant company resources like Google and Facebook.
> 
> 
> I am strongly opposed to a name change.  I think this would be a huge
> mistake.
> 
> On top of that, picking a new name and gaining awareness of it is HARD.
> 
> It should be reason enough for the Apache powers-that-be to approve a
> project change to avoid being stuck with a huge legacy Flex bugbase that
> Adobe donated, and instead start fresh with our 1.0 name.
> 
> If that cannot be achieved, then at a bare minimum we should seek to keep
> the name FlexJS.
> 
> 
> Regarding targeting something other than Javascript -- like SWF or AIR -- I
> realize the debug aspect benefits are important, but all this is going to
> do is confuse people.
> 
> I have read about HaXe a dozen times, and I never understand what it does
> because apparently it does too much.   A swiss army knife is a lot more
> confusing to use then a fixed head screwdriver.
> 
> Please, we have spent SO much time trying to get to 1.0 -- lets get FOCUSED
> on delivering what everyone outside of the community of active participants
> here has been waiting on, which is a future direction for their Flex
> efforts.
> 
> Thank you,
> 
> Justin Hill
> http://Prominic.NET | Skype: JustinProminic
> 
> My Apache Flex community contribution is working on the open
> source Moonshine-IDE.com for FlexJS.

Re: [DISCUSS] Name of the FlexJS Fork

[Alex Harui]

Hi Justin,

Great to hear from you on this.  Do you think it would be a problem if the
project name != product name?  That we call the project Royale for example
and ship a product called FlexJS?

Thanks,
-Alex

On 9/14/17, 1:07 PM, "Justin M. Hill"  wrote:

>
>Hi everyone,
>
>I am not someone with an official vote, but I wanted to express my concern
>about ditching the FlexJS name.
>
>The largest possible market for adoption of a new "javascript" solution is
>to go after those who have stuck with Flex.   There are FAR too many
>javascript solutions on the market right now.
>
>If the vote is to change the name, this will:
>
>-- confuse the people who have been patiently waiting for FlexJS to get to
>1.0 so they can dive in.
>
>-- get lost in the noise of all of the other far more well popularized
>javascript frameworks like Angular, React, etc.
>
>-- lose the feeling, however small it may be, that those who came from the
>Flex background can expect to have some of their knowledge recycled.
>
>
>These are 3 critical aspects in terms of raising awareness and having a
>potentially devoted following of one technology (Flex) star to transition
>and champion to a new one (FlexJS).
>
>If we lose that, then we effectively have to target against ALL javascript
>frameworks, most notably ones that are heavily entrenched already and
>supported by giant company resources like Google and Facebook.
>
>
>I am strongly opposed to a name change.  I think this would be a huge
>mistake.
>
>On top of that, picking a new name and gaining awareness of it is HARD.
>
>It should be reason enough for the Apache powers-that-be to approve a
>project change to avoid being stuck with a huge legacy Flex bugbase that
>Adobe donated, and instead start fresh with our 1.0 name.
>
>If that cannot be achieved, then at a bare minimum we should seek to keep
>the name FlexJS.
>
>
>Regarding targeting something other than Javascript -- like SWF or AIR --
>I
>realize the debug aspect benefits are important, but all this is going to
>do is confuse people.
>
>I have read about HaXe a dozen times, and I never understand what it does
>because apparently it does too much.   A swiss army knife is a lot more
>confusing to use then a fixed head screwdriver.
>
>Please, we have spent SO much time trying to get to 1.0 -- lets get
>FOCUSED
>on delivering what everyone outside of the community of active
>participants
>here has been waiting on, which is a future direction for their Flex
>efforts.
>
>Thank you,
>
>Justin Hill
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2FProminic.N
>ET=02%7C01%7C%7C40c91c1f39dd46586e3708d4fbac4d4f%7Cfa7b1b5a7b34438794
>aed2c178decee1%7C0%7C0%7C636410164842659490=NLZYJpAcCc1vu%2FoFGCLv5u
>HdxM9Q2mvdLWr2xK8unGw%3D=0 | Skype: JustinProminic
>
>My Apache Flex community contribution is working on the open
>source Moonshine-IDE.com for FlexJS.

Re: [DISCUSS] Name of the FlexJS Fork

[Dave Fisher]

Your community view is important. I encourage you to VOTE!

Regards,
Dave

Sent from my iPhone

> On Sep 14, 2017, at 1:07 PM, Justin M. Hill  wrote:
> 
> 
> Hi everyone,
> 
> I am not someone with an official vote, but I wanted to express my concern
> about ditching the FlexJS name.
> 
> The largest possible market for adoption of a new "javascript" solution is
> to go after those who have stuck with Flex.   There are FAR too many
> javascript solutions on the market right now.
> 
> If the vote is to change the name, this will:
> 
> -- confuse the people who have been patiently waiting for FlexJS to get to
> 1.0 so they can dive in.
> 
> -- get lost in the noise of all of the other far more well popularized
> javascript frameworks like Angular, React, etc.
> 
> -- lose the feeling, however small it may be, that those who came from the
> Flex background can expect to have some of their knowledge recycled.
> 
> 
> These are 3 critical aspects in terms of raising awareness and having a
> potentially devoted following of one technology (Flex) star to transition
> and champion to a new one (FlexJS).
> 
> If we lose that, then we effectively have to target against ALL javascript
> frameworks, most notably ones that are heavily entrenched already and
> supported by giant company resources like Google and Facebook.
> 
> 
> I am strongly opposed to a name change.  I think this would be a huge
> mistake.
> 
> On top of that, picking a new name and gaining awareness of it is HARD.
> 
> It should be reason enough for the Apache powers-that-be to approve a
> project change to avoid being stuck with a huge legacy Flex bugbase that
> Adobe donated, and instead start fresh with our 1.0 name.
> 
> If that cannot be achieved, then at a bare minimum we should seek to keep
> the name FlexJS.
> 
> 
> Regarding targeting something other than Javascript -- like SWF or AIR -- I
> realize the debug aspect benefits are important, but all this is going to
> do is confuse people.
> 
> I have read about HaXe a dozen times, and I never understand what it does
> because apparently it does too much.   A swiss army knife is a lot more
> confusing to use then a fixed head screwdriver.
> 
> Please, we have spent SO much time trying to get to 1.0 -- lets get FOCUSED
> on delivering what everyone outside of the community of active participants
> here has been waiting on, which is a future direction for their Flex
> efforts.
> 
> Thank you,
> 
> Justin Hill
> http://Prominic.NET | Skype: JustinProminic
> 
> My Apache Flex community contribution is working on the open
> source Moonshine-IDE.com for FlexJS.

Re: [DISCUSS] Name of the FlexJS Fork

[Justin M. Hill]

Hi everyone,

I am not someone with an official vote, but I wanted to express my concern
about ditching the FlexJS name.

The largest possible market for adoption of a new "javascript" solution is
to go after those who have stuck with Flex.   There are FAR too many
javascript solutions on the market right now.

If the vote is to change the name, this will:

-- confuse the people who have been patiently waiting for FlexJS to get to
1.0 so they can dive in.

-- get lost in the noise of all of the other far more well popularized
javascript frameworks like Angular, React, etc.

-- lose the feeling, however small it may be, that those who came from the
Flex background can expect to have some of their knowledge recycled.


These are 3 critical aspects in terms of raising awareness and having a
potentially devoted following of one technology (Flex) star to transition
and champion to a new one (FlexJS).

If we lose that, then we effectively have to target against ALL javascript
frameworks, most notably ones that are heavily entrenched already and
supported by giant company resources like Google and Facebook.


I am strongly opposed to a name change.  I think this would be a huge
mistake.

On top of that, picking a new name and gaining awareness of it is HARD.

It should be reason enough for the Apache powers-that-be to approve a
project change to avoid being stuck with a huge legacy Flex bugbase that
Adobe donated, and instead start fresh with our 1.0 name.

If that cannot be achieved, then at a bare minimum we should seek to keep
the name FlexJS.


Regarding targeting something other than Javascript -- like SWF or AIR -- I
realize the debug aspect benefits are important, but all this is going to
do is confuse people.

I have read about HaXe a dozen times, and I never understand what it does
because apparently it does too much.   A swiss army knife is a lot more
confusing to use then a fixed head screwdriver.

Please, we have spent SO much time trying to get to 1.0 -- lets get FOCUSED
on delivering what everyone outside of the community of active participants
here has been waiting on, which is a future direction for their Flex
efforts.

Thank you,

Justin Hill
http://Prominic.NET | Skype: JustinProminic

My Apache Flex community contribution is working on the open
source Moonshine-IDE.com for FlexJS.

Re: [VOTE][DISCUSS] Should the Project Name of the Proposed Fork be FlexJS?

[Dave Fisher]

Thank you and I agree so long as FlexJS is not on the second ballot.

I recommend a preference list.

Sent from my iPhone

> On Sep 14, 2017, at 12:21 PM, Harbs  wrote:
> 
> Yes. I am willing to go along with changing the name and start a vote asap on 
> what it should be.
> 
> As far as I’m concerned this vote can remain open and the second vote can 
> proceed in parallel. If the first vote concludes with “yes”, then the second 
> vote will be void. I don’t see that waiting to start a second vote until the 
> first vote finishes is beneficial.
> 
> I’d REALLY like to have this wrapped up before the board meeting next week.
> 
> To be official:
> No (binding)
> 
>> On Sep 14, 2017, at 9:55 PM, Dave Fisher  wrote:
>> 
>> Is this a “No” Binding vote?
>> 
>>> On Sep 14, 2017, at 11:36 AM, Harbs  wrote:
>>> 
>>> +1 from me.
>>> 
 On Sep 14, 2017, at 9:28 PM, Alex Harui  wrote:
 
 Can we stop this vote thread and start a new one for a new name?  I don't
 want to wait until Sunday to start voting on the new name.
 
 Thanks,
 -Alex
 
> On 9/14/17, 10:33 AM, "Peter Ent"  wrote:
> 
> No (binding)
> 
>> On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:
>> 
>> VOTE Should the Project Name of the Proposed Fork be FlexJS?
>> 
>> [ ] Yes - The forked project should be Apache FlexJS.
>> [ ] No - The forked project should have another name which will be
>> discussed.
>> [ ] Abstain - Don¹t care what the forked project is called.
>> 
>> The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
>> 
> 
 
>>> 
>> 
> 

Re: [VOTE][DISCUSS] Should the Project Name of the Proposed Fork be FlexJS?

[Piotr Zarzycki]

NO (binding)

Carlos definitely helped me with the decision. He triggers me with MDL and
it was worth it, so I believe in his web design abilities and branding
super powers! :)
+1 for open vote with list of already proposed names, voters could propose
something outside list. At the end we can count everything.

Thanks,
Piotr

2017-09-14 21:21 GMT+02:00 Harbs :

> Yes. I am willing to go along with changing the name and start a vote asap
> on what it should be.
>
> As far as I’m concerned this vote can remain open and the second vote can
> proceed in parallel. If the first vote concludes with “yes”, then the
> second vote will be void. I don’t see that waiting to start a second vote
> until the first vote finishes is beneficial.
>
> I’d REALLY like to have this wrapped up before the board meeting next week.
>
> To be official:
> No (binding)
>
> > On Sep 14, 2017, at 9:55 PM, Dave Fisher  wrote:
> >
> > Is this a “No” Binding vote?
> >
> >> On Sep 14, 2017, at 11:36 AM, Harbs  wrote:
> >>
> >> +1 from me.
> >>
> >>> On Sep 14, 2017, at 9:28 PM, Alex Harui 
> wrote:
> >>>
> >>> Can we stop this vote thread and start a new one for a new name?  I
> don't
> >>> want to wait until Sunday to start voting on the new name.
> >>>
> >>> Thanks,
> >>> -Alex
> >>>
> >>> On 9/14/17, 10:33 AM, "Peter Ent"  wrote:
> >>>
>  No (binding)
> 
>  On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:
> 
> > VOTE Should the Project Name of the Proposed Fork be FlexJS?
> >
> > [ ] Yes - The forked project should be Apache FlexJS.
> > [ ] No - The forked project should have another name which will be
> > discussed.
> > [ ] Abstain - Don¹t care what the forked project is called.
> >
> > The vote will be open for 72 hours until Sunday September 17, 16:00
> UT.
> >
> 
> >>>
> >>
> >
>
>


-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

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

Re: [VOTE][DISCUSS] Should the Project Name of the Proposed Fork be FlexJS?

[Harbs]

Yes. I am willing to go along with changing the name and start a vote asap on 
what it should be.

As far as I’m concerned this vote can remain open and the second vote can 
proceed in parallel. If the first vote concludes with “yes”, then the second 
vote will be void. I don’t see that waiting to start a second vote until the 
first vote finishes is beneficial.

I’d REALLY like to have this wrapped up before the board meeting next week.

To be official:
No (binding)

> On Sep 14, 2017, at 9:55 PM, Dave Fisher  wrote:
> 
> Is this a “No” Binding vote?
> 
>> On Sep 14, 2017, at 11:36 AM, Harbs  wrote:
>> 
>> +1 from me.
>> 
>>> On Sep 14, 2017, at 9:28 PM, Alex Harui  wrote:
>>> 
>>> Can we stop this vote thread and start a new one for a new name?  I don't
>>> want to wait until Sunday to start voting on the new name.
>>> 
>>> Thanks,
>>> -Alex
>>> 
>>> On 9/14/17, 10:33 AM, "Peter Ent"  wrote:
>>> 
 No (binding)
 
 On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:
 
> VOTE Should the Project Name of the Proposed Fork be FlexJS?
> 
> [ ] Yes - The forked project should be Apache FlexJS.
> [ ] No - The forked project should have another name which will be
> discussed.
> [ ] Abstain - Don¹t care what the forked project is called.
> 
> The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
> 
 
>>> 
>> 
> 

Re: [VOTE][DISCUSS] Should the Project Name of the Proposed Fork be FlexJS?

[Dave Fisher]

Is this a No Binding VOTE?

> On Sep 14, 2017, at 11:33 AM, Piotr Zarzycki  
> wrote:
> 
> I see the consensus already,I'm sorry for the noise and insist for the VOTE
> guys. We may start VOTE on, a new name. Some folks were for YES to the old
> one, but I see that they are also open for the new name.
> 
> Piotr
> 
> 2017-09-14 20:28 GMT+02:00 Alex Harui :
> 
>> Can we stop this vote thread and start a new one for a new name?  I don't
>> want to wait until Sunday to start voting on the new name.
>> 
>> Thanks,
>> -Alex
>> 
>> On 9/14/17, 10:33 AM, "Peter Ent"  wrote:
>> 
>>> No (binding)
>>> 
>>> On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:
>>> 
 VOTE Should the Project Name of the Proposed Fork be FlexJS?
 
 [ ] Yes - The forked project should be Apache FlexJS.
 [ ] No - The forked project should have another name which will be
 discussed.
 [ ] Abstain - Don¹t care what the forked project is called.
 
 The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
 
>>> 
>> 
>> 
> 
> 
> --
> 
> Piotr Zarzycki
> 
> mobile: +48 880 859 557
> skype: zarzycki10
> 
> LinkedIn: http://www.linkedin.com/piotrzarzycki
> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE][DISCUSS] Should the Project Name of the Proposed Fork be FlexJS?

[Dave Fisher]

Is this a No Binging VOTE?

> On Sep 14, 2017, at 11:28 AM, Alex Harui  wrote:
> 
> Can we stop this vote thread and start a new one for a new name?  I don't
> want to wait until Sunday to start voting on the new name.
> 
> Thanks,
> -Alex
> 
> On 9/14/17, 10:33 AM, "Peter Ent"  wrote:
> 
>> No (binding)
>> 
>> On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:
>> 
>>> VOTE Should the Project Name of the Proposed Fork be FlexJS?
>>> 
>>> [ ] Yes - The forked project should be Apache FlexJS.
>>> [ ] No - The forked project should have another name which will be
>>> discussed.
>>> [ ] Abstain - Don¹t care what the forked project is called.
>>> 
>>> The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
>>> 
>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE][DISCUSS] Should the Project Name of the Proposed Fork be FlexJS?

[Dave Fisher]

Is this a “No” Binding vote?

> On Sep 14, 2017, at 11:36 AM, Harbs  wrote:
> 
> +1 from me.
> 
>> On Sep 14, 2017, at 9:28 PM, Alex Harui  wrote:
>> 
>> Can we stop this vote thread and start a new one for a new name?  I don't
>> want to wait until Sunday to start voting on the new name.
>> 
>> Thanks,
>> -Alex
>> 
>> On 9/14/17, 10:33 AM, "Peter Ent"  wrote:
>> 
>>> No (binding)
>>> 
>>> On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:
>>> 
 VOTE Should the Project Name of the Proposed Fork be FlexJS?
 
 [ ] Yes - The forked project should be Apache FlexJS.
 [ ] No - The forked project should have another name which will be
 discussed.
 [ ] Abstain - Don¹t care what the forked project is called.
 
 The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
 
>>> 
>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE][DISCUSS] Should the Project Name of the Proposed Fork be FlexJS?

[Dave Fisher]

Hi -

I am not available for anything until Saturday. I’m done.

I proposed the process as far as I can tell there is not even a consensus on 
what other names to vote on other than Royale. I consider this move to squash 
the vote to be steamrolling. I explained it yesterday to proceed in parallel.

There is no reason not to proceed with the VOTE. I am not rescinding it. Plenty 
of time was given to discuss this I gave a ballot and warned people what it 
would be.

Regards,
Dave

> On Sep 14, 2017, at 11:28 AM, Alex Harui  wrote:
> 
> Can we stop this vote thread and start a new one for a new name?  I don't
> want to wait until Sunday to start voting on the new name.
> 
> Thanks,
> -Alex
> 
> On 9/14/17, 10:33 AM, "Peter Ent"  wrote:
> 
>> No (binding)
>> 
>> On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:
>> 
>>> VOTE Should the Project Name of the Proposed Fork be FlexJS?
>>> 
>>> [ ] Yes - The forked project should be Apache FlexJS.
>>> [ ] No - The forked project should have another name which will be
>>> discussed.
>>> [ ] Abstain - Don¹t care what the forked project is called.
>>> 
>>> The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
>>> 
>> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: [DISCUSS] Name of the FlexJS Fork

[Alex Harui]

I just heard back from Adobe Branding.  They confirmed they do not own a
trademark for Royale and they don't care if we use it.

Thanks,
-Alex

On 9/14/17, 9:47 AM, "Alex Harui"  wrote:

>Even that is hard to explain on email.  I think "Royal" has more emphasis
>on the first syllable "ROY-el" and "Royale" is a bit more like "ro-YELL".
>
>Dictionary.com:  Royale [roi-AL]
> Royal [[ROI-uh l]
>
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dictio
>nary.com%2Fbrowse%2Froyale%3Fs%3Dt=02%7C01%7C%7C0c46e80df1784aa366110
>8d4fb9047bc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63641004447830930
>8=rlJ7AJ5JcggoPNCB%2FQkClIb8v2JOpj0bANGrG%2BGX2vs%3D=0
>Click on the pronunciation button.
>
>HTH,
>-Alex
>
>On 9/14/17, 8:12 AM, "Dave Fisher"  wrote:
>
>>Like these two names - Roy-Al
>>
>>Sent from my iPhone
>>
>>> On Sep 14, 2017, at 4:15 AM, Yishay Weiss 
>>>wrote:
>>> 
>>> How is Royale pronounced? Can Americans pronounce it and stay alive? I
>>>would go with a max 2 syllable word. If it’s Roh-yah-lay, then sorry
>>>Carlos, I’d send you back to the drawing board.
>>> 
>>> From: Harbs
>>> Sent: Thursday, September 14, 2017 12:55 PM
>>> To: dev@flex.apache.org
>>> Subject: Re: [DISCUSS] Name of the FlexJS Fork
>>> 
>>> I agree that for a new name it should just be something unique with a
>>>good “ring” to it.
>>> 
>>> Harbs
>>> 
 On Sep 14, 2017, at 12:49 PM, Olaf Krueger 
wrote:
 
 Hi,
 I just would like to mention that it seems to me that there's an inner
urge
 inside most of us to leave the beaten paths and to build a new
identity for
 FlexJS which is more appropriate to this awesome technology in any
respects.
 
 Moreover, it seems to me more and more that such a new shiny identity
 provides a fair chance to get more people involved.
 
 I just fear the effort.
 So thank you, Carlos, for your offer to help out with this!!!
 
 I like "bøje" which is the Danish translation for "bend"
 (I think this was already suggested by Harbs anywhere).
 
 I also like anagrams and words as names that don't exist yet, e.g.:
 Flex -> elfX
 
 However and whatever name, you got me!
 
 Olaf
 
 
 
 --
 Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-
f
lex-development.247.n4.nabble.com%2F=02%7C01%7C%7Cd9ec0129c007
4
247b1b708d4fb830063%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636409
9
87447708032=t6eSaFBVCFFDzu%2Bg1DutwzCNvLPL0apABdbx2raFCcI%3D
r
ved=0
>>> 
>>
>

Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?

[Harbs]

+1 from me.

> On Sep 14, 2017, at 9:28 PM, Alex Harui  wrote:
> 
> Can we stop this vote thread and start a new one for a new name?  I don't
> want to wait until Sunday to start voting on the new name.
> 
> Thanks,
> -Alex
> 
> On 9/14/17, 10:33 AM, "Peter Ent"  wrote:
> 
>> No (binding)
>> 
>> On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:
>> 
>>> VOTE Should the Project Name of the Proposed Fork be FlexJS?
>>> 
>>> [ ] Yes - The forked project should be Apache FlexJS.
>>> [ ] No - The forked project should have another name which will be
>>> discussed.
>>> [ ] Abstain - Don¹t care what the forked project is called.
>>> 
>>> The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
>>> 
>> 
> 

Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?

[Piotr Zarzycki]

I see the consensus already,I'm sorry for the noise and insist for the VOTE
guys. We may start VOTE on, a new name. Some folks were for YES to the old
one, but I see that they are also open for the new name.

Piotr

2017-09-14 20:28 GMT+02:00 Alex Harui :

> Can we stop this vote thread and start a new one for a new name?  I don't
> want to wait until Sunday to start voting on the new name.
>
> Thanks,
> -Alex
>
> On 9/14/17, 10:33 AM, "Peter Ent"  wrote:
>
> >No (binding)
> >
> >On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:
> >
> >>VOTE Should the Project Name of the Proposed Fork be FlexJS?
> >>
> >>[ ] Yes - The forked project should be Apache FlexJS.
> >>[ ] No - The forked project should have another name which will be
> >>discussed.
> >>[ ] Abstain - Don¹t care what the forked project is called.
> >>
> >>The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
> >>
> >
>
>


-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

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

Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?

[Alex Harui]

Can we stop this vote thread and start a new one for a new name?  I don't
want to wait until Sunday to start voting on the new name.

Thanks,
-Alex

On 9/14/17, 10:33 AM, "Peter Ent"  wrote:

>No (binding)
>
>On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:
>
>>VOTE Should the Project Name of the Proposed Fork be FlexJS?
>>
>>[ ] Yes - The forked project should be Apache FlexJS.
>>[ ] No - The forked project should have another name which will be
>>discussed.
>>[ ] Abstain - Don¹t care what the forked project is called.
>>
>>The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
>>
>

Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?

[Peter Ent]

No (binding)

On 9/14/17, 11:37 AM, "Dave Fisher"  wrote:

>VOTE Should the Project Name of the Proposed Fork be FlexJS?
>
>[ ] Yes - The forked project should be Apache FlexJS.
>[ ] No - The forked project should have another name which will be
>discussed.
>[ ] Abstain - Don¹t care what the forked project is called.
>
>The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
>

Re: [DISCUSS] Name of the FlexJS Fork

[Erik de Bruin]

BendForward...

(just kidding!)

EdB



On Thu, Sep 14, 2017 at 6:52 PM, Mihai Chira  wrote:

> How about FlexForward? Maybe better for the project name.
>
> On Thu, 14 Sep 2017 11:48 Harbs  wrote:
>
> > Here’s a list of other options which came up off-list:
> >
> > > Limber (or maybe Limbre/Limbur for a unique name)
> > > LimberApp
> > > Boinga (unique name which retains the message)
> > >
> > > Actually, Bead or alternately Beed might be usable
> > > Strands can probably also work.
> >
> > > Beads
> > >
> > > and second
> > >
> > > Strands
> >
> > > Action
> >
> >
> > > KickAS
> > >
> > > Another idea: NewAction
> > >
> > > What about FractionScript?
> > >
> > > NewScript?
> > > Warp
> > >
> > > We can also go for a translation of Flex.
> > >
> > > Biegen anyone? ;-)
> > >
> > > The Swedish translation looks cool: Böja
> >
> > > Maybe something to do with connections or lineage...  Heritage /
> > Ancestry / Derivation ?
> > >
> > > Or more towards the future / destination arrive / attain / reach /
> > emerge / dawn / arise
> > >
> > >
> > > "AS Dawn" sounds like a new beginning.
> >
> >
> > > On Sep 14, 2017, at 8:01 AM, Piotr Zarzycki  >
> > wrote:
> > >
> > > Don't you think guys that is too much references, regarding what Alex
> > found?
> > >
> > > We are writing in AS - what about emphasis this to RoyaleAS?
> > >
> > > I'm still not sure yet whether name change convince me..
> > >
> > > Piotr
> > >
> > > On Thu, Sep 14, 2017, 03:35 Jeffry Houser 
> wrote:
> > >
> > >> Wasn't Royale the beta name for some version of Flex?  [Flex 2? or was
> > >> it Flex 1?]
> > >>
> > >>
> > >> On 9/13/2017 6:30 PM, Dave Fisher wrote:
> > >>> Hi -
> > >>>
> > >>> I did a quick suitable name search.
> > >>>
> > >>> Royale might be taken by this individual’s project
> > >>> https://github.com/ian-culleton/royale
> > >>>
> > >>> Otherwise Royale in a TESS search is liquor and beauty products
> mostly.
> > >>> There is a lot of “Clash Royale"
> > >>>
> > >>> And there is also “Royale with Cheese” - a reference in Pulp Fiction
> > >>> to what a Macdonald’s Quarter Pounder is called in Paris.
> > >>>
> > >>> Regards,
> > >>> Dave
> > >>>
> >  On Sep 13, 2017, at 3:09 PM, Dave Fisher  >  > wrote:
> > 
> >  Hi -
> > 
> >  We have one alternative name - Royale
> > 
> >  Are there others that people would like to propose?
> > 
> >  If not then we can have a simple VOTE between FlexJS and Royale.
> > 
> >  Regards,
> >  Dave
> > 
> > > On Sep 13, 2017, at 3:01 PM, Dave Fisher  > > > wrote:
> > >
> > > Hi Om,
> > >
> > > I think that dilutes the votes and biases the result towards
> FlexJS.
> > > If we want to go that way then we need a preference ranking and
> more
> > > complicated VOTE counting.
> > >
> > > Regards,
> > > Dave
> > >
> > >> On Sep 13, 2017, at 2:57 PM, OmPrakash Muppirala
> > >> > wrote:
> > >>
> > >> We could always structure the VOTE like this:
> > >>
> > >> 1.  Royale
> > >> 2.  XXX
> > >> 3.  YYY
> > >> 4.  FlexJS
> > >>
> > >> One vote should answer both questions.
> > >>
> > >> Thanks,
> > >> Om
> > >>
> > >> On Wed, Sep 13, 2017 at 2:52 PM, Piotr Zarzycki
> > >> >
> > >> wrote:
> > >>
> > >>> On the other hand, we have rather majority of voices for do not
> > >>> change the
> > >>> name and Alex is right. - I'm seeing more people asking for help
> > with
> > >>> porting. - We may disappear in the sea of frameworks with changed
> > >>> name...
> > >>>
> > >>> Maybe better have solid framework and invest in current name
> still
> > >>> with
> > >>> nice branding. I'm puzzled, so definitely I will give myself at
> > >>> least one
> > >>> day more before VOTE.
> > >>>
> > >>> Piotr
> > >>>
> > >>>
> > >>>
> > >>> 2017-09-13 23:31 GMT+02:00 Piotr Zarzycki
> > >>> >:
> > >>>
> >  +1 for Dave's proposition on starting the VOTE for name change.
> > 
> >  I would like to also add that Carlos's proposition for help to
> >  build new
> >  brand triggers me. Peter helped also do understand that we can
> > >> always
> > >>> state
> >  from where we have come and what was our story.
> > 
> >  I'm going to change my mind on name changing and pickup "Royale"
> >  as the
> >  most powerful for the new one. - The main question is can we use
> >  it since
> >  it was code name of Macromedia 

Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?

[Erik de Bruin]

No (binding)

EdB



On Thu, Sep 14, 2017 at 5:37 PM, Dave Fisher  wrote:

> VOTE Should the Project Name of the Proposed Fork be FlexJS?
>
> [ ] Yes - The forked project should be Apache FlexJS.
> [ ] No - The forked project should have another name which will be
> discussed.
> [ ] Abstain - Don’t care what the forked project is called.
>
> The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
>
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295 <06%2051952295>
I. www.ixsoftware.nl

Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?

[Mihai Chira]

Abstain

On Thu, 14 Sep 2017 17:37 Dave Fisher  wrote:

> VOTE Should the Project Name of the Proposed Fork be FlexJS?
>
> [ ] Yes - The forked project should be Apache FlexJS.
> [ ] No - The forked project should have another name which will be
> discussed.
> [ ] Abstain - Don’t care what the forked project is called.
>
> The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
>
>

Re: [DISCUSS] Name of the FlexJS Fork

[Mihai Chira]

How about FlexForward? Maybe better for the project name.

On Thu, 14 Sep 2017 11:48 Harbs  wrote:

> Here’s a list of other options which came up off-list:
>
> > Limber (or maybe Limbre/Limbur for a unique name)
> > LimberApp
> > Boinga (unique name which retains the message)
> >
> > Actually, Bead or alternately Beed might be usable
> > Strands can probably also work.
>
> > Beads
> >
> > and second
> >
> > Strands
>
> > Action
>
>
> > KickAS
> >
> > Another idea: NewAction
> >
> > What about FractionScript?
> >
> > NewScript?
> > Warp
> >
> > We can also go for a translation of Flex.
> >
> > Biegen anyone? ;-)
> >
> > The Swedish translation looks cool: Böja
>
> > Maybe something to do with connections or lineage...  Heritage /
> Ancestry / Derivation ?
> >
> > Or more towards the future / destination arrive / attain / reach /
> emerge / dawn / arise
> >
> >
> > "AS Dawn" sounds like a new beginning.
>
>
> > On Sep 14, 2017, at 8:01 AM, Piotr Zarzycki 
> wrote:
> >
> > Don't you think guys that is too much references, regarding what Alex
> found?
> >
> > We are writing in AS - what about emphasis this to RoyaleAS?
> >
> > I'm still not sure yet whether name change convince me..
> >
> > Piotr
> >
> > On Thu, Sep 14, 2017, 03:35 Jeffry Houser  wrote:
> >
> >> Wasn't Royale the beta name for some version of Flex?  [Flex 2? or was
> >> it Flex 1?]
> >>
> >>
> >> On 9/13/2017 6:30 PM, Dave Fisher wrote:
> >>> Hi -
> >>>
> >>> I did a quick suitable name search.
> >>>
> >>> Royale might be taken by this individual’s project
> >>> https://github.com/ian-culleton/royale
> >>>
> >>> Otherwise Royale in a TESS search is liquor and beauty products mostly.
> >>> There is a lot of “Clash Royale"
> >>>
> >>> And there is also “Royale with Cheese” - a reference in Pulp Fiction
> >>> to what a Macdonald’s Quarter Pounder is called in Paris.
> >>>
> >>> Regards,
> >>> Dave
> >>>
>  On Sep 13, 2017, at 3:09 PM, Dave Fisher   > wrote:
> 
>  Hi -
> 
>  We have one alternative name - Royale
> 
>  Are there others that people would like to propose?
> 
>  If not then we can have a simple VOTE between FlexJS and Royale.
> 
>  Regards,
>  Dave
> 
> > On Sep 13, 2017, at 3:01 PM, Dave Fisher  > > wrote:
> >
> > Hi Om,
> >
> > I think that dilutes the votes and biases the result towards FlexJS.
> > If we want to go that way then we need a preference ranking and more
> > complicated VOTE counting.
> >
> > Regards,
> > Dave
> >
> >> On Sep 13, 2017, at 2:57 PM, OmPrakash Muppirala
> >> > wrote:
> >>
> >> We could always structure the VOTE like this:
> >>
> >> 1.  Royale
> >> 2.  XXX
> >> 3.  YYY
> >> 4.  FlexJS
> >>
> >> One vote should answer both questions.
> >>
> >> Thanks,
> >> Om
> >>
> >> On Wed, Sep 13, 2017 at 2:52 PM, Piotr Zarzycki
> >> >
> >> wrote:
> >>
> >>> On the other hand, we have rather majority of voices for do not
> >>> change the
> >>> name and Alex is right. - I'm seeing more people asking for help
> with
> >>> porting. - We may disappear in the sea of frameworks with changed
> >>> name...
> >>>
> >>> Maybe better have solid framework and invest in current name still
> >>> with
> >>> nice branding. I'm puzzled, so definitely I will give myself at
> >>> least one
> >>> day more before VOTE.
> >>>
> >>> Piotr
> >>>
> >>>
> >>>
> >>> 2017-09-13 23:31 GMT+02:00 Piotr Zarzycki
> >>> >:
> >>>
>  +1 for Dave's proposition on starting the VOTE for name change.
> 
>  I would like to also add that Carlos's proposition for help to
>  build new
>  brand triggers me. Peter helped also do understand that we can
> >> always
> >>> state
>  from where we have come and what was our story.
> 
>  I'm going to change my mind on name changing and pickup "Royale"
>  as the
>  most powerful for the new one. - The main question is can we use
>  it since
>  it was code name of Macromedia Framework ?
> 
>  Thanks,
>  Piotr
> 
>  2017-09-13 22:59 GMT+02:00 Dave Fisher   >:
> 
> > Hi -
> >
> > Sent from my iPhone
> >
> >> On Sep 13, 2017, at 1:40 PM, Harbs  >> > wrote:
> >>
> >> Carlos’ argument carries weight to 

Re: [DISCUSS] Name of the FlexJS Fork

[Alex Harui]

Even that is hard to explain on email.  I think "Royal" has more emphasis
on the first syllable "ROY-el" and "Royale" is a bit more like "ro-YELL".

Dictionary.com:  Royale [roi-AL]
 Royal [[ROI-uh l]


http://www.dictionary.com/browse/royale?s=t
Click on the pronunciation button.

HTH,
-Alex

On 9/14/17, 8:12 AM, "Dave Fisher"  wrote:

>Like these two names - Roy-Al
>
>Sent from my iPhone
>
>> On Sep 14, 2017, at 4:15 AM, Yishay Weiss 
>>wrote:
>> 
>> How is Royale pronounced? Can Americans pronounce it and stay alive? I
>>would go with a max 2 syllable word. If it’s Roh-yah-lay, then sorry
>>Carlos, I’d send you back to the drawing board.
>> 
>> From: Harbs
>> Sent: Thursday, September 14, 2017 12:55 PM
>> To: dev@flex.apache.org
>> Subject: Re: [DISCUSS] Name of the FlexJS Fork
>> 
>> I agree that for a new name it should just be something unique with a
>>good “ring” to it.
>> 
>> Harbs
>> 
>>> On Sep 14, 2017, at 12:49 PM, Olaf Krueger 
>>>wrote:
>>> 
>>> Hi,
>>> I just would like to mention that it seems to me that there's an inner
>>>urge
>>> inside most of us to leave the beaten paths and to build a new
>>>identity for
>>> FlexJS which is more appropriate to this awesome technology in any
>>>respects.
>>> 
>>> Moreover, it seems to me more and more that such a new shiny identity
>>> provides a fair chance to get more people involved.
>>> 
>>> I just fear the effort.
>>> So thank you, Carlos, for your offer to help out with this!!!
>>> 
>>> I like "bøje" which is the Danish translation for "bend"
>>> (I think this was already suggested by Harbs anywhere).
>>> 
>>> I also like anagrams and words as names that don't exist yet, e.g.:
>>> Flex -> elfX
>>> 
>>> However and whatever name, you got me!
>>> 
>>> Olaf
>>> 
>>> 
>>> 
>>> --
>>> Sent from: 
>>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-f
>>>lex-development.247.n4.nabble.com%2F=02%7C01%7C%7Cd9ec0129c0074
>>>247b1b708d4fb830063%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364099
>>>87447708032=t6eSaFBVCFFDzu%2Bg1DutwzCNvLPL0apABdbx2raFCcI%3D
>>>ved=0
>> 
>

Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?

[David Fisher]

No (Binding)

On 2017-09-14 08:37, Dave Fisher  wrote: 
> VOTE Should the Project Name of the Proposed Fork be FlexJS?
> 
> [ ] Yes - The forked project should be Apache FlexJS.
> [ ] No - The forked project should have another name which will be discussed.
> [ ] Abstain - Don’t care what the forked project is called.
> 
> The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
> 
> 

Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?

[OmPrakash Muppirala]

No
(binding)

On Sep 14, 2017 8:37 AM, "Dave Fisher"  wrote:

VOTE Should the Project Name of the Proposed Fork be FlexJS?

[ ] Yes - The forked project should be Apache FlexJS.
[ ] No - The forked project should have another name which will be
discussed.
[ ] Abstain - Don’t care what the forked project is called.

The vote will be open for 72 hours until Sunday September 17, 16:00 UT.

Re: [DISCUSS] Name of the FlexJS Fork

[Dave Fisher]

Like these two names - Roy-Al

Sent from my iPhone

> On Sep 14, 2017, at 4:15 AM, Yishay Weiss  wrote:
> 
> How is Royale pronounced? Can Americans pronounce it and stay alive? I would 
> go with a max 2 syllable word. If it’s Roh-yah-lay, then sorry Carlos, I’d 
> send you back to the drawing board.
> 
> From: Harbs
> Sent: Thursday, September 14, 2017 12:55 PM
> To: dev@flex.apache.org
> Subject: Re: [DISCUSS] Name of the FlexJS Fork
> 
> I agree that for a new name it should just be something unique with a good 
> “ring” to it.
> 
> Harbs
> 
>> On Sep 14, 2017, at 12:49 PM, Olaf Krueger  wrote:
>> 
>> Hi,
>> I just would like to mention that it seems to me that there's an inner urge
>> inside most of us to leave the beaten paths and to build a new identity for
>> FlexJS which is more appropriate to this awesome technology in any respects.
>> 
>> Moreover, it seems to me more and more that such a new shiny identity
>> provides a fair chance to get more people involved.
>> 
>> I just fear the effort.
>> So thank you, Carlos, for your offer to help out with this!!!
>> 
>> I like "bøje" which is the Danish translation for "bend"
>> (I think this was already suggested by Harbs anywhere).
>> 
>> I also like anagrams and words as names that don't exist yet, e.g.:
>> Flex -> elfX
>> 
>> However and whatever name, you got me!
>> 
>> Olaf
>> 
>> 
>> 
>> --
>> Sent from: http://apache-flex-development.247.n4.nabble.com/
> 

Re: [FLEXJS][Marketing] why should a web dev choose FlexJS?

[Erik de Bruin]

Piotr,

I'm not subscribed, would you mind doing this for me?

EdB



On Thu, Sep 14, 2017 at 2:16 PM, Piotr Zarzycki 
wrote:

> Hi Erik,
>
> I think this should be also forwarded to users group.
>
> Thanks,
> Piotr
>
>
> 2017-09-14 14:02 GMT+02:00 Erik de Bruin :
>
> > Hi,
> >
> > With the upcoming fork and renewed focus and most likely some publicity,
> I
> > want to ask the community to answer this question:
> >
> > Why should a web dev choose FlexJS to write JS applications, and not go
> > with a more mainstream option like e.g. TypeScript/Angular?
> >
> > I think that if we can answer that question in a compelling way, we are
> in
> > a good place as a project (from a code perspective, at least) and it
> gives
> > the marketing folks something to work with.
> >
> > Thanks,
> >
> > EdB
> >
> >
> >
> > --
> > Ix Multimedia Software
> >
> > Jan Luykenstraat 27
> > 3521 VB Utrecht
> >
> > T. 06-51952295
> > I. www.ixsoftware.nl
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> mobile: +48 880 859 557
> skype: zarzycki10
>
> LinkedIn: http://www.linkedin.com/piotrzarzycki
> 
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

Re: [FLEXJS][Marketing] why should a web dev choose FlexJS?

[Piotr Zarzycki]

Hi Erik,

I think this should be also forwarded to users group.

Thanks,
Piotr


2017-09-14 14:02 GMT+02:00 Erik de Bruin :

> Hi,
>
> With the upcoming fork and renewed focus and most likely some publicity, I
> want to ask the community to answer this question:
>
> Why should a web dev choose FlexJS to write JS applications, and not go
> with a more mainstream option like e.g. TypeScript/Angular?
>
> I think that if we can answer that question in a compelling way, we are in
> a good place as a project (from a code perspective, at least) and it gives
> the marketing folks something to work with.
>
> Thanks,
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>



-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

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

[FLEXJS][Marketing] why should a web dev choose FlexJS?

[Erik de Bruin]

Hi,

With the upcoming fork and renewed focus and most likely some publicity, I
want to ask the community to answer this question:

Why should a web dev choose FlexJS to write JS applications, and not go
with a more mainstream option like e.g. TypeScript/Angular?

I think that if we can answer that question in a compelling way, we are in
a good place as a project (from a code perspective, at least) and it gives
the marketing folks something to work with.

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

Re: [DISCUSS] Name of the FlexJS Fork

[Jeffry Houser]

 Is it worth adding, this seems to have killed Angular, allowing React 
to take the top spot?  A running joke with some of my web dev friends is 
that Angular did the same thing that Flex did with regards to Spark vs 
Halo.  They built a brand new framework with [almost] the same name that 
provides a completely different approach to building applications.  In 
the HTML space, since a lot of people felt they were starting 'from 
scratch' anyway, they moved to other technologies.



On 9/14/2017 4:34 AM, Carlos Rovira wrote:

if you compare what others are doing, you'l see that "AngularJS" is now
"Angular",


--
Jeffry Houser
Technical Entrepreneur
http://www.dot-com-it.com
http://www.jeffryhouser.com
203-379-0773

RE: [DISCUSS] Name of the FlexJS Fork

[Kessler CTR Mark J]

Royale sounds too much like Pulp Fiction...


I do like the idea of the project and frameworks have similar names.  
Although I don't mind either way.  If it's like having a make and a model, I 
would consider Apache more of the Make field and the Model being the 
SDK/framework which skips our project name all together.

In our environment they hear the framework name, but do not know what it 
means, they simply just see the end result of the products we produce.  We are 
judged on what our target application looks, feels, and functions like.  Once 
we get rid of the Flash dependency, the only negative perception will go away.  
So the ultimate framework just needs to have professional name and website.


Selling the concept of the framework is rated for us in three main aspects.

1.  Longevity; knowing it will be around a long time.

2.  Consistency that the structure, classes, and properties that we end up 
using won't be constantly changing (adding to is fine).

3.  Activity on the project showing its alive and well.


-Mark K

Re: [DISCUSS] Name of the FlexJS Fork

[Piotr Zarzycki]

Good point from Yishay :) i also really like Boja or Bend.

Thanks,
Piotr

2017-09-14 13:15 GMT+02:00 Yishay Weiss :

> How is Royale pronounced? Can Americans pronounce it and stay alive? I
> would go with a max 2 syllable word. If it’s Roh-yah-lay, then sorry
> Carlos, I’d send you back to the drawing board.
>
> From: Harbs
> Sent: Thursday, September 14, 2017 12:55 PM
> To: dev@flex.apache.org
> Subject: Re: [DISCUSS] Name of the FlexJS Fork
>
> I agree that for a new name it should just be something unique with a good
> “ring” to it.
>
> Harbs
>
> > On Sep 14, 2017, at 12:49 PM, Olaf Krueger  wrote:
> >
> > Hi,
> > I just would like to mention that it seems to me that there's an inner
> urge
> > inside most of us to leave the beaten paths and to build a new identity
> for
> > FlexJS which is more appropriate to this awesome technology in any
> respects.
> >
> > Moreover, it seems to me more and more that such a new shiny identity
> > provides a fair chance to get more people involved.
> >
> > I just fear the effort.
> > So thank you, Carlos, for your offer to help out with this!!!
> >
> > I like "bøje" which is the Danish translation for "bend"
> > (I think this was already suggested by Harbs anywhere).
> >
> > I also like anagrams and words as names that don't exist yet, e.g.:
> > Flex -> elfX
> >
> > However and whatever name, you got me!
> >
> > Olaf
> >
> >
> >
> > --
> > Sent from: http://apache-flex-development.247.n4.nabble.com/
>
>


-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

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

RE: [DISCUSS] Name of the FlexJS Fork

[Yishay Weiss]

How is Royale pronounced? Can Americans pronounce it and stay alive? I would go 
with a max 2 syllable word. If it’s Roh-yah-lay, then sorry Carlos, I’d send 
you back to the drawing board.

From: Harbs
Sent: Thursday, September 14, 2017 12:55 PM
To: dev@flex.apache.org
Subject: Re: [DISCUSS] Name of the FlexJS Fork

I agree that for a new name it should just be something unique with a good 
“ring” to it.

Harbs

> On Sep 14, 2017, at 12:49 PM, Olaf Krueger  wrote:
>
> Hi,
> I just would like to mention that it seems to me that there's an inner urge
> inside most of us to leave the beaten paths and to build a new identity for
> FlexJS which is more appropriate to this awesome technology in any respects.
>
> Moreover, it seems to me more and more that such a new shiny identity
> provides a fair chance to get more people involved.
>
> I just fear the effort.
> So thank you, Carlos, for your offer to help out with this!!!
>
> I like "bøje" which is the Danish translation for "bend"
> (I think this was already suggested by Harbs anywhere).
>
> I also like anagrams and words as names that don't exist yet, e.g.:
> Flex -> elfX
>
> However and whatever name, you got me!
>
> Olaf
>
>
>
> --
> Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS] Name of the FlexJS Fork

[Harbs]

I agree that for a new name it should just be something unique with a good 
“ring” to it.

Harbs

> On Sep 14, 2017, at 12:49 PM, Olaf Krueger  wrote:
> 
> Hi,
> I just would like to mention that it seems to me that there's an inner urge
> inside most of us to leave the beaten paths and to build a new identity for
> FlexJS which is more appropriate to this awesome technology in any respects.
> 
> Moreover, it seems to me more and more that such a new shiny identity
> provides a fair chance to get more people involved.
> 
> I just fear the effort.
> So thank you, Carlos, for your offer to help out with this!!!
> 
> I like "bøje" which is the Danish translation for "bend"
> (I think this was already suggested by Harbs anywhere).
> 
> I also like anagrams and words as names that don't exist yet, e.g.:
> Flex -> elfX 
> 
> However and whatever name, you got me!
> 
> Olaf
> 
> 
> 
> --
> Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS] Name of the FlexJS Fork

[Olaf Krueger]

Hi,
I just would like to mention that it seems to me that there's an inner urge
inside most of us to leave the beaten paths and to build a new identity for
FlexJS which is more appropriate to this awesome technology in any respects.

Moreover, it seems to me more and more that such a new shiny identity
provides a fair chance to get more people involved.

I just fear the effort.
So thank you, Carlos, for your offer to help out with this!!!

I like "bøje" which is the Danish translation for "bend"
(I think this was already suggested by Harbs anywhere).

I also like anagrams and words as names that don't exist yet, e.g.:
Flex -> elfX 

However and whatever name, you got me!

Olaf



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

Re: [DISCUSS] Name of the FlexJS Fork

[Harbs]

Here’s a list of other options which came up off-list:

> Limber (or maybe Limbre/Limbur for a unique name)
> LimberApp
> Boinga (unique name which retains the message)
> 
> Actually, Bead or alternately Beed might be usable
> Strands can probably also work.

> Beads
> 
> and second
> 
> Strands

> Action


> KickAS
> 
> Another idea: NewAction
> 
> What about FractionScript?
> 
> NewScript?
> Warp
> 
> We can also go for a translation of Flex.
> 
> Biegen anyone? ;-)
> 
> The Swedish translation looks cool: Böja

> Maybe something to do with connections or lineage...  Heritage / Ancestry / 
> Derivation ?
> 
> Or more towards the future / destination arrive / attain / reach / emerge 
> / dawn / arise
> 
> 
> "AS Dawn" sounds like a new beginning.


> On Sep 14, 2017, at 8:01 AM, Piotr Zarzycki  wrote:
> 
> Don't you think guys that is too much references, regarding what Alex found?
> 
> We are writing in AS - what about emphasis this to RoyaleAS?
> 
> I'm still not sure yet whether name change convince me..
> 
> Piotr
> 
> On Thu, Sep 14, 2017, 03:35 Jeffry Houser  wrote:
> 
>> Wasn't Royale the beta name for some version of Flex?  [Flex 2? or was
>> it Flex 1?]
>> 
>> 
>> On 9/13/2017 6:30 PM, Dave Fisher wrote:
>>> Hi -
>>> 
>>> I did a quick suitable name search.
>>> 
>>> Royale might be taken by this individual’s project
>>> https://github.com/ian-culleton/royale
>>> 
>>> Otherwise Royale in a TESS search is liquor and beauty products mostly.
>>> There is a lot of “Clash Royale"
>>> 
>>> And there is also “Royale with Cheese” - a reference in Pulp Fiction
>>> to what a Macdonald’s Quarter Pounder is called in Paris.
>>> 
>>> Regards,
>>> Dave
>>> 
 On Sep 13, 2017, at 3:09 PM, Dave Fisher > wrote:
 
 Hi -
 
 We have one alternative name - Royale
 
 Are there others that people would like to propose?
 
 If not then we can have a simple VOTE between FlexJS and Royale.
 
 Regards,
 Dave
 
> On Sep 13, 2017, at 3:01 PM, Dave Fisher  > wrote:
> 
> Hi Om,
> 
> I think that dilutes the votes and biases the result towards FlexJS.
> If we want to go that way then we need a preference ranking and more
> complicated VOTE counting.
> 
> Regards,
> Dave
> 
>> On Sep 13, 2017, at 2:57 PM, OmPrakash Muppirala
>> > wrote:
>> 
>> We could always structure the VOTE like this:
>> 
>> 1.  Royale
>> 2.  XXX
>> 3.  YYY
>> 4.  FlexJS
>> 
>> One vote should answer both questions.
>> 
>> Thanks,
>> Om
>> 
>> On Wed, Sep 13, 2017 at 2:52 PM, Piotr Zarzycki
>> >
>> wrote:
>> 
>>> On the other hand, we have rather majority of voices for do not
>>> change the
>>> name and Alex is right. - I'm seeing more people asking for help with
>>> porting. - We may disappear in the sea of frameworks with changed
>>> name...
>>> 
>>> Maybe better have solid framework and invest in current name still
>>> with
>>> nice branding. I'm puzzled, so definitely I will give myself at
>>> least one
>>> day more before VOTE.
>>> 
>>> Piotr
>>> 
>>> 
>>> 
>>> 2017-09-13 23:31 GMT+02:00 Piotr Zarzycki
>>> >:
>>> 
 +1 for Dave's proposition on starting the VOTE for name change.
 
 I would like to also add that Carlos's proposition for help to
 build new
 brand triggers me. Peter helped also do understand that we can
>> always
>>> state
 from where we have come and what was our story.
 
 I'm going to change my mind on name changing and pickup "Royale"
 as the
 most powerful for the new one. - The main question is can we use
 it since
 it was code name of Macromedia Framework ?
 
 Thanks,
 Piotr
 
 2017-09-13 22:59 GMT+02:00 Dave Fisher >:
 
> Hi -
> 
> Sent from my iPhone
> 
>> On Sep 13, 2017, at 1:40 PM, Harbs > > wrote:
>> 
>> Carlos’ argument carries weight to me.
>> 
>> If a new name will help motivate him in terms of marketing it,
>> that’s
> value I can recognize.
>> 
>> The name is not as important to me as motivating people to be
>> involved
> in the project. We can build whatever messages we want around
> the name.
>> 
>> Carlos clearly feels more passionate 

Re: [DISCUSS] Name of the FlexJS Fork

[Alex Harui]

Here's my last thought of the day:

-Use Royale for the project name
-Use FlexJS for the product name
-Call the new JS-only packaging I'm working on "Royale".

Thoughts?
-Alex

On 9/14/17, 2:06 AM, "Piotr Zarzycki"  wrote:

>I believe we need to have voting both for whether we should change, and
>later with all proposition of new name if VOTE pass.
>
>Piotr
>
>2017-09-14 11:02 GMT+02:00 Erik de Bruin :
>
>> >
>> > [...] so my preference stays with Blend
>> >
>>
>> Bend, Erik, not BLend. Wow.
>>
>> EdB
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. 
>>https://na01.safelinks.protection.outlook.com/?url=www.ixsoftware.nl
>>=02%7C01%7C%7C91263c249dc8426903e908d4fb4feb4d%7Cfa7b1b5a7b34438794aed2c1
>>78decee1%7C0%7C0%7C636409768045518882=s5HcVkyHqCMJG6mgC%2Flc5pNXw23
>>pnk6E%2BbvIZ%2BlqLCE%3D=0
>>
>
>
>
>-- 
>
>Piotr Zarzycki
>
>mobile: +48 880 859 557
>skype: zarzycki10
>
>LinkedIn: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linked
>in.com%2Fpiotrzarzycki=02%7C01%7C%7C91263c249dc8426903e908d4fb4feb4d%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636409768045518882=Yq1C
>Mwe0kx5BO2zI7ljOA%2FSr6UpU4EVAD5LE0c2r7Cg%3D=0
>din.com%2Fin%2Fpiotr-zarzycki-92a53552=02%7C01%7C%7C91263c249dc842690
>3e908d4fb4feb4d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364097680455
>18882=vWC3Jb34%2BdfFMoKI2KhlYVy4Yk4%2BRroiLhrErL3RURk%3D=0>

Re: [DISCUSS] Name of the FlexJS Fork

[Piotr Zarzycki]

I believe we need to have voting both for whether we should change, and
later with all proposition of new name if VOTE pass.

Piotr

2017-09-14 11:02 GMT+02:00 Erik de Bruin :

> >
> > [...] so my preference stays with Blend
> >
>
> Bend, Erik, not BLend. Wow.
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>



-- 

Piotr Zarzycki

mobile: +48 880 859 557
skype: zarzycki10

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

Re: [DISCUSS] Name of the FlexJS Fork

[Erik de Bruin]

>
> [...] so my preference stays with Blend
>

Bend, Erik, not BLend. Wow.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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

Re: [DISCUSS] Name of the FlexJS Fork

[Erik de Bruin]

You caught me.

Royale may be a killer name (yeah, a pun, again ;-)) but I'm not convinced.
Coming from a kingdom with a less than inspiring king, the name is not
giving me a warm and fuzzy feeling. And, to me, it is also not a really a
'catchy' name, so my preference stays with Blend. Or FlexJS, if we end up
staying with Apache after all.

EdB



On Thu, Sep 14, 2017 at 10:37 AM, Carlos Rovira <
carlos.rov...@codeoscopic.com> wrote:

> Hi Erik,
>
> you're referring to this?
>
> https://www.youtube.com/watch?v=6Pkq_eBHXJ4
>
> (minute 1'15'')
>
> hehe
>
> ;)
>
>
>
> 2017-09-14 9:29 GMT+02:00 Erik de Bruin :
>
> > Royale
> >
> > makes me think of French hamburgers :-)
> >
> > I do like
> >
> > Bend
> >
> > To keep things simple, my prime candidate is still simply
> >
> > FlexJS
> >
> > EdB
> >
> >
> >
> > On Thu, Sep 14, 2017 at 7:01 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com
> > >
> > wrote:
> >
> > > Don't you think guys that is too much references, regarding what Alex
> > > found?
> > >
> > > We are writing in AS - what about emphasis this to RoyaleAS?
> > >
> > > I'm still not sure yet whether name change convince me..
> > >
> > > Piotr
> > >
> > > On Thu, Sep 14, 2017, 03:35 Jeffry Houser 
> wrote:
> > >
> > > > Wasn't Royale the beta name for some version of Flex?  [Flex 2? or
> was
> > > > it Flex 1?]
> > > >
> > > >
> > > > On 9/13/2017 6:30 PM, Dave Fisher wrote:
> > > > > Hi -
> > > > >
> > > > > I did a quick suitable name search.
> > > > >
> > > > > Royale might be taken by this individual’s project
> > > > > https://github.com/ian-culleton/royale
> > > > >
> > > > > Otherwise Royale in a TESS search is liquor and beauty products
> > mostly.
> > > > > There is a lot of “Clash Royale"
> > > > >
> > > > > And there is also “Royale with Cheese” - a reference in Pulp
> Fiction
> > > > > to what a Macdonald’s Quarter Pounder is called in Paris.
> > > > >
> > > > > Regards,
> > > > > Dave
> > > > >
> > > > >> On Sep 13, 2017, at 3:09 PM, Dave Fisher  > > > >> > wrote:
> > > > >>
> > > > >> Hi -
> > > > >>
> > > > >> We have one alternative name - Royale
> > > > >>
> > > > >> Are there others that people would like to propose?
> > > > >>
> > > > >> If not then we can have a simple VOTE between FlexJS and Royale.
> > > > >>
> > > > >> Regards,
> > > > >> Dave
> > > > >>
> > > > >>> On Sep 13, 2017, at 3:01 PM, Dave Fisher  > > > >>> > wrote:
> > > > >>>
> > > > >>> Hi Om,
> > > > >>>
> > > > >>> I think that dilutes the votes and biases the result towards
> > FlexJS.
> > > > >>> If we want to go that way then we need a preference ranking and
> > more
> > > > >>> complicated VOTE counting.
> > > > >>>
> > > > >>> Regards,
> > > > >>> Dave
> > > > >>>
> > > >  On Sep 13, 2017, at 2:57 PM, OmPrakash Muppirala
> > > >  > wrote:
> > > > 
> > > >  We could always structure the VOTE like this:
> > > > 
> > > >  1.  Royale
> > > >  2.  XXX
> > > >  3.  YYY
> > > >  4.  FlexJS
> > > > 
> > > >  One vote should answer both questions.
> > > > 
> > > >  Thanks,
> > > >  Om
> > > > 
> > > >  On Wed, Sep 13, 2017 at 2:52 PM, Piotr Zarzycki
> > > >  >
> > > >  wrote:
> > > > 
> > > > > On the other hand, we have rather majority of voices for do not
> > > > > change the
> > > > > name and Alex is right. - I'm seeing more people asking for
> help
> > > with
> > > > > porting. - We may disappear in the sea of frameworks with
> changed
> > > > > name...
> > > > >
> > > > > Maybe better have solid framework and invest in current name
> > still
> > > > > with
> > > > > nice branding. I'm puzzled, so definitely I will give myself at
> > > > > least one
> > > > > day more before VOTE.
> > > > >
> > > > > Piotr
> > > > >
> > > > >
> > > > >
> > > > > 2017-09-13 23:31 GMT+02:00 Piotr Zarzycki
> > > > >  >>:
> > > > >
> > > > >> +1 for Dave's proposition on starting the VOTE for name
> change.
> > > > >>
> > > > >> I would like to also add that Carlos's proposition for help to
> > > > >> build new
> > > > >> brand triggers me. Peter helped also do understand that we can
> > > > always
> > > > > state
> > > > >> from where we have come and what was our story.
> > > > >>
> > > > >> I'm going to change my mind on name changing and pickup
> "Royale"
> > > > >> as the
> > > > >> most powerful for the new one. - The main question is can we
> use
> > > > >> it since
> > > > >> it was code name of Macromedia Framework ?
> > > > >>
> > > > >> Thanks,
> > > > >> Piotr
> > > > >>
> > > > >> 

Re: [DISCUSS] Name of the FlexJS Fork

[Carlos Rovira]

Hi Piotr,

if you compare what others are doing, you'l see that "AngularJS" is now
"Angular", and "React" is only that although you use JS and JSX...and is
the same for others.

For me the marketing of the name needs to be simple as that only "Royale".

You should don't mind "Royale" word is out there in many things. The same
applies for "Angular" or "React", but we all know what those words means in
our tech world ;)

Thanks


2017-09-14 7:01 GMT+02:00 Piotr Zarzycki :

> Don't you think guys that is too much references, regarding what Alex
> found?
>
> We are writing in AS - what about emphasis this to RoyaleAS?
>
> I'm still not sure yet whether name change convince me..
>
> Piotr
>
> On Thu, Sep 14, 2017, 03:35 Jeffry Houser  wrote:
>
> > Wasn't Royale the beta name for some version of Flex?  [Flex 2? or was
> > it Flex 1?]
> >
> >
> > On 9/13/2017 6:30 PM, Dave Fisher wrote:
> > > Hi -
> > >
> > > I did a quick suitable name search.
> > >
> > > Royale might be taken by this individual’s project
> > > https://github.com/ian-culleton/royale
> > >
> > > Otherwise Royale in a TESS search is liquor and beauty products mostly.
> > > There is a lot of “Clash Royale"
> > >
> > > And there is also “Royale with Cheese” - a reference in Pulp Fiction
> > > to what a Macdonald’s Quarter Pounder is called in Paris.
> > >
> > > Regards,
> > > Dave
> > >
> > >> On Sep 13, 2017, at 3:09 PM, Dave Fisher  > >> > wrote:
> > >>
> > >> Hi -
> > >>
> > >> We have one alternative name - Royale
> > >>
> > >> Are there others that people would like to propose?
> > >>
> > >> If not then we can have a simple VOTE between FlexJS and Royale.
> > >>
> > >> Regards,
> > >> Dave
> > >>
> > >>> On Sep 13, 2017, at 3:01 PM, Dave Fisher  > >>> > wrote:
> > >>>
> > >>> Hi Om,
> > >>>
> > >>> I think that dilutes the votes and biases the result towards FlexJS.
> > >>> If we want to go that way then we need a preference ranking and more
> > >>> complicated VOTE counting.
> > >>>
> > >>> Regards,
> > >>> Dave
> > >>>
> >  On Sep 13, 2017, at 2:57 PM, OmPrakash Muppirala
> >  > wrote:
> > 
> >  We could always structure the VOTE like this:
> > 
> >  1.  Royale
> >  2.  XXX
> >  3.  YYY
> >  4.  FlexJS
> > 
> >  One vote should answer both questions.
> > 
> >  Thanks,
> >  Om
> > 
> >  On Wed, Sep 13, 2017 at 2:52 PM, Piotr Zarzycki
> >  >
> >  wrote:
> > 
> > > On the other hand, we have rather majority of voices for do not
> > > change the
> > > name and Alex is right. - I'm seeing more people asking for help
> with
> > > porting. - We may disappear in the sea of frameworks with changed
> > > name...
> > >
> > > Maybe better have solid framework and invest in current name still
> > > with
> > > nice branding. I'm puzzled, so definitely I will give myself at
> > > least one
> > > day more before VOTE.
> > >
> > > Piotr
> > >
> > >
> > >
> > > 2017-09-13 23:31 GMT+02:00 Piotr Zarzycki
> > > >:
> > >
> > >> +1 for Dave's proposition on starting the VOTE for name change.
> > >>
> > >> I would like to also add that Carlos's proposition for help to
> > >> build new
> > >> brand triggers me. Peter helped also do understand that we can
> > always
> > > state
> > >> from where we have come and what was our story.
> > >>
> > >> I'm going to change my mind on name changing and pickup "Royale"
> > >> as the
> > >> most powerful for the new one. - The main question is can we use
> > >> it since
> > >> it was code name of Macromedia Framework ?
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> 2017-09-13 22:59 GMT+02:00 Dave Fisher  > >> >:
> > >>
> > >>> Hi -
> > >>>
> > >>> Sent from my iPhone
> > >>>
> >  On Sep 13, 2017, at 1:40 PM, Harbs  >  > wrote:
> > 
> >  Carlos’ argument carries weight to me.
> > 
> >  If a new name will help motivate him in terms of marketing it,
> >  that’s
> > >>> value I can recognize.
> > 
> >  The name is not as important to me as motivating people to be
> >  involved
> > >>> in the project. We can build whatever messages we want around
> > >>> the name.
> > 
> >  Carlos clearly feels more passionate about his position than I
> do
> > > about
> > >>> mine.
> > 
> >  A hesitation I have about picking a new name is that 

Re: [DISCUSS] Name of the FlexJS Fork

[Carlos Rovira]

Hi Jeffry,

exactly. As I report when I first proposed the name, as hidden bonus is the
codename used when Flex was initially created at Macromedia sometime in
2001 or 2002. I always liked that name since it evocate to me something
"magnificent", "superb", "marvelous"...as our project is ;)


2017-09-14 3:35 GMT+02:00 Jeffry Houser :

> Wasn't Royale the beta name for some version of Flex?  [Flex 2? or was it
> Flex 1?]
>
>
> On 9/13/2017 6:30 PM, Dave Fisher wrote:
>
>> Hi -
>>
>> I did a quick suitable name search.
>>
>> Royale might be taken by this individual’s project
>> https://github.com/ian-culleton/royale
>>
>> Otherwise Royale in a TESS search is liquor and beauty products mostly.
>> There is a lot of “Clash Royale"
>>
>> And there is also “Royale with Cheese” - a reference in Pulp Fiction to
>> what a Macdonald’s Quarter Pounder is called in Paris.
>>
>> Regards,
>> Dave
>>
>> On Sep 13, 2017, at 3:09 PM, Dave Fisher > dave2w...@comcast.net>> wrote:
>>>
>>> Hi -
>>>
>>> We have one alternative name - Royale
>>>
>>> Are there others that people would like to propose?
>>>
>>> If not then we can have a simple VOTE between FlexJS and Royale.
>>>
>>> Regards,
>>> Dave
>>>
>>> On Sep 13, 2017, at 3:01 PM, Dave Fisher >> dave2w...@comcast.net>> wrote:

 Hi Om,

 I think that dilutes the votes and biases the result towards FlexJS. If
 we want to go that way then we need a preference ranking and more
 complicated VOTE counting.

 Regards,
 Dave

 On Sep 13, 2017, at 2:57 PM, OmPrakash Muppirala  > wrote:
>
> We could always structure the VOTE like this:
>
> 1.  Royale
> 2.  XXX
> 3.  YYY
> 4.  FlexJS
>
> One vote should answer both questions.
>
> Thanks,
> Om
>
> On Wed, Sep 13, 2017 at 2:52 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com >
> wrote:
>
> On the other hand, we have rather majority of voices for do not change
>> the
>> name and Alex is right. - I'm seeing more people asking for help with
>> porting. - We may disappear in the sea of frameworks with changed
>> name...
>>
>> Maybe better have solid framework and invest in current name still
>> with
>> nice branding. I'm puzzled, so definitely I will give myself at least
>> one
>> day more before VOTE.
>>
>> Piotr
>>
>>
>>
>> 2017-09-13 23:31 GMT+02:00 Piotr Zarzycki > >:
>>
>> +1 for Dave's proposition on starting the VOTE for name change.
>>>
>>> I would like to also add that Carlos's proposition for help to build
>>> new
>>> brand triggers me. Peter helped also do understand that we can always
>>>
>> state
>>
>>> from where we have come and what was our story.
>>>
>>> I'm going to change my mind on name changing and pickup "Royale" as
>>> the
>>> most powerful for the new one. - The main question is can we use it
>>> since
>>> it was code name of Macromedia Framework ?
>>>
>>> Thanks,
>>> Piotr
>>>
>>> 2017-09-13 22:59 GMT+02:00 Dave Fisher >> >:
>>>
>>> Hi -

 Sent from my iPhone

 On Sep 13, 2017, at 1:40 PM, Harbs > wrote:
>
> Carlos’ argument carries weight to me.
>
> If a new name will help motivate him in terms of marketing it,
> that’s
>
 value I can recognize.

>
> The name is not as important to me as motivating people to be
> involved
>
 in the project. We can build whatever messages we want around the
 name.

>
> Carlos clearly feels more passionate about his position than I do
>
 about
>>
>>> mine.

>
> A hesitation I have about picking a new name is that I don’t want
> to
>
 delay the board’s decision on the new PMC. If we go for a new name
 can

>>> we
>>
>>> try and pick one quickly?

 Let's start the FlexJS yes or no vote tonight or tomorrow morning.

 In parallel we can discuss other names if a new name is the result
 then
 we can immediately start the next vote. We have just enough time.

 Regards,
 Dave



> Harbs
>
> On Sep 13, 2017, at 9:20 PM, Carlos Rovira <
>>
> carlos.rov...@codeoscopic.com > wrote:

>
>> Hi all,
>>
>> I'm putting 

Re: [DISCUSS] Name of the FlexJS Fork

[Carlos Rovira]

Hi Chris,

glad you like it. Thanks



2017-09-14 1:00 GMT+02:00 Chris Martin :

> Yeah no worries Carlos. I’ve been getting the same impression too. I'm
> totally down to move with what the team decides.
>
>
>
> I think a name change is fine after 3 years when the “migration link” is
> less important as most people who want to migrate will have already well
> underway if not mostly completed.
>
>
>
> Just wanted to get my thoughts up there before a [VOTE] thread hits.
>
>
>
> Loving your thoughts and insights on the name change and this discussion
> overall.
>
>
>
> Cheers,
>
>
>
> Chrsmrtn
>
> Sent from my Windows 10 phone
>
>
>
> From: Carlos Rovira
> Sent: Wednesday, September 13, 2017 3:45 PM
> To: dev@flex.apache.org
> Subject: Re: [DISCUSS] Name of the FlexJS Fork
>
>
>
> Chris,
>
> 2017-09-14 0:37 GMT+02:00 Chris Martin :
> >
> > As for the JS being apart of the name, I’m not too worried about it.
> Since
> > we’re still in pre 1.0, I’d imagine we’re still working on stabilizing
> and
> > getting that conversion to JS to work seamlessly?  Once that has
> stabilized
> > I can totally see us “cross compiling” to Android, iPhone, etc. were
> > naturally we’d want to loose the “JS” part of the name. That I can only
> > figure would land around 3 years down the road? I honestly don’t have a
> > good beat on where the FlexJS project is at right now. I feel like it’s
> > close but just not there yet.
> >
> >
> If we all already think the JS suffix is a mistake for a robust name, we
> should address it now, since it cost many time to get people know and
> respect a brand. So stick with xxxJS to change it in three years, is for me
> something we shouldn't do at all, IMHO.
>



-- 



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] Name of the FlexJS Fork

[Erik de Bruin]

Royale

makes me think of French hamburgers :-)

I do like

Bend

To keep things simple, my prime candidate is still simply

FlexJS

EdB



On Thu, Sep 14, 2017 at 7:01 AM, Piotr Zarzycki 
wrote:

> Don't you think guys that is too much references, regarding what Alex
> found?
>
> We are writing in AS - what about emphasis this to RoyaleAS?
>
> I'm still not sure yet whether name change convince me..
>
> Piotr
>
> On Thu, Sep 14, 2017, 03:35 Jeffry Houser  wrote:
>
> > Wasn't Royale the beta name for some version of Flex?  [Flex 2? or was
> > it Flex 1?]
> >
> >
> > On 9/13/2017 6:30 PM, Dave Fisher wrote:
> > > Hi -
> > >
> > > I did a quick suitable name search.
> > >
> > > Royale might be taken by this individual’s project
> > > https://github.com/ian-culleton/royale
> > >
> > > Otherwise Royale in a TESS search is liquor and beauty products mostly.
> > > There is a lot of “Clash Royale"
> > >
> > > And there is also “Royale with Cheese” - a reference in Pulp Fiction
> > > to what a Macdonald’s Quarter Pounder is called in Paris.
> > >
> > > Regards,
> > > Dave
> > >
> > >> On Sep 13, 2017, at 3:09 PM, Dave Fisher  > >> > wrote:
> > >>
> > >> Hi -
> > >>
> > >> We have one alternative name - Royale
> > >>
> > >> Are there others that people would like to propose?
> > >>
> > >> If not then we can have a simple VOTE between FlexJS and Royale.
> > >>
> > >> Regards,
> > >> Dave
> > >>
> > >>> On Sep 13, 2017, at 3:01 PM, Dave Fisher  > >>> > wrote:
> > >>>
> > >>> Hi Om,
> > >>>
> > >>> I think that dilutes the votes and biases the result towards FlexJS.
> > >>> If we want to go that way then we need a preference ranking and more
> > >>> complicated VOTE counting.
> > >>>
> > >>> Regards,
> > >>> Dave
> > >>>
> >  On Sep 13, 2017, at 2:57 PM, OmPrakash Muppirala
> >  > wrote:
> > 
> >  We could always structure the VOTE like this:
> > 
> >  1.  Royale
> >  2.  XXX
> >  3.  YYY
> >  4.  FlexJS
> > 
> >  One vote should answer both questions.
> > 
> >  Thanks,
> >  Om
> > 
> >  On Wed, Sep 13, 2017 at 2:52 PM, Piotr Zarzycki
> >  >
> >  wrote:
> > 
> > > On the other hand, we have rather majority of voices for do not
> > > change the
> > > name and Alex is right. - I'm seeing more people asking for help
> with
> > > porting. - We may disappear in the sea of frameworks with changed
> > > name...
> > >
> > > Maybe better have solid framework and invest in current name still
> > > with
> > > nice branding. I'm puzzled, so definitely I will give myself at
> > > least one
> > > day more before VOTE.
> > >
> > > Piotr
> > >
> > >
> > >
> > > 2017-09-13 23:31 GMT+02:00 Piotr Zarzycki
> > > >:
> > >
> > >> +1 for Dave's proposition on starting the VOTE for name change.
> > >>
> > >> I would like to also add that Carlos's proposition for help to
> > >> build new
> > >> brand triggers me. Peter helped also do understand that we can
> > always
> > > state
> > >> from where we have come and what was our story.
> > >>
> > >> I'm going to change my mind on name changing and pickup "Royale"
> > >> as the
> > >> most powerful for the new one. - The main question is can we use
> > >> it since
> > >> it was code name of Macromedia Framework ?
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> 2017-09-13 22:59 GMT+02:00 Dave Fisher  > >> >:
> > >>
> > >>> Hi -
> > >>>
> > >>> Sent from my iPhone
> > >>>
> >  On Sep 13, 2017, at 1:40 PM, Harbs  >  > wrote:
> > 
> >  Carlos’ argument carries weight to me.
> > 
> >  If a new name will help motivate him in terms of marketing it,
> >  that’s
> > >>> value I can recognize.
> > 
> >  The name is not as important to me as motivating people to be
> >  involved
> > >>> in the project. We can build whatever messages we want around
> > >>> the name.
> > 
> >  Carlos clearly feels more passionate about his position than I
> do
> > > about
> > >>> mine.
> > 
> >  A hesitation I have about picking a new name is that I don’t
> >  want to
> > >>> delay the board’s decision on the new PMC. If we go for a new
> > >>> name can
> > > we
> > >>> try and pick one quickly?
> > >>>
> > >>> Let's start the FlexJS yes or no vote tonight or tomorrow
> morning.
> >