Re: [DISCUSS] Name of the FlexJS Fork

Hi Peter, voting was closed and now project is called "Royale" (see vote results thread) Thanks for share your thoughts! Carlos 2017-09-20 9:30 GMT+02:00 Peter Ginneberge : > > I kept repeating "Bead" over and over in my head and all of a sudden > turned it into

Re: [DISCUSS] Name of the FlexJS Fork

I kept repeating "Bead" over and over in my head and all of a sudden turned it into "Beadle", which I think has a much nicer ring to it. Then looked it up and apparently it's an existing word (didn't think it was, but then again, English isn't my native language). Beadle: sometimes spelled

Re: [DISCUSS] Name of the FlexJS Fork

>>>>>> Boja is one name I really dislike. Sorry Piotr > >> > >>>>>> > >> > >>>>>> Also I dont know how to pronounce it. Is it Bo-ha, or boo-ha or > >> > bo-ja, > >> > >>>>> etc? > >> > >>&g

Re: [DISCUSS] Name of the FlexJS Fork

Fbraid=02%7C01%7C%7C2f878032534e4131bec408d4ff9d57 >>aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636414498626680232= >>PFAK5EsVQos6oTHUh%2BRnxie9bFwrJAj0ZKEQCHMP67E%3D=0 >> > > >> > > 2017-09-19 20:38 GMT+02:00 Kessler CTR Mark J < >> mark.kess

Re: [DISCUSS] Name of the FlexJS Fork

arks > > > implications. > > > > > > [1] https://github.com/cristibalan/braid > > > > > > 2017-09-19 20:38 GMT+02:00 Kessler CTR Mark J < > mark.kessler@usmc.mil > > >: > > > > > >> Apache Bob... > > >> > > >

Re: [DISCUSS] Name of the FlexJS Fork

gt; > [1] https://github.com/cristibalan/braid > > > > 2017-09-19 20:38 GMT+02:00 Kessler CTR Mark J <mark.kessler@usmc.mil > >: > > > >> Apache Bob... > >> > >> > >> -Original Message- > >> From: Harbs [mailto:harbs.

Re: [DISCUSS] Name of the FlexJS Fork

Hi Alex, 2017-09-19 20:59 GMT+02:00 Alex Harui : > > That's why I'm concerned about Royale when there is a GitHub project > called Royale that is a "A React-esque framework for Javascript". Think > of it this way. If you did a search on GitHub for our project name and

Re: [DISCUSS] Name of the FlexJS Fork

Message- >> From: Harbs [mailto:harbs.li...@gmail.com] >> Sent: Tuesday, September 19, 2017 2:20 PM >> To: dev@flex.apache.org >> Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork >> >> Ick… >> >> Why do these things have to

Re: [DISCUSS] Name of the FlexJS Fork

Looks like a conflict to me. Regards, Dave > On Sep 19, 2017, at 3:48 PM, Harbs wrote: > > Helix is nice. > > Possible conflict: > http://www.helixsdk.org/ > >> On Sep 19, 2017, at 10:40 PM, OmPrakash Muppirala >>

Re: [DISCUSS] Name of the FlexJS Fork

I swear all the good names are already taken. I think we just need to throw letters into a box and shake them at this point. ‹peter On 9/19/17, 3:48 PM, "Harbs" wrote: >Helix is nice. > >Possible conflict:

Re: [DISCUSS] Name of the FlexJS Fork

Helix is nice. Possible conflict: http://www.helixsdk.org/ > On Sep 19, 2017, at 10:40 PM, OmPrakash Muppirala > wrote: > >> >> > > "Braid" also brings to mind "Helix". I haven't looked to see if there >>> are > any projects that

Re: [DISCUSS] Name of the FlexJS Fork

> > >> > > >> > > "Braid" also brings to mind "Helix". I haven't looked to see if there >> are >> > > any projects that use "Helix" which I'm sure there are. And if so, >> maybe >> > > "Felix" to give a nod back to Flex along with the helix. >> > > >> > > —peter >> > I love Helix. It actually

Re: [DISCUSS] Name of the FlexJS Fork

;>>>>>> wrote: >>>>>>>>> >>>>>>>>> We don't have time for another vote thread. We need to close down >>>>>> the >>>>>>>>> vote tonight or early tomorrow morning. So, if you are ok with

Re: [DISCUSS] Name of the FlexJS Fork

;>> vote for Royale just so we have a name for tomorrow. >>>> >>>> HTH, >>>> -Alex >>>> >>>> On 9/19/17, 11:43 AM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> >> wrote: >>>> >>>>&

Re: [DISCUSS] Name of the FlexJS Fork

e for tomorrow. >>>> >>>> HTH, >>>> -Alex >>>> >>>> On 9/19/17, 11:43 AM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> >> wrote: >>>> >>>>> I checked Braid on github and found

Re: [DISCUSS] Name of the FlexJS Fork

otrzarzyck...@gmail.com> > > wrote: > > >> > > >>> I checked Braid on github and found [1]. It was quite popular - can > we > > >>> just > > >>> grab that name - I still do not understand fully those trademarks > > >>&g

Re: [DISCUSS] Name of the FlexJS Fork

tr Zarzycki" <piotrzarzyck...@gmail.com> > wrote: > >> > >>> I checked Braid on github and found [1]. It was quite popular - can we > >>> just > >>> grab that name - I still do not understand fully those trademarks > >>>

Re: [DISCUSS] Name of the FlexJS Fork

;>> just >>> grab that name - I still do not understand fully those trademarks >>> implications. >>> >>> [1] >>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c >>> o >>> m%2Fcristibalan%2Fbraid=02%7C01%7

Re: [DISCUSS] Name of the FlexJS Fork

>o > >>m%2Fcristibalan%2Fbraid=02%7C01%7C%7C5ebf232812004352ad0108d4ff8e > 4f1 > >>7 > >>%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > 7C636414434060882785=A6 > >>I > >>IL4SNYWP2XFTvOife92gA1t8Km4E%2Fr7QpvQ3B3mI%3D=0 > >> > >>2017-09-1

Re: [DISCUSS] Name of the FlexJS Fork

ad0108d4ff8e4f1 >>7 >>%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636414434060882785=A6 >>I >>IL4SNYWP2XFTvOife92gA1t8Km4E%2Fr7QpvQ3B3mI%3D=0 >> >>2017-09-19 20:38 GMT+02:00 Kessler CTR Mark J >><mark.kessler@usmc.mil>: >> >>> Apache

Re: [DISCUSS] Name of the FlexJS Fork

Tuesday, September 19, 2017 2:20 PM > To: dev@flex.apache.org > Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork > > Ick… > > Why do these things have to be so complicated? ;-) > > Harbs > >> On Sep 19, 2017, at 8:58 PM, Dave Fisher <dave2w...

Re: [DISCUSS] Name of the FlexJS Fork

pache Bob... > > > -Original Message- > From: Harbs [mailto:harbs.li...@gmail.com] > Sent: Tuesday, September 19, 2017 2:20 PM > To: dev@flex.apache.org > Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork > > Ick… > > Why do these things have to be so

Re: [DISCUSS] Name of the FlexJS Fork

Apache Bob... -Original Message- From: Harbs [mailto:harbs.li...@gmail.com] Sent: Tuesday, September 19, 2017 2:20 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork Ick… Why do these things have to be so complicated? ;-) Harbs > On Sep

Re: [DISCUSS] Name of the FlexJS Fork

t;>> FWIW, I think Limbr is another good spelling. >>>>>>>> >>>>>>>>> On Sep 19, 2017, at 7:34 PM, Alex Harui <aha...@adobe.com.INVALID> >>>>>>>> wrote: >>>>>>>>> >>>>>&

Re: [DISCUSS] Name of the FlexJS Fork

>> We don't have time for another vote thread. We need to close down >>>>> the >>>>>>>> vote tonight or early tomorrow morning. So, if you are ok with >>>>> Limber >>>>>>>> (still not clear it will win, please

Re: [DISCUSS] Name of the FlexJS Fork

ok with >>>> Limber >>>>>>> (still not clear it will win, please state objections to using >>> Limbyr >>>>> as >>>>>>> the spelling. It is true a unique spelling stand out from search >>>>>> results, >>>>>>>

Re: [DISCUSS] Name of the FlexJS Fork

ease state objections to using >> Limbyr >>>> as >>>>>> the spelling. It is true a unique spelling stand out from search >>>>> results, >>>>>> but first, you have to remember how to spell it, and my spell >> checker >&g

Re: [DISCUSS] Name of the FlexJS Fork

; -Alex > > > > > > > > > > On 9/19/17, 5:05 AM, "Kessler CTR Mark J" < > mark.kessler@usmc.mil > > > > > > > > wrote: > > > > > > > > > >> If limber wins, a simple discussion thread

Re: [DISCUSS] Name of the FlexJS Fork

tantly changing. > > > > > > > > -Alex > > > > > > > > On 9/19/17, 5:05 AM, "Kessler CTR Mark J" <mark.kessler@usmc.mil > > > > > > wrote: > > > > > > > >> If limber wins, a simple discussion t

Re: [DISCUSS] Name of the FlexJS Fork

; > > > > > On 9/19/17, 5:05 AM, "Kessler CTR Mark J" <mark.kessler@usmc.mil> > > > wrote: > > > > > >> If limber wins, a simple discussion thread should resolve letter > changes > > >> to the name. > > >> > > &

Re: [DISCUSS] Name of the FlexJS Fork

e- > >> From: Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com] > >> Sent: Tuesday, September 19, 2017 4:52 AM > >> To: dev@flex.apache.org > >> Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork > >> > >> Hi, > >> > &

Re: [DISCUSS] Name of the FlexJS Fork

zycki [mailto:piotrzarzyck...@gmail.com] >> Sent: Tuesday, September 19, 2017 4:52 AM >> To: dev@flex.apache.org >> Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork >> >> Hi, >> >> It has advantage of having the name which d

Re: [DISCUSS] Name of the FlexJS Fork

Mark K > >-Original Message- >From: Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com] >Sent: Tuesday, September 19, 2017 4:52 AM >To: dev@flex.apache.org >Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork > >Hi, > >It has advantage of having the nam

Re: [DISCUSS] Name of the FlexJS Fork

Hi Rui, You can vote in our VOTE thread. Community vote is important. Pickup three names, propose yours one. Thanks, Piotr 2017-09-19 16:06 GMT+02:00 Rui Cruz : > I like > > cruzer.io (implies fast robust) > > 2017-09-19 14:50 GMT+01:00 Carlos Rovira

Re: [DISCUSS] Name of the FlexJS Fork

I like cruzer.io (implies fast robust) 2017-09-19 14:50 GMT+01:00 Carlos Rovira : > Hi, > > sorry to not agree with Limbyr (or limber), but the concept and name > doesn't sound good to me. Although I see the intention behind. > > For me a name should be as direct

Re: [DISCUSS] Name of the FlexJS Fork

Consider what Dave mention I agree with Carlos. Although I like Lymbir idea we should not go into that name having such issues. We have still 9 hours of voting and I'm thinking to change my VOTE cause Beads sound to me ok, but it seems to be less powerful. Conversation on users group seems to be

Re: [DISCUSS] Name of the FlexJS Fork

Hi, sorry to not agree with Limbyr (or limber), but the concept and name doesn't sound good to me. Although I see the intention behind. For me a name should be as direct as possible, that substitution of "e" with "y" was something used a decade or so ago to get 2.0 names for the internet, but

Re: [DISCUSS] Name of the FlexJS Fork

I read that as Limb Buyer. As in organ trafficking, Let's not :) Tom On 19/09/17 13:05, Kessler CTR Mark J wrote: to have "Limbyr" - Which I like personally.

Re: [DISCUSS] Name of the FlexJS Fork

Hi - Keep in mind - (1) As an Apache project the URL is limbyr.apache.org (Apple mail auto-correct me to limber) (2) If independent people may hear about limbyr and type in or be auto-corrected to limber.com . We really don’t want anyone in a corporation going to an adult

RE: Re: [DISCUSS] Name of the FlexJS Fork

If limber wins, a simple discussion thread should resolve letter changes to the name. -Mark K -Original Message- From: Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com] Sent: Tuesday, September 19, 2017 4:52 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [DISCUSS] Name

Re: [DISCUSS] Name of the FlexJS Fork

Hi, It has advantage of having the name which do not exist on github. Let say that Limber with win in the voting - We probably have to open another VOTE to have "Limbyr" - Which I like personally. Is it enough that PMCs agreed here with changing Limber to Limbyr here ? Thanks, Piotr

Re: [DISCUSS] Name of the FlexJS Fork

Finding names which have not yet been “taken” is tough… ;-) Unusual spellings also have an advantage in search. I like Limbyr. Harbs > On Sep 19, 2017, at 10:26 AM, Alex Harui wrote: > > I was looking into various spellings of Limber because just about every > name

Re: [DISCUSS] Name of the FlexJS Fork

I was looking into various spellings of Limber because just about every name we came up with is already on GitHub: limber.com is an adult site limber.org is an observatory limber.io is about marketing royale.com is about ticket sales royale.org is about dogs royale.io is owned by

Re: [DISCUSS] Name of the FlexJS Fork

Carlos, You are right, I'm sorry if my tone was to harsh! Too much storm lately around all of this. I hope soon we will have better weather. :) Best Piotr! 2017-09-18 13:26 GMT+02:00 Carlos Rovira : > Hi Piotr, > > I think people could pick "Beads" as one of his

Re: [DISCUSS] Name of the FlexJS Fork

Hi Piotr, I think people could pick "Beads" as one of his options. We're all free to choose whatever we want. But I think this DISCUSS thread is very useful as well to express why this or that option should be considered for people voting Thanks 2017-09-18 11:54 GMT+02:00 Piotr Zarzycki

Re: [DISCUSS] Name of the FlexJS Fork

That's why we have VOTE thread, anyone can express their needs by picking up some options. Encourage everyone for voting! Let's have it done! Thanks, Piotr 2017-09-18 11:48 GMT+02:00 Carlos Rovira : > I agree with Om, that naming a project with one of the features is

Re: [DISCUSS] Name of the FlexJS Fork

I agree with Om, that naming a project with one of the features is not a good strategy in marketing terms. Beads-Strand is a good feature that said a lot about the compositing nature behind it, and something very relevant in FlexJS, but not should be its identifier. There's much more in our

Re: [DISCUSS] Name of the FlexJS Fork

One point of clarification. The Beads concept comes into play only in the FlexJS SDK and not in the Flex Falcon or FalconJX compiler. Some day it could be FalconWebAssemby or FalconIOS. Naming the Apache project as Beads means that we are highlighting only the SDK and not the cross-compilers.

Re: [DISCUSS] Name of the FlexJS Fork

Not sure what are you asking. I should probably use Beads instead Bead in the VOTE. Do you think that list should be updated with Bead -> Beads Strand -> Strands Piotr 2017-09-17 21:38 GMT+02:00 Harbs : > Question: > > In the vote, is it for the exact name? For example

Re: [DISCUSS] Name of the FlexJS Fork

Question: In the vote, is it for the exact name? For example “Beadz” and “Limbre” seem to be much less used than “Beads” and “Limber”. Thanks, Harbs > On Sep 17, 2017, at 6:55 PM, Carlos Rovira > wrote: > > Hi > > I think it would be good to start that vote

Re: [DISCUSS] Name of the FlexJS Fork

Hi I think it would be good to start that vote thread with some possibilities. I think we should put the three most wanted over ten, since is what we should found in some election systems. We get to the final stage the most popular ones to vote. I think if we put ten options we'll end with a

Re: [DISCUSS] Name of the FlexJS Fork

Royale: 710 repos match Royale on Github. One, https://github.com/ian-culleton/royale is a "React-esque framework for Javascript" That is a little close to home... EdB On Sun, Sep 17, 2017 at 7:29 AM, Alex Harui wrote: > A quick "suitable name search" on some other

Re: [DISCUSS] Name of the FlexJS Fork

Hi Piotr, If you can start it that would be great. I’m very limited in time today. Thanks, Harbs > On Sep 17, 2017, at 11:20 AM, Piotr Zarzycki > wrote: > > I can start the VOTE within 12H cause I don't see anything against. If > someone can start earlier that

Re: [DISCUSS] Name of the FlexJS Fork

I can start the VOTE within 12H cause I don't see anything against. If someone can start earlier that would be great. Proposed title: [VOTE] What should be new project name for proposed fork of FlexJS? List Description of VOTE from Harbs. VOTE itself: 1) Name +1 (Binding) 2) Second Proposal

Re: [DISCUSS] Name of the FlexJS Fork

Let's bring together the most mentioned from this thread and start a VOTE by Harbs's system. Let it be max 10 props. Piotr On Sun, Sep 17, 2017, 08:26 Alex Harui wrote: > BOJA also was/is software-related: > https://link.springer.com/article/10.1007/BF00143947 > >

Re: [DISCUSS] Name of the FlexJS Fork

BOJA also was/is software-related: https://link.springer.com/article/10.1007/BF00143947 Again, not a deal-killer. One question that came to mind is whether we'd spend too much time explaining why we called the project BOJA. That got me thinking of it as an acronym as well. Or maybe a new

Re: [DISCUSS] Name of the FlexJS Fork

To be clear, none of my findings are deal killers for the proposed name. BOJA is the stock symbol for Bojangles Inc. A chain of fried chicken restaurants. Wiktionary defined variants of boja [1]. What did you say you thought it meant? Boja has 163 matches on Github, but I didn't see an exact

Re: [DISCUSS] Name of the FlexJS Fork

> On Sep 17, 2017, at 8:29 AM, Alex Harui wrote: > > A quick "suitable name search" on some other candidates: > > Braid: 260 repos match with Braid on Github. There is a project call > BraidApps. Could pose some confusion since we produce apps. > > Strand: 697

Re: [DISCUSS] Name of the FlexJS Fork

A quick "suitable name search" on some other candidates: Braid: 260 repos match with Braid on Github. There is a project call BraidApps. Could pose some confusion since we produce apps. Strand: 697 repos match Strand on Github. First match was https://github.com/MediaMath/strand. It is a

Re: [DISCUSS] Name of the FlexJS Fork

I mentioned STeVe but after reading this [1][2], I withdraw that suggestion as I think STV is intended for choosing multiple from multiple instead of one of multiple. (I did not read all of [2]). My takeaway is that, unless a true majority results, the results of other system can be challenged.

Re: [DISCUSS] Name of the FlexJS Fork

I like this one. Harbs > On Sep 16, 2017, at 11:31 PM, Andrew Wetmore wrote: > > Braid (bunch of strands, right?)

Re: [DISCUSS] Name of the FlexJS Fork

Someone up thread mentioned that Apache STeVe could be used for this. https://steve.apache.org/vote_types.html Thanks, Om On Sep 16, 2017 1:22 PM, "Piotr Zarzycki" wrote: Hi Harbs, Nice idea. It allows picking up for anyone couple of options. Piotr On Sat, Sep

Re: [DISCUSS] Name of the FlexJS Fork

Nsurgent Deliver Carrier Braid (bunch of strands, right?) On Sat, Sep 16, 2017 at 5:28 PM, Andrew Wetmore wrote: > Royale, in my part of the world, is a low-grade line of processed food > products: styrofoam-flavored ice cream, and so on. > > On Sat, Sep 16, 2017 at

Re: [DISCUSS] Name of the FlexJS Fork

Royale, in my part of the world, is a low-grade line of processed food products: styrofoam-flavored ice cream, and so on. On Sat, Sep 16, 2017 at 5:22 PM, Piotr Zarzycki wrote: > Hi Harbs, > > Nice idea. It allows picking up for anyone couple of options. > > Piotr > >

Re: [DISCUSS] Name of the FlexJS Fork

Hi Harbs, Nice idea. It allows picking up for anyone couple of options. Piotr On Sat, Sep 16, 2017, 21:57 Harbs wrote: > I’m not sure why, but Royale does not resonate very well with me. > > Bend Bead and Strand are all good names as far as I’m concerned. > > I

Re: [DISCUSS] Name of the FlexJS Fork

I’m not sure why, but Royale does not resonate very well with me. Bend Bead and Strand are all good names as far as I’m concerned. I personally like Limber/Limbre. I like Boinga in a different way. I think that Böja has a great ring to it. One way I was thinking about a vote was by allowing

Re: Renaming Work (Re: [DISCUSS] Name of the FlexJS Fork)

I did a quick look through licenses and this does not seem to be the problem I thought it might be. I would be glad to help with documentation migration when we get to that point. On Fri, Sep 15, 2017 at 3:20 PM, Alex Harui wrote: > Hi Andrew, > > I think our licenses

Re: Renaming Work (Re: [DISCUSS] Name of the FlexJS Fork)

Hi Andrew, I think our licenses don't mention project or product names since it is all under Apache, but if you have time to help with checking on that we'd certainly appreciate it. Thanks, -Alex On 9/15/17, 10:51 AM, "Andrew Wetmore" wrote: >Would the text of licenses

RE: [DISCUSS] Name of the FlexJS Fork

/s DNF SDK - Definitely Not Flash SDK YAAS SDK - Yet Another ActionScript SDK :P -Mark K -Original Message- From: Alex Harui [mailto:aha...@adobe.com.INVALID] Sent: Friday, September 15, 2017 1:31 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS

Re: Renaming Work (Re: [DISCUSS] Name of the FlexJS Fork)

Would the text of licenses and suchlike fall into the documentation task? That is a task I have done several times with software companies and would be glad to help out with, given that it does not require much code expertise to make sure the sentences are coherent and refer to the current product

Renaming Work (Re: [DISCUSS] Name of the FlexJS Fork)

In this thread, let's see if we can list out what needs to be done to rename the code. I think for the ActionScript code, the steps are: 1) go through each folder in framework/projects and do: git mv src/main/flex src/main/royale git mv src/main/flex/org/apache/flex

RE: Re: [DISCUSS] Name of the FlexJS Fork

> For migration : As a customer, I don't think migration is a real option. I can’t say I agree with that. The business logic is almost seamlessly ported. The UI is more involved but still pretty similar. Also, most examples one sees these days are using the Basic component set. I can

Re: [DISCUSS] Name of the FlexJS Fork

Dave says, and I agree, that if there is more than one candidate, we might need to use a more complicated voting system like STeVe. What other suggestions do you think have been popular enough to make a second candidate? I think FlexJS has been rejected as the project name. If anyone wants to

Re: [DISCUSS] Name of the FlexJS Fork

On Fri, Sep 15, 2017 at 9:45 AM, Piotr Zarzycki wrote: > Definitely the were the most support for Royale. +1 for starting vote > YES/NO. We could express in the VOTE thread that anyone can shot his own > name idea and others can give him +1. > There were several

Re: [DISCUSS] Name of the FlexJS Fork

Definitely the were the most support for Royale. +1 for starting vote YES/NO. We could express in the VOTE thread that anyone can shot his own name idea and others can give him +1. Piotr On Fri, Sep 15, 2017, 18:39 Piotr Zarzycki wrote: > As Alex said I also didn't

Re: [DISCUSS] Name of the FlexJS Fork

As Alex said I also didn't answer for any single email from someone who would like to start from scratch app or even would be new Flex world. We may get such people in the future, but we need to go with path where first target will be ports the old one applications. As for the bad press - 4

Re: [DISCUSS] Name of the FlexJS Fork

Hi Carlos, I agree with Piotr. Retaining your ActionScript business logic instead of the risk of porting it to a less structured language is one of the original premises behind FlexJS. I could be wrong, but I think all of the emails I've answered about FlexJS in the past months are from people

Re: [DISCUSS] Name of the FlexJS Fork

gt;-Original Message- >From: Erik de Bruin [mailto:e...@ixsoftware.nl] >Sent: Thursday, September 14, 2017 1:26 PM >To: dev@flex.apache.org >Subject: Re: [DISCUSS] Name of the FlexJS Fork > >BendForward... > >(just kidding!) > >EdB >

Re: [DISCUSS] Name of the FlexJS Fork

Kessler CTR Mark J" <mark.kessler@usmc.mil> wrote: >I actually spilt some coffee on this one. Lol > >-Mark K > >-Original Message- >From: Erik de Bruin [mailto:e...@ixsoftware.nl] >Sent: Thursday, September 14, 2017 1:26 PM >To: dev@flex.apache.org >Subje

Re: Re: [DISCUSS] Name of the FlexJS Fork

Carlos, Love your passion and share it fully. I cannot fully agree with you that having an old application in Flex people will need to rewrite completely. If they have separated enough good logic - they can put it without to much effort in our framework. - That is huge advantage in my opinion.

Re: Re: [DISCUSS] Name of the FlexJS Fork

Hi, I'm with Om and others that one of the results we pursue with this renaming is to avoid the "Flex" name. We talked about the problems we have today with clients when "Flex" is put in a discussion. You pay in terms of credibility to your client. For migration : As a customer, I don't think

RE: Re: [DISCUSS] Name of the FlexJS Fork

I wanted to throw in a couple words / names to see if they "spark" anything. Arise Dawn Raise / Rise Dimension Facet Morph Poly Strand Derive Drive Quest Journey Fortune Prospect Trend -Mark K

RE: Re: [DISCUSS] Name of the FlexJS Fork

I actually spilt some coffee on this one. Lol -Mark K -Original Message- From: Erik de Bruin [mailto:e...@ixsoftware.nl] Sent: Thursday, September 14, 2017 1:26 PM To: dev@flex.apache.org Subject: Re: [DISCUSS] Name of the FlexJS Fork BendForward... (just kidding!) EdB

Re: [DISCUSS] Name of the FlexJS Fork

Could we try to summarize all name proposals in order to build a single post that contains all candidates (project names) before voting? I think it's not so easy to extract all naming ideas from the different threads/posts, I just remember a few. What do you think of just creating a list of

Re: [DISCUSS] Name of the FlexJS Fork

Harbs, Agree to start another vote simultaneously. We have gathered proposition in this email chain, if you could get all of them. VOTE could look like that: +1 (Name from the list) +1 (My proposition) Does this sound ok ? I'm looking into the code what would be the impact changing all the

Re: [DISCUSS] Name of the FlexJS Fork

Another idea to get out the naming dilemma could be to find a name for the new project that still contains 'flex' but don't let you think of flex when you read it the first time, e.g.: ... Inflexion Flexor Flexure ... Just a Scrabble exercise... ;-) So people might be less confused if they find

Re: [DISCUSS] Name of the FlexJS Fork

I agree. Let’s finish the vote on the project name and we can discuss the product (or products) name(s) later. I think we should start the vote on the new name options. I’m not sure what the best format of such a vote should be. We need a culled list of options and way of tallying up

Re: [DISCUSS] Name of the FlexJS Fork

Hi, This was posted by Chris at the [VOTE] thread >and I know what getting rid of "flex" everywhere inside the project would mean regarding refactoring and >tool support. I thought that for now we just vote for a new project name in order to get rid of the word 'Flex' within the Apache project

Re: [DISCUSS] Name of the FlexJS Fork

I'm willing to change my VOTE to Yes if there will be no help from Carlos if we will have Project Name: Royale, but ship product name: FlexJS. Sorry but we really have to have real help if it is even going to happen. Thanks, Piotr 2017-09-15 8:36 GMT+02:00 Olaf Krueger : >

Re: [DISCUSS] Name of the FlexJS Fork

It may not be the same bits. I think it would be two different packages. There might be different defaults, there is no need for Flash Builder support in the product that isn't called FlexJS so we may not ship those files or mention Flash Builder in the doc. -Alex On 9/14/17, 11:01 PM, "Harbs"

Re: [DISCUSS] Name of the FlexJS Fork

So same product but marketed with two different names? Kind of odd, but an interesting approach. It might have merit. I’d like to sit on this idea. I’m not yet sure how I feel about it. Harbs > On Sep 15, 2017, at 3:04 AM, Alex Harui wrote: > > This is why I

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

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

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

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

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

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

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

  1   2   >