I would like some thoughts on a related question, but first some context:

IMO, it would help to continue to develop and ship a product called Apache
FlexJS right now to draw in migrating Flex folks.  And maybe some day,
we'll ship a product that is more targeted to folks writing new JS apps
and maybe even target runtimes other than JS, and that might have a name
that doesn't have Flex in it.  So, the _project_ could be called something
else, but it seems odd for there to be an Apache Flex project and an
Apache XX project that ships an Apache FlexJS product.

So my question is: How impactful the project name is compared to the
product name?  I'm not sure I can recite the project/manufacturer names
behind many products but most are the same at Apache.

So, if someone thinks of a great project name that can encompass these
possibilities in our future and Apache authorities won't object to using
FlexJS for a product in a project with a different name, I would be in
favor of the new name, but if project names aren't as impactful as product
names, I'd just lean towards sticking with FlexJS as the project name for
now just so we can get the proposal decided on in the September 20 board
meeting and not have to wait more.

Thoughts?
-Alex

On 9/11/17, 9:35 PM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> wrote:

>Hi Dave,
>
>I believe that FlexJS is the right name. We have gained some recognition
>and visibility among people and companies. I don't believe that we are
>really at the beginning anymore.
>
>Our main first customers are companies who would like to rewrite their
>apps
>from Flex, so this connection is something really good.
>If majority which response to this thread would like to change the name I
>will not fight. Keep in mind that we really would like to have the project
>split - I believe that is the most important to us.
>
>Thanks,
>Piotr
>
>2017-09-12 3:01 GMT+02:00 Dave Fisher <dave2w...@comcast.net>:
>
>> Hi -
>>
>> In discussions on the Board and Private list about the proposal voted
>>on a
>> few weeks ago to fork FlexJS it was pointed out that it would good to
>> discuss if a new name should be attached to the forked project.
>>
>> There are one or two propositions to discuss.
>>
>> (1) FlexJS - is this distinct enough and will the historical connection
>>to
>> Adobe/Apache Flex and Flash help or hinder the forked project’s future?
>>
>> Please provide arguments in any direction.
>>
>> (2) If a change is the outcome then we need to discuss and accumulate
>> reasonable names. Determine what is suitable by checking for other uses
>>of
>> these names. If there are multiple choices available then we should
>>vote.
>>
>> A discussion of possible names can go in parallel to the discussion
>>about
>> keeping FlexJS.
>>
>> This discussion needs to proceed quickly if we want to have an open
>> process in advance of the next ASF Board meeting.
>>
>> Regards,
>> Dave
>>
>
>
>
>-- 
>
>Piotr Zarzycki
>
>mobile: +48 880 859 557 <+48%20880%20859%20557>
>skype: zarzycki10
>
>LinkedIn: 
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linked
>in.com%2Fpiotrzarzycki&data=02%7C01%7C%7C9e4bacb6b08a4923de8108d4f997b9a7%
>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636407877434499520&sdata=Nhht
>Kaf9RlzE9cCdJ3WErVGfHVFXsdQX%2BK48hw0Der8%3D&reserved=0
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.linke
>din.com%2Fin%2Fpiotr-zarzycki-92a53552&data=02%7C01%7C%7C9e4bacb6b08a4923d
>e8108d4f997b9a7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364078774344
>99520&sdata=el1sClOn82J2rnnm4N01Te8Z5bPylMriHy%2Fdp0%2Budd0%3D&reserved=0>

Reply via email to