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

[Andrew Wetmore]

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 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 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 name.
> >
> >On Fri, Sep 15, 2017 at 2:41 PM, Alex Harui 
> >wrote:
> >
> >> 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 src/main/flex/org/apache/royale
> >>
> >> 2) from the root of the repo:
> >>find . -name *.as -exec sed -i *.bak
> >> 's/org\.apache\.flex/org\.apache\.royale/g' {} \;
> >>find . -name *.xml -exec sed -i *.bak
> >> 's/org\.apache\.flex/org\.apache\.royale/g' {} \;
> >>find . -name *.xml -exec sed -i *.bak
> >> 's/src\/main\/flex/src\/main\/royale/g' {} \;
> >>find . -name *.xml -exec sed -i *.bak
> >> 's/org\/apache\/flex/org\/apache\/royale/g' {} \;
> >>find . -name *.bak -delete
> >>
> >> What else is needed?  I think the hard/boring part is dealing with
> >> documentation.  We have to go through:
> >> Wiki
> >> ASDoc
> >> LICENSE
> >> README
> >> RELEASE_NOTES
> >> NOTICE
> >>
> >> And find/replace FlexJS and Flex and review each change as we may
> >> reference regular Flex and are likely to still have a product called
> >> FlexJS.
> >>
> >>
> >> Thoughts?
> >> -Alex
> >>
> >>
> >> On 9/15/17, 7:46 AM, "Piotr Zarzycki" 
> wrote:
> >>
> >> >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.
> >> >
> >> >Voting is going well on renaming. We have enough voices. Even if I
> >>change
> >> >my vote it is still pass with renaming.
> >> >
> >> >The question is - what's with code rename? Can we stay as is? -
> >> >
> >> >I think someone should start vote with all name proposition. I don't
> >>have
> >> >capacity within next 24 hours.
> >> >
> >> >Piotr
> >> >
> >> >On Fri, Sep 15, 2017, 16:21 Carlos Rovira
> >>
> >> >wrote:
> >> >
> >> >> 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 migration is a real
> >>option.
> >> >> FlexJS impose a very different code so almost all must be rewritten.
> >>You
> >> >> only can think in maintain your languages (AS3/MXML) and environments
> >> >>(FB,
> >> >> IDEA,...), so for me there's no much room there to discuss. I must
> >>say
> >> >>that
> >> >> nowadays people like us considering to migrate would consider other
> >> >>actual
> >> >> techs like Angular or React since the cost is similar and they get
> >>the
> >> >> popular framework in 2017.
> >> >>
> >> >> I see this renaming as a way to rebrand all our project and present
> >>it
> >> >>to
> >> >> the world with new visuals and marketing. And try to compete in the
> >>same
> >> >> terms they do. Same kind of name, same kind of website, and so on...
> >> >>
> >> >> About Alex proposal to make different packages I think it could work,
> >> >>but
> >> >> for me that would be a plan after rename, rebranding and website
> >> >>creation.
> >> >> We can have it in mind for next steps after that. For me we need the
> >> >>same
> >> >> top name for product and project, and then we can release a package
> >>for
> >> >> people wanting to migrate called "apache XXX FlexJS" or something.
> >>But
> >> >> consider that to make that real we will need people interested in
> >>make
> >> >>such
> >> >> package and work for it. And consider how many people will be
> >>planing to
> >> >> migrate from Flex and will find that FlexJS is completely different
> >>and
> >> >> they can do it easily.
> >> >>
> >> >> @Piotr, my plans 

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

[Alex Harui]

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 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 name.
>
>On Fri, Sep 15, 2017 at 2:41 PM, Alex Harui 
>wrote:
>
>> 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 src/main/flex/org/apache/royale
>>
>> 2) from the root of the repo:
>>find . -name *.as -exec sed -i *.bak
>> 's/org\.apache\.flex/org\.apache\.royale/g' {} \;
>>find . -name *.xml -exec sed -i *.bak
>> 's/org\.apache\.flex/org\.apache\.royale/g' {} \;
>>find . -name *.xml -exec sed -i *.bak
>> 's/src\/main\/flex/src\/main\/royale/g' {} \;
>>find . -name *.xml -exec sed -i *.bak
>> 's/org\/apache\/flex/org\/apache\/royale/g' {} \;
>>find . -name *.bak -delete
>>
>> What else is needed?  I think the hard/boring part is dealing with
>> documentation.  We have to go through:
>> Wiki
>> ASDoc
>> LICENSE
>> README
>> RELEASE_NOTES
>> NOTICE
>>
>> And find/replace FlexJS and Flex and review each change as we may
>> reference regular Flex and are likely to still have a product called
>> FlexJS.
>>
>>
>> Thoughts?
>> -Alex
>>
>>
>> On 9/15/17, 7:46 AM, "Piotr Zarzycki"  wrote:
>>
>> >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.
>> >
>> >Voting is going well on renaming. We have enough voices. Even if I
>>change
>> >my vote it is still pass with renaming.
>> >
>> >The question is - what's with code rename? Can we stay as is? -
>> >
>> >I think someone should start vote with all name proposition. I don't
>>have
>> >capacity within next 24 hours.
>> >
>> >Piotr
>> >
>> >On Fri, Sep 15, 2017, 16:21 Carlos Rovira
>>
>> >wrote:
>> >
>> >> 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 migration is a real
>>option.
>> >> FlexJS impose a very different code so almost all must be rewritten.
>>You
>> >> only can think in maintain your languages (AS3/MXML) and environments
>> >>(FB,
>> >> IDEA,...), so for me there's no much room there to discuss. I must
>>say
>> >>that
>> >> nowadays people like us considering to migrate would consider other
>> >>actual
>> >> techs like Angular or React since the cost is similar and they get
>>the
>> >> popular framework in 2017.
>> >>
>> >> I see this renaming as a way to rebrand all our project and present
>>it
>> >>to
>> >> the world with new visuals and marketing. And try to compete in the
>>same
>> >> terms they do. Same kind of name, same kind of website, and so on...
>> >>
>> >> About Alex proposal to make different packages I think it could work,
>> >>but
>> >> for me that would be a plan after rename, rebranding and website
>> >>creation.
>> >> We can have it in mind for next steps after that. For me we need the
>> >>same
>> >> top name for product and project, and then we can release a package
>>for
>> >> people wanting to migrate called "apache XXX FlexJS" or something.
>>But
>> >> consider that to make that real we will need people interested in
>>make
>> >>such
>> >> package and work for it. And consider how many people will be
>>planing to
>> >> migrate from Flex and will find that FlexJS is completely different
>>and
>> >> they can do it easily.
>> >>
>> >> @Piotr, my plans will be to work (if people wants me on that) on:
>> >>website,
>> >> logo design for me the motivation to work in that things is to
>>get a
>> >> name that will make me think we can reach our goals, since if I don't
>> >> believe in a name will be complicated to give us a good work.
>> >> Far beyond that I always want to put work on the visuals of a
>>component
>> >> design, I think we need that as we need the website and new name.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> 2017-09-15 13:17 GMT+02:00 Kessler CTR Mark J
>> 

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

[Andrew Wetmore]

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

On Fri, Sep 15, 2017 at 2:41 PM, Alex Harui 
wrote:

> 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 src/main/flex/org/apache/royale
>
> 2) from the root of the repo:
>find . -name *.as -exec sed -i *.bak
> 's/org\.apache\.flex/org\.apache\.royale/g' {} \;
>find . -name *.xml -exec sed -i *.bak
> 's/org\.apache\.flex/org\.apache\.royale/g' {} \;
>find . -name *.xml -exec sed -i *.bak
> 's/src\/main\/flex/src\/main\/royale/g' {} \;
>find . -name *.xml -exec sed -i *.bak
> 's/org\/apache\/flex/org\/apache\/royale/g' {} \;
>find . -name *.bak -delete
>
> What else is needed?  I think the hard/boring part is dealing with
> documentation.  We have to go through:
> Wiki
> ASDoc
> LICENSE
> README
> RELEASE_NOTES
> NOTICE
>
> And find/replace FlexJS and Flex and review each change as we may
> reference regular Flex and are likely to still have a product called
> FlexJS.
>
>
> Thoughts?
> -Alex
>
>
> On 9/15/17, 7:46 AM, "Piotr Zarzycki"  wrote:
>
> >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.
> >
> >Voting is going well on renaming. We have enough voices. Even if I change
> >my vote it is still pass with renaming.
> >
> >The question is - what's with code rename? Can we stay as is? -
> >
> >I think someone should start vote with all name proposition. I don't have
> >capacity within next 24 hours.
> >
> >Piotr
> >
> >On Fri, Sep 15, 2017, 16:21 Carlos Rovira 
> >wrote:
> >
> >> 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 migration is a real option.
> >> FlexJS impose a very different code so almost all must be rewritten. You
> >> only can think in maintain your languages (AS3/MXML) and environments
> >>(FB,
> >> IDEA,...), so for me there's no much room there to discuss. I must say
> >>that
> >> nowadays people like us considering to migrate would consider other
> >>actual
> >> techs like Angular or React since the cost is similar and they get the
> >> popular framework in 2017.
> >>
> >> I see this renaming as a way to rebrand all our project and present it
> >>to
> >> the world with new visuals and marketing. And try to compete in the same
> >> terms they do. Same kind of name, same kind of website, and so on...
> >>
> >> About Alex proposal to make different packages I think it could work,
> >>but
> >> for me that would be a plan after rename, rebranding and website
> >>creation.
> >> We can have it in mind for next steps after that. For me we need the
> >>same
> >> top name for product and project, and then we can release a package for
> >> people wanting to migrate called "apache XXX FlexJS" or something. But
> >> consider that to make that real we will need people interested in make
> >>such
> >> package and work for it. And consider how many people will be planing to
> >> migrate from Flex and will find that FlexJS is completely different and
> >> they can do it easily.
> >>
> >> @Piotr, my plans will be to work (if people wants me on that) on:
> >>website,
> >> logo design for me the motivation to work in that things is to get a
> >> name that will make me think we can reach our goals, since if I don't
> >> believe in a name will be complicated to give us a good work.
> >> Far beyond that I always want to put work on the visuals of a component
> >> design, I think we need that as we need the website and new name.
> >>
> >>
> >>
> >>
> >>
> >> 2017-09-15 13:17 GMT+02:00 Kessler CTR Mark J
> >>:
> >>
> >> > 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
> >> >
> >> >
> >>
> >>
> >> --

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

[Alex Harui]

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 src/main/flex/org/apache/royale

2) from the root of the repo:
   find . -name *.as -exec sed -i *.bak
's/org\.apache\.flex/org\.apache\.royale/g' {} \;
   find . -name *.xml -exec sed -i *.bak
's/org\.apache\.flex/org\.apache\.royale/g' {} \;
   find . -name *.xml -exec sed -i *.bak
's/src\/main\/flex/src\/main\/royale/g' {} \;
   find . -name *.xml -exec sed -i *.bak
's/org\/apache\/flex/org\/apache\/royale/g' {} \;
   find . -name *.bak -delete

What else is needed?  I think the hard/boring part is dealing with
documentation.  We have to go through:
Wiki
ASDoc
LICENSE
README
RELEASE_NOTES
NOTICE

And find/replace FlexJS and Flex and review each change as we may
reference regular Flex and are likely to still have a product called
FlexJS.


Thoughts?
-Alex


On 9/15/17, 7:46 AM, "Piotr Zarzycki"  wrote:

>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.
>
>Voting is going well on renaming. We have enough voices. Even if I change
>my vote it is still pass with renaming.
>
>The question is - what's with code rename? Can we stay as is? -
>
>I think someone should start vote with all name proposition. I don't have
>capacity within next 24 hours.
>
>Piotr
>
>On Fri, Sep 15, 2017, 16:21 Carlos Rovira 
>wrote:
>
>> 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 migration is a real option.
>> FlexJS impose a very different code so almost all must be rewritten. You
>> only can think in maintain your languages (AS3/MXML) and environments
>>(FB,
>> IDEA,...), so for me there's no much room there to discuss. I must say
>>that
>> nowadays people like us considering to migrate would consider other
>>actual
>> techs like Angular or React since the cost is similar and they get the
>> popular framework in 2017.
>>
>> I see this renaming as a way to rebrand all our project and present it
>>to
>> the world with new visuals and marketing. And try to compete in the same
>> terms they do. Same kind of name, same kind of website, and so on...
>>
>> About Alex proposal to make different packages I think it could work,
>>but
>> for me that would be a plan after rename, rebranding and website
>>creation.
>> We can have it in mind for next steps after that. For me we need the
>>same
>> top name for product and project, and then we can release a package for
>> people wanting to migrate called "apache XXX FlexJS" or something. But
>> consider that to make that real we will need people interested in make
>>such
>> package and work for it. And consider how many people will be planing to
>> migrate from Flex and will find that FlexJS is completely different and
>> they can do it easily.
>>
>> @Piotr, my plans will be to work (if people wants me on that) on:
>>website,
>> logo design for me the motivation to work in that things is to get a
>> name that will make me think we can reach our goals, since if I don't
>> believe in a name will be complicated to give us a good work.
>> Far beyond that I always want to put work on the visuals of a component
>> design, I think we need that as we need the website and new name.
>>
>>
>>
>>
>>
>> 2017-09-15 13:17 GMT+02:00 Kessler CTR Mark J
>>:
>>
>> > 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
>> >
>> >
>>
>>
>> --
>>
>> 
>>>oscopic.com=02%7C01%7C%7Ca13ef292891c4ddc929f08d4fc48a9fb%7Cfa7b1b5a
>>7b34438794aed2c178decee1%7C0%7C0%7C636410836399205878=BF6LX6%2BAsTv
>>HXwvnfS8VBEu7CDId3YFt5M%2BqMy6lncM%3D=0>
>>
>> Carlos Rovira
>>
>> Director General
>>
>> M: +34 607 22 60 05
>>
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>>scopic.com=02%7C01%7C%7Ca13ef292891c4ddc929f08d4fc48a9fb%7Cfa7b1b5a7
>>b34438794aed2c178decee1%7C0%7C0%7C636410836399205878=BF6LX6%2BAsTvH
>>XwvnfS8VBEu7CDId3YFt5M%2BqMy6lncM%3D=0
>>
>>