Hi Bill, On Wed, Dec 21, 2011 at 11:02 AM, William A. Rowe Jr. <wr...@rowe-clan.net> wrote: > On 12/21/2011 3:00 AM, Bertrand Delacretaz wrote: >> >> As long as there's no confusion as to which Flex is which, and as long >> as there's no favoritism in how people are allowed to use the Flex >> name, I think this might work. > > Whoa... slow down. You are not correct Bertrand. > > As long as there is no confusion over 'The ASF Project Flex' and everything > else that has nothing (or little) to do with the ASF, or is commercial > in nature, then you were essentially right....
Ok, that's what I meant, or intended to mean at least. > > But the project doesn't have the liberty to say f**kit, everyone already > is using the word "flex", we'll roll with it. An ASF project name must > be a distinct and defensible mark, in order to ensure that what the ASF > aggregates is "the ASF work" and everything else is "something else".... I agree about the need to be able to distinguish ASF work from non-ASF work. The usual way to solve this is to be very picky about people using Foo as part of their stuff's name when Foo is an Apache project. It might not be the only way - I don't want to go into detail now (as I might not be sufficiently competent in terms of trademarks to do so), my goal is to defer this discussion until the podling actually starts. Considering that a name change is possible, this issue does not (IMO) need to be solved before the podling is voted in. > > That makes some existing consumers/distributors/providers uncomfortable > and we can and will work with them on a case by case basis, to ensure > that what they are doing is not confused with the ASF's efforts. But > we can't just say "it might work" and throw it over our shoulder. > By "it might work" I mean "the podling might find a way to make it work". I totally agree that the use of the Apache Flex trademark needs to be clearly defined - once the podling starts. -Bertrand --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
