Re: [DISCUSS] Name of the FlexJS Fork

Don't you think guys that is too much references, regarding what Alex found? We are writing in AS - what about emphasis this to RoyaleAS? I'm still not sure yet whether name change convince me.. Piotr On Thu, Sep 14, 2017, 03:35 Jeffry Houser wrote: > Wasn't Royale the

Re: [DISCUSS] Name of the FlexJS Fork

Wasn't Royale the beta name for some version of Flex?  [Flex 2? or was it Flex 1?] On 9/13/2017 6:30 PM, Dave Fisher wrote: Hi - I did a quick suitable name search. Royale might be taken by this individual’s project https://github.com/ian-culleton/royale Otherwise Royale in a TESS search

RE: [DISCUSS] Name of the FlexJS Fork

Yeah no worries Carlos. I’ve been getting the same impression too. I'm totally down to move with what the team decides. I think a name change is fine after 3 years when the “migration link” is less important as most people who want to migrate will have already well underway if not mostly

Re: [DISCUSS] Name of the FlexJS Fork

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,

Re: [DISCUSS] Name of the FlexJS Fork

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 > wrote: > > Hi, > > I think we should target as well available domains.

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: [DISCUSS] Name of the FlexJS Fork

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"

Re: [DISCUSS] Name of the FlexJS Fork

Chris, 2017-09-14 0:37 GMT+02:00 Chris Martin : > > As for the JS being apart of the name, I’m not too worried about it. Since > we’re still in pre 1.0, I’d imagine we’re still working on stabilizing and > getting that conversion to JS to work seamlessly? Once that has

Re: [DISCUSS] Name of the FlexJS Fork

Hi Dave, I think Ian's project should not be a problem since It's like the "Flex" name, it could be as well choose for someone to start a project and nobody could obligate him to change it. But "Apache Flex" is not the same, there will be trademarks problems. If not, the marketing world would

RE: [DISCUSS] Name of the FlexJS Fork

I think the project name and “product” name should match up. I don’t feel what we have is a product. We have a framework that developers will use to produce a product. If the names align then searches will be much easier to follow. That way when we produce “marketing material” for the

Re: [DISCUSS] Name of the FlexJS Fork

Hi - I did a quick suitable name search. Royale might be taken by this individual’s project https://github.com/ian-culleton/royale Otherwise Royale in a TESS search is liquor and beauty products mostly. There is a lot of “Clash Royale" And there is

Re: [DISCUSS] Name of the FlexJS Fork

Hi - We have one alternative name - Royale Are there others that people would like to propose? If not then we can have a simple VOTE between FlexJS and Royale. Regards, Dave > On Sep 13, 2017, at 3:01 PM, Dave Fisher wrote: > > Hi Om, > > I think that dilutes the

Re: [DISCUSS] Name of the FlexJS Fork

Hi Om, I think that dilutes the votes and biases the result towards FlexJS. If we want to go that way then we need a preference ranking and more complicated VOTE counting. Regards, Dave > On Sep 13, 2017, at 2:57 PM, OmPrakash Muppirala wrote: > > We could always

Re: [DISCUSS] Name of the FlexJS Fork

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 wrote: > On the other hand, we have rather majority of voices for do not change the

Re: [DISCUSS] Name of the FlexJS Fork

Dave, Personally I like the idea. Thanks, Piotr 2017-09-13 23:46 GMT+02:00 Dave Fisher : > When we start the VOTE I suggest the following ballot: > > VOTE Should the Project Name of the Proposed Fork be FlexJS? > > [ ] Yes - The forked project should be Apache FlexJS. >

Re: [DISCUSS] Name of the FlexJS Fork

I think the momentum is shifting and the vote will be about some other name. -Alex On 9/13/17, 2:46 PM, "Dave Fisher" wrote: >When we start the VOTE I suggest the following ballot: > >VOTE Should the Project Name of the Proposed Fork be FlexJS? > >[ ] Yes - The forked

Re: [DISCUSS] Name of the FlexJS Fork

When we start the VOTE I suggest the following ballot: 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 care what the forked project

Re: [DISCUSS] Name of the FlexJS Fork

+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

Re: [DISCUSS] Name of the FlexJS Fork

Hi Alex, Let’s slow the roll and see what the people say when the sun is shining on their part of the globe. Regards, Dave > On Sep 13, 2017, at 2:13 PM, Alex Harui wrote: > > Hi Dave, > > I prefer not to rush a vote for FlexJS because I feel like Carlos and Om >

Re: [DISCUSS] Name of the FlexJS Fork

Hi Dave, I prefer not to rush a vote for FlexJS because I feel like Carlos and Om are starting to change some minds. AFAICT, everyone who was in favor of FlexJS as the name was mainly concerned about how migrating Flex customers will find that we have something that can help them. And the

Re: [DISCUSS] Name of the FlexJS Fork

Hi - Sent from my iPhone > On Sep 13, 2017, at 1:40 PM, Harbs 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

Re: [DISCUSS] Name of the FlexJS Fork

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

Re: home.apache.org

Success! Thanks for clarifying that. —peter On 9/13/17, 4:12 PM, "Mark Thomas" wrote: >On 13/09/17 21:00, Peter Ent wrote: >> My LDAP entry at id.apache.org has a OpenPGP Public Key Primary >> Fingerprint set. I assume when I do sftp p...@home.apache.org it looks >>up >>

Re: home.apache.org

On 13/09/17 21:00, Peter Ent wrote: > My LDAP entry at id.apache.org has a OpenPGP Public Key Primary > Fingerprint set. I assume when I do sftp p...@home.apache.org it looks up > 'pent' and sees the OpenPGP fingerprint, goes out to some key server and > fetches whatever it needs. > > And after

Re: home.apache.org

My LDAP entry at id.apache.org has a OpenPGP Public Key Primary Fingerprint set. I assume when I do sftp p...@home.apache.org it looks up 'pent' and sees the OpenPGP fingerprint, goes out to some key server and fetches whatever it needs. And after all this time I still get Permission denied.

Re: [DISCUSS] Name of the FlexJS Fork

On Wed, Sep 13, 2017 at 11:30 AM, Alex Harui wrote: > I believe those who say that trying to sell Flex or FlexJS to a client is > difficult. > Not just to a client, but also for example, co-workers or managers. > > I don't have hard data to back this, but I've always

Re: home.apache.org

On 13/09/17 19:27, Peter Ent wrote: > Thanks, Mark. > > I think I've done all the right stuff. As I started to do it, I began to > remember doing it once before for SSH. I've been waiting awhile and still > get permission denied, so I'll just keep waiting. I'm pretty sure I sent > my key to a

Re: [DISCUSS] Name of the FlexJS Fork

Hi Alex, > On Sep 13, 2017, at 11:30 AM, Alex Harui wrote: > > I believe those who say that trying to sell Flex or FlexJS to a client is > difficult. > > I don't have hard data to back this, but I've always felt that there are > two kinds of Flex customers. One set

Re: [DISCUSS] Name of the FlexJS Fork

I believe those who say that trying to sell Flex or FlexJS to a client is difficult. I don't have hard data to back this, but I've always felt that there are two kinds of Flex customers. One set builds their own applications and thus can choose their own development technologies. Another set

Re: home.apache.org

Thanks, Mark. I think I've done all the right stuff. As I started to do it, I began to remember doing it once before for SSH. I've been waiting awhile and still get permission denied, so I'll just keep waiting. I'm pretty sure I sent my key to a public key server. I'll go out for coffee and I

Re: [DISCUSS] Name of the FlexJS Fork

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 mattersand is important in a way many of us in this community maybe can't imagine. If we don't get a fresh and compelling

RE: [DISCUSS] Name of the FlexJS Fork

On Sep 13, 2017 9:39 AM, "Yishay Weiss" wrote: My main concern was with the JS suffix. If we can create new products without the JS suffix that’s fine with me. On the other hand, if Carlos or someone else feels passionate about a name change and volunteers to deal with

Re: [DISCUSS] Name of the FlexJS Fork

Hi - > On Sep 13, 2017, at 9:39 AM, Yishay Weiss wrote: > > My main concern was with the JS suffix. If we can create new products without > the JS suffix that’s fine with me. > > On the other hand, if Carlos or someone else feels passionate about a name > change and

Re: home.apache.org

On 13/09/2017 18:05, Peter Ent wrote: > I get permission denied (public key). I remember having to set up > something for the old people site (I think) and have been trying to hunt > down the instructions. You should be able to set up your key through id.apache.org You then need to allow enough

Re: home.apache.org

I get permission denied (public key). I remember having to set up something for the old people site (I think) and have been trying to hunt down the instructions. ‹peter On 9/13/17, 12:49 PM, "Alex Harui" wrote: >Should just be: > sftp home.apache.org > >Hope you

Re: home.apache.org

Should just be: sftp home.apache.org Hope you remember your passphrase. -Alex On 9/13/17, 9:16 AM, "Peter Ent" wrote: >Hi, > >Does anyone have the instructions on how to set up access to your >home.apache.org space? I've looked on the apache.org site and all I can

Re: [FlexJS][Installer] Future packaging of FlexJS releases

OK, good to know it works for other people. I've been trying to adjust the build scripts to create this package automatically. The current problem I'm wrestling with is in the Flash Builder launch configs. The launch configs are used by Flash Builder to update a new Flex project with a valid

RE: [DISCUSS] Name of the FlexJS Fork

My main concern was with the JS suffix. If we can create new products without the JS suffix that’s fine with me. On the other hand, if Carlos or someone else feels passionate about a name change and volunteers to deal with the overhead I wouldn’t go against it. From: Alex

home.apache.org

Hi, Does anyone have the instructions on how to set up access to your home.apache.org space? I've looked on the apache.org site and all I can find are instructions about the old people.apache.org. I guess I haven't accessed my home.apache.org since I set up my newer computer. I'm going to

Re: [DISCUSS] Name of the FlexJS Fork

Actually, my question was whether the PROJECT name is more or less important than the PRODUCT name. Mostly, the board/infra doesn't want us to change the PROJECT name. Infra replied that we can create PRODUCTs with names that do not match the PROJECT name. So, could we live with the PROJECT

Re: [DISCUSS] Name of the FlexJS Fork

Yes. If we might change the name after forming the new PMC, it’s a concern. Alex’s question is more about the framework developing into something else in the future. That’s something I don’t think we need to be concerned about right now. I’d rather capitalize on the FlexJS name. Harbs > On

Re: [DISCUSS] Name of the FlexJS Fork

I thought that name things was one of the concerns in the thread from board. Maybe including link with the vote where we decide whether we would like to change the name or not can be helpful to start talk about the proposal. If no one oppose I could start soon with [VOTE] Should we change name of

Re: [DISCUSS] Name of the FlexJS Fork

I’m fine with voting now. I think the reasons for and against have more or less been addressed. The only point which has not really been addressed was Alex’s question. Personally I don’t think the project name is really a concern as far as some unknown direction the project might take. If it

Re: [DISCUSS] Name of the FlexJS Fork

Probably could vote on the name change. But if that passes, it would need a discussion thread for the new name. -Mark K -Original Message- From: Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com] Sent: Wednesday, September 13, 2017 6:06 AM To: dev@flex.apache.org Subject: [Non-DoD

Re: [DISCUSS] Name of the FlexJS Fork

Agreed with Mark completely! Especially in case of IDEs. I will summarize discussion tomorrow for the notice to the board that we have consensus or not. If there will not be more voices for change than for staying with current one do we still need start a Vote - Something like: Change name or

Re: [DISCUSS] Name of the FlexJS Fork

One thing we need to do is stick with whatever name we come up with. There is a lot of time and money involved in renaming stuff. Not only internally for our own repo's, sites, JIRA, wikies... but also for things like the IDE makes or people building 3rd libraries from it. -Mark K

Re: [DISCUSS] Name of the FlexJS Fork

I got several questions like Harbs mention and people instantly know what is going on when I said them that is the new framework right after Flex. Piotr 2017-09-13 10:53 GMT+02:00 Harbs : > To me the question is how will people react if you tell them you’re doing > it in

Re: [DISCUSS] Name of the FlexJS Fork

To me the question is how will people react if you tell them you’re doing it in FlexJS vs. FooJS. I think in either case you will get a response of “what’s that”. What’s going to get a better explanation? “I’m doing it in a relatively unknown framework but one I like.” Or “I’m doing it in a

Re: [DISCUSS] Name of the FlexJS Fork

Hi Dave, 2017-09-12 21:12 GMT+02:00 Dave Fisher : > > > Do you have examples of Apache Flex or FlexJS getting bad press? It would > make your argument more persuasive. > > There's nothing published. I'm talking about customer meetings where you expose that you can use

Re: [FLEX JS] How to import mx.managers.PopUpManager?

Hi :), I think there is great answer to your question on users list posted today [1]. [1] http://apache-flex-users.246.n4.nabble.com/How-To-Start-Converting-A-Browser-Project-to-FlexJS-td15946.html Thanks, Piotr On Wed, Sep 13, 2017, 08:36 m_awais wrote: > Hi, > > I

Re: [FLEX JS] How to import mx.managers.PopUpManager?

Hi, I was wondering is there any official FLEX JS website, that states all the details of classes and packages FLEX JS currently have. Like Apache Flex Website https://flex.apache.org/asdoc/ which lists all the packages and classes of apache flex and their details. I know one website