Unfortunately that’s an Apache foundation policy and the Spark community has no power to change it. My understanding: The reason Spark can’t be in the name is because if it is used frequently enough, the foundation would lose the Spark trademark. Cheers.
On Wed, Aug 15, 2018 at 7:19 AM Simon Dirmeier <simon.dirme...@web.de> wrote: > Hey, > thanks for clearning that up. > Imho this is somewhat unfortunate, because package names that contain > "spark", somewhat promote and advertise Apache Spark, right? > > Best, > Simon > > Am 15.08.18 um 14:00 schrieb Sean Owen: > > You raise a great point, and we were just discussing this. The page is old > and contains many projects that were listed before the trademarks we're > being enforced. Some have renamed themselves. We will update the page and > remove stale or noncompliant projects and ask those that need to change to > do so. > > You are correct that the guidance you quote is current and should be > followed. > > Note there is an exception for software identifiers. > > On Wed, Aug 15, 2018, 6:13 AM Simon Dirmeier <simon.dirme...@web.de> > wrote: > >> Dear all, >> >> I am currently developing two OSS extension packages for spark; one >> related to machine learning; one related to biological applications. >> According to the trademark guidelines ( >> https://spark.apache.org/trademarks.html) I am not allowed to use >> *Names derived from “Spark”, such as “sparkly”. * >> My question is if that is really the case or how stringent these >> guidelines are, given that so many spark packages ( >> https://spark.apache.org/third-party-projects.html) contain Spark as >> name already. I already contacted the official email for questions like >> these, but didn't hear back until now. >> >> Can anyone please shed light on this? >> Thanks in advance! >> >> Best, >> Simon >> > >
