Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

> > [...] 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

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

Re: [DISCUSS] Name of the FlexJS Fork

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

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

Re: [DISCUSS] Name of the FlexJS Fork

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,

Re: [DISCUSS] Name of the FlexJS Fork

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 >

Re: [DISCUSS] Name of the FlexJS Fork

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 > > > >

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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

RE: [DISCUSS] Name of the FlexJS Fork

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:

Re: [DISCUSS] Name of the FlexJS Fork

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 ;)

Re: [DISCUSS] Name of the FlexJS Fork

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,

Re: [DISCUSS] Name of the FlexJS Fork

 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

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

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

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

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

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

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

RE: [DISCUSS] Name of the FlexJS Fork

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

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

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 -

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

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 -

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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.

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

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

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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

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

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 -

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

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

Re: [DISCUSS] Name of the FlexJS Fork

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, >

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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

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

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"

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

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

Re: [DISCUSS] Name of the FlexJS Fork

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

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

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 >

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

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

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

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

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

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 -

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

+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"

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

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

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

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

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

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,

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

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. >

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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