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

2017-09-15 Thread Alex Harui
Hi Rui, Are you not allowed to consider 'beta' frameworks? That's an interesting data point. The supposed advantage of working with open source at Apache is that you can directly influence the development of the code including stabilizing the parts you need. Thanks, -Alex On 9/15/17, 6:06 AM,

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

2017-09-15 Thread Chris Martin
Yes - binding Sent from Mail for Windows 10 From: Dave Fisher Sent: Thursday, September 14, 2017 8:37 AM To: dev@flex.apache.org Subject: [VOTE] Should the Project Name of the Proposed Fork

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

2017-09-15 Thread Carlos Rovira
No (Binding) 2017-09-15 15:06 GMT+02:00 Rui Cruz : > I think the name doesn't really matter.. all I want is a solid trustable > framework.. if it uses as3 instead of typescript? better than... lately > I've been porting a complete app from as3 to typescript (all I

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

2017-09-15 Thread Rui Cruz
I think the name doesn't really matter.. all I want is a solid trustable framework.. if it uses as3 instead of typescript? better than... lately I've been porting a complete app from as3 to typescript (all I wanted is that FlexJS had a stable release no matter the name..) my 2 cents 2017-09-15

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

2017-09-15 Thread Kessler CTR Mark J
No (binding) The project name should not contain Flex or JS. The flex change because it’s separating the name and the JS because we do more than JS. -Mark K -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Thursday, September 14, 2017 11:37 AM To:

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

2017-09-15 Thread Justin Mclean
Hi, I can see there good reasons for a name change and also a good number for not changing the name. I wouldn’t underestimate the effort needed to change the name and the impact this would have on current users. It’s not an easy to decide but I’m more on the yes side than no side but it’s not

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

2017-09-15 Thread Christofer Dutz
I really feel silly about this seems I'm the only one up to now. But as I do tend to think the name FlexJS is a good name and I know what getting rid of "flex" everywhere inside the project would mean regarding refactoring and tool support. Yes (Binding) Chris On 2017-09-14 17:37, Dave

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

2017-09-14 Thread 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 -

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

2017-09-14 Thread 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"

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

2017-09-14 Thread 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

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

2017-09-14 Thread 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"

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

2017-09-14 Thread 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 -

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

2017-09-14 Thread 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 >

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

2017-09-14 Thread 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 -

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

2017-09-14 Thread 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 -

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

2017-09-14 Thread 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