Hey Mike, good to see your name again ;) Interesting point, something I was not thinking about to take into consideration indeed. I think we got it convered for the purpose of this thread and each party / role expressed their concern. I'm looking forward to reading the feedback from Apache lawyers on the use of Flex in domain name without "apache". Im just a bit concerned about being an obstacle to the community embracing Flex and promoting it. In this specific case, I also do not see how using Flex alone as a generic name for "flash interfaces using Flex SDK" would be a concern for enterprises. I would even argue that not seing flex anywhere on search engine anymore would be telling enterprises "there is not enough adoption".
Which remind me of anothet concern I have: support. I should probably send a separate email with a new title to create a new conversation, I will after searching previous conversation first. But just as an example, Disney Interactive in Palo Alto recently told me that they abandon AIR because Flex support was now community based. I can see enteprises being concern if Flex support is community bases with not enough adoption, which apache lawyers attitude about the use of "flex" could make even.worse. Remember the time when you could Google any Flash, Flex or AIR problem or task or error message amd find an answer, a solution or a fix in 2 mn? We need that back, badly! On Jan 3, 2014 5:20 PM, "Michael A. Labriola" <labri...@digitalprimates.net> wrote: > >Here is the thing though -- it's not a "us vs. them" type of situation. > We are all Apache (including the community). The trademark group within > the Apache Foundation is there to protect us. Please see it that way. >We > live in a litigious world and we all need to realize that. > > I don't want to wade too deeply into this without reading everything else, > but keep one more thing in mind too. Apache doesn't just protect us; they > also protect the people that use Flex. One of the reasons corporations, > even those that don't normally allow much open source, often allow Apache > projects is that they believe in Apache's process. They believe Apache > projects do the diligence to ensure there aren't code and trademark > violations which could be a problem for the Corporation in the future. It > makes them feel safe in using this project. > > Just my addition, > Mike > >
