Apache Ignite Developers - Legacy Mail Archive

Name of .Net product

classic Classic list List threaded Threaded
♦
♦
 9 messages Options
Vladimir Ozerov
Reply | Threaded
Open this post in threaded view
♦
♦
|

Name of .Net product

Vladimir Ozerov
Igniters,

Let's agree on the final name of our .Net product. For now it is referenced
in various places as "Apache Ignite .Net", "Apache Ignite for .Net",
"Apache Ignite .Net platform", etc..

Ports of other Java projects to .Net are usually named as "[Product].NET".
E.g. Akka.NET, Spring.NET.

I suggest use the same scheme and pick the name "Apache Ignite.NET".

Any ideas or objections?

Vladimir.
Sergi
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Name of .Net product

Sergi
I like "Ignite.NET".

Sergi

2015-10-07 15:04 GMT+03:00 Vladimir Ozerov <[hidden email]>:

> Igniters,
>
> Let's agree on the final name of our .Net product. For now it is referenced
> in various places as "Apache Ignite .Net", "Apache Ignite for .Net",
> "Apache Ignite .Net platform", etc..
>
> Ports of other Java projects to .Net are usually named as "[Product].NET".
> E.g. Akka.NET, Spring.NET.
>
> I suggest use the same scheme and pick the name "Apache Ignite.NET".
>
> Any ideas or objections?
>
> Vladimir.
>
chandresh pancholi
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Name of .Net product

chandresh pancholi
What abount "Ignite DotN".

On Wed, Oct 7, 2015 at 6:54 PM, Sergi Vladykin <[hidden email]>
wrote:

> I like "Ignite.NET".
>
> Sergi
>
> 2015-10-07 15:04 GMT+03:00 Vladimir Ozerov <[hidden email]>:
>
> > Igniters,
> >
> > Let's agree on the final name of our .Net product. For now it is
> referenced
> > in various places as "Apache Ignite .Net", "Apache Ignite for .Net",
> > "Apache Ignite .Net platform", etc..
> >
> > Ports of other Java projects to .Net are usually named as
> "[Product].NET".
> > E.g. Akka.NET, Spring.NET.
> >
> > I suggest use the same scheme and pick the name "Apache Ignite.NET".
> >
> > Any ideas or objections?
> >
> > Vladimir.
> >
>



--
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:[hidden email]
Contact:08951803660
Anton Vinogradov
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Name of .Net product

Anton Vinogradov
+1 Ignite.NET

On Wed, Oct 7, 2015 at 4:27 PM, chandresh pancholi <
[hidden email]> wrote:

> What abount "Ignite DotN".
>
> On Wed, Oct 7, 2015 at 6:54 PM, Sergi Vladykin <[hidden email]>
> wrote:
>
> > I like "Ignite.NET".
> >
> > Sergi
> >
> > 2015-10-07 15:04 GMT+03:00 Vladimir Ozerov <[hidden email]>:
> >
> > > Igniters,
> > >
> > > Let's agree on the final name of our .Net product. For now it is
> > referenced
> > > in various places as "Apache Ignite .Net", "Apache Ignite for .Net",
> > > "Apache Ignite .Net platform", etc..
> > >
> > > Ports of other Java projects to .Net are usually named as
> > "[Product].NET".
> > > E.g. Akka.NET, Spring.NET.
> > >
> > > I suggest use the same scheme and pick the name "Apache Ignite.NET".
> > >
> > > Any ideas or objections?
> > >
> > > Vladimir.
> > >
> >
>
>
>
> --
> Chandresh Pancholi
> Senior Software Engineer
> Flipkart.com
> Email-id:[hidden email]
> Contact:08951803660
>
Raul Kripalani-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Name of .Net product

Raul Kripalani-2
In reply to this post by Vladimir Ozerov
I like Ignite.NET.

I wonder if the .NET portion may be trademarked by Microsoft. If that's the
case, I guess we cannot put a blank space between Ignite and .NET (Ignite
.NET), it'll all need to be a single word, like proposed.

Regards,

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Wed, Oct 7, 2015 at 1:04 PM, Vladimir Ozerov <[hidden email]>
wrote:

> Igniters,
>
> Let's agree on the final name of our .Net product. For now it is referenced
> in various places as "Apache Ignite .Net", "Apache Ignite for .Net",
> "Apache Ignite .Net platform", etc..
>
> Ports of other Java projects to .Net are usually named as "[Product].NET".
> E.g. Akka.NET, Spring.NET.
>
> I suggest use the same scheme and pick the name "Apache Ignite.NET".
>
> Any ideas or objections?
>
> Vladimir.
>
Vladimir Ozerov
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Name of .Net product

Vladimir Ozerov
Raul, good point!

I have no information about .Net trademark, but other products use ".NET"
without a blank space.

On Wed, Oct 7, 2015 at 4:37 PM, Raul Kripalani <[hidden email]> wrote:

> I like Ignite.NET.
>
> I wonder if the .NET portion may be trademarked by Microsoft. If that's the
> case, I guess we cannot put a blank space between Ignite and .NET (Ignite
> .NET), it'll all need to be a single word, like proposed.
>
> Regards,
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Wed, Oct 7, 2015 at 1:04 PM, Vladimir Ozerov <[hidden email]>
> wrote:
>
> > Igniters,
> >
> > Let's agree on the final name of our .Net product. For now it is
> referenced
> > in various places as "Apache Ignite .Net", "Apache Ignite for .Net",
> > "Apache Ignite .Net platform", etc..
> >
> > Ports of other Java projects to .Net are usually named as
> "[Product].NET".
> > E.g. Akka.NET, Spring.NET.
> >
> > I suggest use the same scheme and pick the name "Apache Ignite.NET".
> >
> > Any ideas or objections?
> >
> > Vladimir.
> >
>
dsetrakyan
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Name of .Net product

dsetrakyan
+1 for Ignite.NET or Apache Ignite.NET. I think both should be valid.

On Wed, Oct 7, 2015 at 7:12 AM, Vladimir Ozerov <[hidden email]>
wrote:

> Raul, good point!
>
> I have no information about .Net trademark, but other products use ".NET"
> without a blank space.
>
> On Wed, Oct 7, 2015 at 4:37 PM, Raul Kripalani <[hidden email]> wrote:
>
> > I like Ignite.NET.
> >
> > I wonder if the .NET portion may be trademarked by Microsoft. If that's
> the
> > case, I guess we cannot put a blank space between Ignite and .NET (Ignite
> > .NET), it'll all need to be a single word, like proposed.
> >
> > Regards,
> >
> > *Raúl Kripalani*
> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> > Messaging Engineer
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
> >
> > On Wed, Oct 7, 2015 at 1:04 PM, Vladimir Ozerov <[hidden email]>
> > wrote:
> >
> > > Igniters,
> > >
> > > Let's agree on the final name of our .Net product. For now it is
> > referenced
> > > in various places as "Apache Ignite .Net", "Apache Ignite for .Net",
> > > "Apache Ignite .Net platform", etc..
> > >
> > > Ports of other Java projects to .Net are usually named as
> > "[Product].NET".
> > > E.g. Akka.NET, Spring.NET.
> > >
> > > I suggest use the same scheme and pick the name "Apache Ignite.NET".
> > >
> > > Any ideas or objections?
> > >
> > > Vladimir.
> > >
> >
>
Konstantin Boudnik-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Name of .Net product

Konstantin Boudnik-2
Technically, "Apache Ignite" is the project trademark (which could be
registered, if needed). Hence the longer name is probably more correct.

Cos

On Wed, Oct 07, 2015 at 07:31AM, Dmitriy Setrakyan wrote:

> +1 for Ignite.NET or Apache Ignite.NET. I think both should be valid.
>
> On Wed, Oct 7, 2015 at 7:12 AM, Vladimir Ozerov <[hidden email]>
> wrote:
>
> > Raul, good point!
> >
> > I have no information about .Net trademark, but other products use ".NET"
> > without a blank space.
> >
> > On Wed, Oct 7, 2015 at 4:37 PM, Raul Kripalani <[hidden email]> wrote:
> >
> > > I like Ignite.NET.
> > >
> > > I wonder if the .NET portion may be trademarked by Microsoft. If that's
> > the
> > > case, I guess we cannot put a blank space between Ignite and .NET (Ignite
> > > .NET), it'll all need to be a single word, like proposed.
> > >
> > > Regards,
> > >
> > > *Raúl Kripalani*
> > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> > > Messaging Engineer
> > > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > > http://blog.raulkr.net | twitter: @raulvk
> > >
> > > On Wed, Oct 7, 2015 at 1:04 PM, Vladimir Ozerov <[hidden email]>
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > Let's agree on the final name of our .Net product. For now it is
> > > referenced
> > > > in various places as "Apache Ignite .Net", "Apache Ignite for .Net",
> > > > "Apache Ignite .Net platform", etc..
> > > >
> > > > Ports of other Java projects to .Net are usually named as
> > > "[Product].NET".
> > > > E.g. Akka.NET, Spring.NET.
> > > >
> > > > I suggest use the same scheme and pick the name "Apache Ignite.NET".
> > > >
> > > > Any ideas or objections?
> > > >
> > > > Vladimir.
> > > >
> > >
> >
Gianfranco Murador-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Name of .Net product

Gianfranco Murador-2
+1 Ignite.NET

2015-10-07 18:31 GMT+02:00 Konstantin Boudnik <[hidden email]>:

> Technically, "Apache Ignite" is the project trademark (which could be
> registered, if needed). Hence the longer name is probably more correct.
>
> Cos
>
> On Wed, Oct 07, 2015 at 07:31AM, Dmitriy Setrakyan wrote:
> > +1 for Ignite.NET or Apache Ignite.NET. I think both should be valid.
> >
> > On Wed, Oct 7, 2015 at 7:12 AM, Vladimir Ozerov <[hidden email]>
> > wrote:
> >
> > > Raul, good point!
> > >
> > > I have no information about .Net trademark, but other products use
> ".NET"
> > > without a blank space.
> > >
> > > On Wed, Oct 7, 2015 at 4:37 PM, Raul Kripalani <[hidden email]>
> wrote:
> > >
> > > > I like Ignite.NET.
> > > >
> > > > I wonder if the .NET portion may be trademarked by Microsoft. If
> that's
> > > the
> > > > case, I guess we cannot put a blank space between Ignite and .NET
> (Ignite
> > > > .NET), it'll all need to be a single word, like proposed.
> > > >
> > > > Regards,
> > > >
> > > > *Raúl Kripalani*
> > > > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big
> Data and
> > > > Messaging Engineer
> > > > http://about.me/raulkripalani |
> http://www.linkedin.com/in/raulkripalani
> > > > http://blog.raulkr.net | twitter: @raulvk
> > > >
> > > > On Wed, Oct 7, 2015 at 1:04 PM, Vladimir Ozerov <
> [hidden email]>
> > > > wrote:
> > > >
> > > > > Igniters,
> > > > >
> > > > > Let's agree on the final name of our .Net product. For now it is
> > > > referenced
> > > > > in various places as "Apache Ignite .Net", "Apache Ignite for
> .Net",
> > > > > "Apache Ignite .Net platform", etc..
> > > > >
> > > > > Ports of other Java projects to .Net are usually named as
> > > > "[Product].NET".
> > > > > E.g. Akka.NET, Spring.NET.
> > > > >
> > > > > I suggest use the same scheme and pick the name "Apache
> Ignite.NET".
> > > > >
> > > > > Any ideas or objections?
> > > > >
> > > > > Vladimir.
> > > > >
> > > >
> > >
>



--
Gianfranco Murador
Igniter and Software Engineer.
Free forum by Nabble Edit this page