wavepacket-ng-devel

[Wavepacket-ng-devel] Project name

[Ulf L. <ul...@wa...>]

First thing to decide on: How do we want to name the project?

There are two names: The public name (what labels appear and so on),
and an internal name that serves as the link on the sourceforge pages.

So how would we call the new subproject? It should be clearly related
to WavePacket, but somehow be set apart from the "normal" project.
Ideas I can come up with right now:

WavePacket-ng
WavePacket++
OOWavePacket

Other ideas?

For the internal name, I have used wavepacket-ng for now (ng = next
generation). We can change this to another one, however, I do not know
what characters are allowed (probably alphanumeric + "-"). Ideas?


Ulf

Re: [Wavepacket-ng-devel] Project name

[Ulf L. <ul...@wa...>]

On Sun, 2 Dec 2012 23:43:23 +0100
Ulf Lorenz <ul...@wa...> wrote:

> First thing to decide on: How do we want to name the project?
> 
> There are two names: The public name (what labels appear and so on),
> and an internal name that serves as the link on the sourceforge pages.

Since the subproject is now gone, and we need not take care of it any
longer, I would build on Burkhard's idea, and suggest:

internal name: cpp (appears in the web server path)
outside name: WavePacket, C++ version (just "C++ version" on the
              project page)

and use version numbers "cpp-x.y.z" for this project, so that one can
refer to it simply as "WavePacket cpp-1.0" etc.


Ulf

Re: [Wavepacket-ng-devel] Project name

[Ulf L. <ul...@wa...>]

Ok, since noone objected, this is now set. I noticed that Burkhard was
faster than me, so the subproject is already found under
http://sourceforge.net/p/wavepacket/cpp


Ulf


On Tue, 4 Dec 2012 17:34:41 +0100
Ulf Lorenz <ul...@wa...> wrote:

> On Sun, 2 Dec 2012 23:43:23 +0100
> Ulf Lorenz <ul...@wa...> wrote:
> 
> > First thing to decide on: How do we want to name the project?
> > 
> > There are two names: The public name (what labels appear and so on),
> > and an internal name that serves as the link on the sourceforge
> > pages.
> 
> Since the subproject is now gone, and we need not take care of it any
> longer, I would build on Burkhard's idea, and suggest:
> 
> internal name: cpp (appears in the web server path)
> outside name: WavePacket, C++ version (just "C++ version" on the
>               project page)
> 
> and use version numbers "cpp-x.y.z" for this project, so that one can
> refer to it simply as "WavePacket cpp-1.0" etc.
> 
> 
> Ulf
> 
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add
> services Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Wavepacket-ng-devel mailing list
> Wav...@li...
> https://lists.sourceforge.net/lists/listinfo/wavepacket-ng-devel