On Tue, Nov 28, 2023 at 12:12 PM Justin Mclean <jus...@classsoftware.com> wrote: > > Hi, > > We need to know the reasons for the name change and why the company is > willing to donate the code but not the name. The possibility of having them > forking the community later is a risk the Incubator needs to know about and > should be mentioned in the proposal. Having a brand closely associated with a > project and owned by a single corporate entity is a risk to the project. Why > a company would be unwilling to give up that brand or trademark just because > it may be convenient in the future is a concern.
While I agree that having a clear reason stated would be helpful, I think I have a different take on the risks you are outlining here. We have tons of examples here in the ASF of project Foo being used to power commercial product Bar (Geode/Gemfire, Ignite/GridGain, Kafka/Confluent, and many, many more). So this kind of dual branding is nothing new -- there's no community fork involved per se. It would be nice if the original name of the open source project (as it existed on Github) was donated to ASF and the new name for a commercially developed product was picked. But even if it is the other way around -- I actually don't see any risks for the foundation in this approach (as long as it is clearly understood that the branding guidelines on both sides need to be honored). Thanks, Roman. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
