Hi Dave, I thank that's fine, but If I'm not missing something, we can have a more friendly and easy domain that points to royale.apache.org,
Or even, we could setup an external website that leverages a good design that will end referring to royale.apache.org for various resources (code, wiki, docs, releases and so on) (I'm talking of course about the marketing of the project) Right? 2017-09-14 1:43 GMT+02:00 Dave Fisher <dave2w...@comcast.net>: > Hey Carlos, > > At Apache we are required to use project.apache.org form. So we would be > royale.apache.org/. > > Regards, > Dave > > Sent from my iPhone > > > On Sep 13, 2017, at 4:03 PM, Carlos Rovira < > carlos.rov...@codeoscopic.com> wrote: > > > > Hi, > > > > I think we should target as well available domains. You could have a > great > > name but not a companion domain that would be ok with it. > > > > When choosing a domain for ROYALE, we should have some options (first > > consider that .com is almost impossible today...only very strange names > > could have some opportunity and this is not the case, and not what we > > really want, so: > > > > 1) Use "royaleframework.XXX" (for example Spring Framework did just that > > http://www.springframework.com), but I don't like that solution, in fact > > they changed to what I think is better: > > > > 2) "royale.XXX" where XXX could be for example ".io", today ".io" is very > > normal in technology and is shorter. For the previous example they now > are: > > http://spring.io/ > > > > (again we should see what other respected and great frameworks did in the > > past and copy what we think is ok for us) > > > > So if we choose 2) We will have "royale.io", that for me is a very > > attractive domain. > > > > Regarding Alex and Dave research, we should think that ROYALE is a word > > that we'll end having lots of referrals to many other things. Imagine you > > want to name the project "CHEESE"...maybe here you should have to put > some > > other word to limit collisions (PURPLECHEESE, or whatever...) > > > > Regarding Macromedia Royale, I think it was an internal codename that > never > > was registered and the normal rule is put efforts in protect the final > > branding name, so we should not be worried about that in case this name > is > > ok for us. > > > > > > > > > > 2017-09-14 0:46 GMT+02:00 Alex Harui <aha...@adobe.com.invalid>: > > > >> Here are the guts of what would I would put in a PODLINGNAMESEARCH for > >> Royale. I don't see anything blocking, but I don't know if there is an > >> issue with using former Macromedia project code names. It doesn't > appear > >> that Macromedia registered it. > >> > >> Interestingly the first definition for "Royale" is not at all what I > >> thought [1]. It is for food. But it certainly hasn't stopped lots of > >> folks from using the second definition in product names [2]. > >> > >> EVIDENCE OF OPEN SOURCE ADOPTION > >> > >> A search on Github for "Royale" returns 705 repositories. The first two > >> pages are results seem to have lots of references to a game called > "Clash > >> Royale" and "Battle Royale". There is one repo for a "React-esque > >> framework for Javascript" > >> > >> There is a Royale project on SourceForge, but it looks empty [4] and a > >> "Royale OS" project that is attempting to be an alternative to Windows > >> [5]. The link to the website for Royale OS is broken. > >> > >> EVIDENCE OF REGISTRATION > >> > >> Royale has been registered multiple times: > >> 1) Restaurant and bar services > >> 2) Entertainment > >> 3) Paints > >> 4) Dinnerware > >> 5) Wine > >> 6) Backpacks > >> > >> Royale Software was registered but is now deemed "DEAD". > >> > >> EVIDENCE OF USE ON WORLD WIDE WEB > >> > >> Google search turned up an "OSRoyale" project [6] and a search for > "Royale > >> Software" turned up [7]. In addition there are products with "Royal" > >> instead of "Royale" like [8] and [9]. > >> > >> Also Macromedia used "Royale" as the code name for Flex. A search for > >> "Macromedia Royale" turns up some hits. > >> > >> [1] http://www.dictionary.com/browse/royale?s=t > >> [2] https://en.wikipedia.org/wiki/Royale > >> [3] https://github.com/search?p=2&q=Royale&type=Repositories&utf8=✓ > >> [4] https://sourceforge.net/projects/royale/ > >> [5] https://sourceforge.net/projects/royaleos/?source=directory > >> [6] https://www.osroyale.com > >> [7] http://pmdtec.com/picofamily/blog/tag/royale/ > >> [8] http://linux-royal.net > >> [9] https://www.royalapplications.com/ts/mac/features > >> > >> On 9/13/17, 2:57 PM, "omup...@gmail.com on behalf of OmPrakash > Muppirala" > >> <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: > >> > >>> We could always structure the VOTE like this: > >>> > >>> 1. Royale > >>> 2. XXX > >>> 3. YYY > >>> 4. FlexJS > >>> > >>> One vote should answer both questions. > >>> > >>> Thanks, > >>> Om > >>> > >>> On Wed, Sep 13, 2017 at 2:52 PM, Piotr Zarzycki > >>> <piotrzarzyck...@gmail.com> > >>> wrote: > >>> > >>>> On the other hand, we have rather majority of voices for do not change > >>>> the > >>>> name and Alex is right. - I'm seeing more people asking for help with > >>>> porting. - We may disappear in the sea of frameworks with changed > >>>> name... > >>>> > >>>> Maybe better have solid framework and invest in current name still > with > >>>> nice branding. I'm puzzled, so definitely I will give myself at least > >>>> one > >>>> day more before VOTE. > >>>> > >>>> Piotr > >>>> > >>>> > >>>> > >>>> 2017-09-13 23:31 GMT+02:00 Piotr Zarzycki <piotrzarzyck...@gmail.com > >: > >>>> > >>>>> +1 for Dave's proposition on starting the VOTE for name change. > >>>>> > >>>>> I would like to also add that Carlos's proposition for help to build > >>>> new > >>>>> brand triggers me. Peter helped also do understand that we can always > >>>> state > >>>>> from where we have come and what was our story. > >>>>> > >>>>> I'm going to change my mind on name changing and pickup "Royale" as > >>>> the > >>>>> most powerful for the new one. - The main question is can we use it > >>>> since > >>>>> it was code name of Macromedia Framework ? > >>>>> > >>>>> Thanks, > >>>>> Piotr > >>>>> > >>>>> 2017-09-13 22:59 GMT+02:00 Dave Fisher <dave2w...@comcast.net>: > >>>>> > >>>>>> Hi - > >>>>>> > >>>>>> Sent from my iPhone > >>>>>> > >>>>>>> On Sep 13, 2017, at 1:40 PM, Harbs <harbs.li...@gmail.com> wrote: > >>>>>>> > >>>>>>> Carlos’ argument carries weight to me. > >>>>>>> > >>>>>>> If a new name will help motivate him in terms of marketing it, > >>>> that’s > >>>>>> value I can recognize. > >>>>>>> > >>>>>>> The name is not as important to me as motivating people to be > >>>> involved > >>>>>> in the project. We can build whatever messages we want around the > >>>> name. > >>>>>>> > >>>>>>> Carlos clearly feels more passionate about his position than I do > >>>> about > >>>>>> mine. > >>>>>>> > >>>>>>> A hesitation I have about picking a new name is that I don’t want > >>>> to > >>>>>> delay the board’s decision on the new PMC. If we go for a new name > >>>> can > >>>> we > >>>>>> try and pick one quickly? > >>>>>> > >>>>>> Let's start the FlexJS yes or no vote tonight or tomorrow morning. > >>>>>> > >>>>>> In parallel we can discuss other names if a new name is the result > >>>> then > >>>>>> we can immediately start the next vote. We have just enough time. > >>>>>> > >>>>>> Regards, > >>>>>> Dave > >>>>>> > >>>>>> > >>>>>>> > >>>>>>> Harbs > >>>>>>> > >>>>>>>> On Sep 13, 2017, at 9:20 PM, Carlos Rovira < > >>>>>> carlos.rov...@codeoscopic.com> wrote: > >>>>>>>> > >>>>>>>> Hi all, > >>>>>>>> > >>>>>>>> I'm putting some efforts here since I think this is really > >>>> important > >>>>>> for > >>>>>>>> all of us and for our beloved FlexJS project. > >>>>>>>> > >>>>>>>> Name, website and all the visuals behind it matters....and is > >>>>>> important in > >>>>>>>> a way many of us in this community maybe can't imagine. If we > >>>> don't > >>>>>> get a > >>>>>>>> fresh and compelling name and a clean and beautiful site where we > >>>>>> explain > >>>>>>>> all the great things our technology can do, we are losing our > >>>> time, > >>>>>> since > >>>>>>>> this project will end with the bulk of the others xxxJS projects, > >>>> and > >>>>>>>> that's even horrible when our tech could be used for things other > >>>> than > >>>>>> JS!! > >>>>>>>> (If we want in future years to make it possible). > >>>>>>>> > >>>>>>>> @Alex: I Think we can't have a PROJECT name != of PRODUCT name for > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> > >>>>> 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.linke > >>>> din.com%2Fpiotrzarzycki&data=02%7C01%7C% > 7Cf59f94a5f94b4a692a8c08d4faf2 > >> 905 > >>>> 2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > >> 7C636409367090833789&sdata=3 > >>>> q%2B6JEmcUGp14HR4edfufpFv0mfglyQfLksYuWeDKUE%3D&reserved=0 > >>>>> > >>>> <https://na01.safelinks.protection.outlook.com/?url= > >> https%3A%2F%2Fpl.link > >>>> edin.com%2Fin%2Fpiotr-zarzycki-92a53552&data=02% > >> 7C01%7C%7Cf59f94a5f94b4a6 > >>>> 92a8c08d4faf29052%7Cfa7b1b5a7b34438794aed2c178de > >> cee1%7C0%7C0%7C6364093670 > >>>> 90833789&sdata=U%2BWhQzyHpMYYXTa%2B3kji8fM8Q% > >> 2Fn6iYseitRusvgsM8E%3D&reser > >>>> ved=0> > >>>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> > >>>> Piotr Zarzycki > >>>> > >>>> mobile: +48 880 859 557 > >>>> skype: zarzycki10 > >>>> > >>>> LinkedIn: > >>>> https://na01.safelinks.protection.outlook.com/?url= > >> http%3A%2F%2Fwww.linke > >>>> din.com%2Fpiotrzarzycki&data=02%7C01%7C% > 7Cf59f94a5f94b4a692a8c08d4faf2 > >> 905 > >>>> 2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > >> 7C636409367090833789&sdata=3 > >>>> q%2B6JEmcUGp14HR4edfufpFv0mfglyQfLksYuWeDKUE%3D&reserved=0 > >>>> > >>>> <https://na01.safelinks.protection.outlook.com/?url= > >> https%3A%2F%2Fpl.link > >>>> edin.com%2Fin%2Fpiotr-zarzycki-92a53552&data=02% > >> 7C01%7C%7Cf59f94a5f94b4a6 > >>>> 92a8c08d4faf29052%7Cfa7b1b5a7b34438794aed2c178de > >> cee1%7C0%7C0%7C6364093670 > >>>> 90833789&sdata=U%2BWhQzyHpMYYXTa%2B3kji8fM8Q% > >> 2Fn6iYseitRusvgsM8E%3D&reser > >>>> ved=0> > >>>> > >> > >> > > > > > > -- > > > > <http://www.codeoscopic.com> > > > > Carlos Rovira > > > > Director General > > > > M: +34 607 22 60 05 > > > > http://www.codeoscopic.com > > > > http://www.avant2.es > > > > > > Conocenos en 1 minuto! <https://youtu.be/P2IEAYDG5HU> > > > > > > Este mensaje se dirige exclusivamente a su destinatario y puede contener > > información privilegiada o confidencial. Si ha recibido este mensaje por > > error, le rogamos que nos lo comunique inmediatamente por esta misma vía > y > > proceda a su destrucción. > > > > De la vigente Ley Orgánica de Protección de Datos (15/1999), le > comunicamos > > que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC > > S.A. La finalidad de dicho tratamiento es facilitar la prestación del > > servicio o información solicitados, teniendo usted derecho de acceso, > > rectificación, cancelación y oposición de sus datos dirigiéndose a > nuestras > > oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación > > necesaria. > > -- <http://www.codeoscopic.com> Carlos Rovira Director General M: +34 607 22 60 05 http://www.codeoscopic.com http://www.avant2.es Conocenos en 1 minuto! <https://youtu.be/P2IEAYDG5HU> Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la prestación del servicio o información solicitados, teniendo usted derecho de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación necesaria.
